This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

python-msp430-tools installation

I am trying to setup the Python_Firmare_Upgrader on Ubuntu 12.04 LTS with Python 2.7.3 installed

 

I have copied the Python_Firmware_Upgrader directory to my home directory.

I cd to python-msp430-tools and run python setup.py install.

It fails!!!.  It seems to be unable to install the scripts, which do exist.

 

sorry if I have missed something obvious, I am a python newbee.

 

 

 

lharmon@ubuntu:~/Python_Firmware_Upgrader/python-msp430-tools$ python setup.py install running install running build running build_py creating build creating build/lib.linux-i686-2.7 creating build/lib.linux-i686-2.7/msp430 copying msp430/target.py -> build/lib.linux-i686-2.7/msp430 copying msp430/__init__.py -> build/lib.linux-i686-2.7/msp430 creating build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/disassemble.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/lib.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/cpp.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/infix2postfix.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/forth.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/rpn.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/__init__.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/mcu_definition_parser.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/h2forth.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/peripherals.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/as.py -> build/lib.linux-i686-2.7/msp430/asm copying msp430/asm/ld.py -> build/lib.linux-i686-2.7/msp430/asm creating build/lib.linux-i686-2.7/msp430/bsl copying msp430/bsl/bsl.py -> build/lib.linux-i686-2.7/msp430/bsl copying msp430/bsl/__init__.py -> build/lib.linux-i686-2.7/msp430/bsl creating build/lib.linux-i686-2.7/msp430/bsl/target copying msp430/bsl/target/__main__.py -> build/lib.linux-i686-2.7/msp430/bsl/target copying msp430/bsl/target/__init__.py -> build/lib.linux-i686-2.7/msp430/bsl/target copying msp430/bsl/target/fcdprog.py -> build/lib.linux-i686-2.7/msp430/bsl/target copying msp430/bsl/target/telosb.py -> build/lib.linux-i686-2.7/msp430/bsl/target creating build/lib.linux-i686-2.7/msp430/bsl5 copying msp430/bsl5/hid.py -> build/lib.linux-i686-2.7/msp430/bsl5 copying msp430/bsl5/__init__.py -> build/lib.linux-i686-2.7/msp430/bsl5 copying msp430/bsl5/bsl5.py -> build/lib.linux-i686-2.7/msp430/bsl5 copying msp430/bsl5/uart.py -> build/lib.linux-i686-2.7/msp430/bsl5 creating build/lib.linux-i686-2.7/msp430/gdb copying msp430/gdb/target.py -> build/lib.linux-i686-2.7/msp430/gdb copying msp430/gdb/__init__.py -> build/lib.linux-i686-2.7/msp430/gdb copying msp430/gdb/gdb.py -> build/lib.linux-i686-2.7/msp430/gdb creating build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/profile.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/dco.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/clock.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/target.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/__init__.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/hilspi.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/jtag.py -> build/lib.linux-i686-2.7/msp430/jtag copying msp430/jtag/HIL.py -> build/lib.linux-i686-2.7/msp430/jtag creating build/lib.linux-i686-2.7/msp430/legacy copying msp430/legacy/bsl.py -> build/lib.linux-i686-2.7/msp430/legacy copying msp430/legacy/__init__.py -> build/lib.linux-i686-2.7/msp430/legacy creating build/lib.linux-i686-2.7/msp430/listing copying msp430/listing/iar.py -> build/lib.linux-i686-2.7/msp430/listing copying msp430/listing/__init__.py -> build/lib.linux-i686-2.7/msp430/listing copying msp430/listing/mspgcc.py -> build/lib.linux-i686-2.7/msp430/listing creating build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/convert.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/titext.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/hexdump.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/elf.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/bin.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/compare.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/intelhex.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/__init__.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/generate.py -> build/lib.linux-i686-2.7/msp430/memory copying msp430/memory/error.py -> build/lib.linux-i686-2.7/msp430/memory creating build/lib.linux-i686-2.7/msp430/shell copying msp430/shell/command.py -> build/lib.linux-i686-2.7/msp430/shell copying msp430/shell/watch.py -> build/lib.linux-i686-2.7/msp430/shell copying msp430/shell/__init__.py -> build/lib.linux-i686-2.7/msp430/shell creating build/lib.linux-i686-2.7/msp430/asm/definitions copying msp430/asm/definitions/msp430-mcu-list.txt -> build/lib.linux-i686-2.7/msp430/asm/definitions copying msp430/bsl/BL_150S_14x.txt -> build/lib.linux-i686-2.7/msp430/bsl copying msp430/bsl/BL_150S_44x.txt -> build/lib.linux-i686-2.7/msp430/bsl copying msp430/bsl/BS_150S_14x.txt -> build/lib.linux-i686-2.7/msp430/bsl copying msp430/bsl/patch.txt -> build/lib.linux-i686-2.7/msp430/bsl copying msp430/bsl5/RAM_BSL.00.07.87.37.txt -> build/lib.linux-i686-2.7/msp430/bsl5 running build_scripts creating build/scripts-2.7 error: file '/home/lharmon/Python_Firmware_Upgrader/python-msp430-tools/scripts/msp430-bsl' does not exist lharmon@ubuntu:~/Python_Firmware_Upgrader/python-msp430-tools$

  • I am seeing a similar problem with the Python_Firmware_UpgraderGUI.exe - it looks like the updater will erase the flash on my F5529 device, download the BSL, but it does not download the selected application (LED blink).

    Here is what is displayed:

    Opening HID device HID device (vID=0x2047, pID=0x0200, v=0x0101); Unknown manufacturer; @input.inf,%hid_device%;HID-compliant device, Path: \\?\hid#vid_2047&pid_0200#7&2f3a261d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
    Mass erase...
    Download full BSL...
    Programming...
    Programming: OK
    Waiting for BSL...
    closing HID device
    Closed!...
    Opening HID device HID device (vID=0x2047, pID=0x0200, v=0x0101); Unknown manufacturer; @input.inf,%hid_device%;HID-compliant device, Path: \\?\hid#vid_2047&pid_0200#7&2f3a261d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
    Exception in Tkinter callback
    Traceback (most recent call last):
      File "C:\msp430usb\msp430_usb\imports\MSP430USBDevelopersPackage_4_10_00\Host_USB_Software\Python_Firmware_Upgrader\build\pyi.win32\Python_Firmware_UpgraderGUI\out00-PYZ.pyz\Tkinter", line 1470, in __call__
      File "<string>", line 135, in doBlinkLED
      File "<string>", line 180, in doLoad
      File "<string>", line 252, in open_connection
      File "C:\msp430usb\msp430_usb\imports\MSP430USBDevelopersPackage_4_10_00\Host_USB_Software\Python_Firmware_Upgrader\build\pyi.win32\Python_Firmware_UpgraderGUI\out00-PYZ.pyz\msp430.bsl5.bsl5", line 111, in BSL_VERSION
      File "C:\msp430usb\msp430_usb\imports\MSP430USBDevelopersPackage_4_10_00\Host_USB_Software\Python_Firmware_Upgrader\build\pyi.win32\Python_Firmware_UpgraderGUI\out00-PYZ.pyz\msp430.bsl5.bsl5", line 68, in check_answer
    BSL5Error: Unknown command

     

    Any ideas?

    BTW, the visual studio-based BSL_USB_GUI.exe works. Erases and downloads "LED blink."

    However, there are reasons for having the Python-based program working TOO.

     

  • By the way, there is a reference to "C:\msp430usb\msp430_usb\imports\MSP430USBDevelopersPackage_4_10_00\Host_USB_Software\Python_Firmware_Upgrader\build\pyi.win32\Python_Firmware_UpgraderGUI ...

    in the above error situation - that path does NOT exist on my computer.

    Is the "Python_Firmware_Upgrader" looking for that particular path?

**Attention** This is a public forum