Hello, I just bought a new MSP-FET (Farnell 2460068) and have problems getting it to work. First I downloaded slac460w from the TI site, but it failed to compile, with DLL430_v3/src/TI/DLL430/UpdateManagerFet.cpp:1279:9: error: ‘MSP_FetFpgaHalImage_sections’ was not declared in this scope
return MSP_FetFpgaHalImage_sections * 2; Then I downloaded <https://github.com/BuLogics/libMSP430> https://github.com/BuLogics/libMSP430 from which I could compile libmsp430.so. Next, I downloaded and compiled last version (0.25) of mspdebug.. It works OK with my launchpad (rf2500), but I can't get it to work with then new MSP_FET (serial 170500372). What could be wrong? Below I pasted the output of dmesg, lsusb and some mspdebug commands. (sorry for the big line spacing, but I am sendidng this from a windows machine which has problems with linux .txt files) Marko Cebokli [ 304.288053] usb 1-6: new full-speed USB device number 3 using xhci_hcd [ 304.419077] usb 1-6: New USB device found, idVendor=2047, idProduct=0014 [ 304.419080] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 304.419081] usb 1-6: Product: MSP Tools Driver [ 304.419082] usb 1-6: Manufacturer: Texas Instruments [ 304.419083] usb 1-6: SerialNumber: ACF713470B001700 [ 304.469789] cdc_acm 1-6:1.0: ttyACM0: USB ACM device [ 304.469988] cdc_acm 1-6:1.2: ttyACM1: USB ACM device [ 304.470145] usbcore: registered new interface driver cdc_acm [ 304.470146] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> lsusb Bus 003 Device 004: ID 0a5c:216c Broadcom Corp. Bus 003 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 2047:0014 Texas Instruments Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mspdebug --usb-list Devices on bus 003: 003:004 0a5c:216c 003:003 05c8:036e 003:002 8087:8000 003:001 1d6b:0002 Devices on bus 002: 002:001 1d6b:0003 Devices on bus 001: 001:003 2047:0014 001:002 0458:003a 001:001 1d6b:0002 mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> sudo ./mspdebug tilib [sudo] password for root: MSPDebug version 0.25 - debugging tool for MSP430 MCUs Copyright (C) 2009-2017 Daniel Beer <dlb...@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using old API MSP430_GetNumberOfUsbIfs No unused FET found. mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> ./mspdebug tilib -U 001:003 MSPDebug version 0.25 - debugging tool for MSP430 MCUs Copyright (C) 2009-2017 Daniel Beer <dlb...@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using old API MSP430_GetNumberOfUsbIfs No unused FET found. mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> sudo ./mspdebug tilib -d /dev/ttyACM1 MSPDebug version 0.25 - debugging tool for MSP430 MCUs Copyright (C) 2009-2017 Daniel Beer <dlb...@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using old API MSP430_Initialize: /dev/ttyACM1 FET firmware update is required. Re-run with --allow-fw-update to perform a firmware update. tilib: device initialization failed mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> mc@gvdpc7:~/Downloads/mspdebug-0.25> sudo ./mspdebug tilib -d /dev/ttyACM1 --allow-fw-update MSPDebug version 0.25 - debugging tool for MSP430 MCUs Copyright (C) 2009-2017 Daniel Beer <dlb...@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using old API MSP430_Initialize: /dev/ttyACM1 FET firmware update is required. Starting firmware update (this may take some time)... Initializing bootloader... Initializing bootloader... Initializing bootloader... tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader active (error = 56) tilib: device initialization failed mc@gvdpc7:~/Downloads/mspdebug-0.25> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
