Something as simple as the wires being too long (adds too much capacitance) could prevent the JTAG/SBW communication from working correctly, which will sometimes respond with the fuse blown error. This is why the above test is important, as it verifies your test setup is ok. Sometimes if the connection is bad between the EZFET and the target device, it will report the same error. You can use the USB BSL to restore the JTAG lock bits on the F5529, assuming that is actually the issue. Just for the sake of ensuring your test setup is correct, did you try using the EZFET on the failing LaunchPad to program the F5529 on the good LP? This should work, but is worth testing to make sure your setup/procedures are good. Pridgen, then its only logical that I should refer to you as Mr. I managed to get into edit mode, here are the screenshots: Can you point me to a binary TI.txt file or other solution, that I can download to the MSP430 and remedy this problem? However, you may know of a better solution, or troubleshooting method and I would like to hear your opinion first. I believe my easiest solution for me would be to try to use the BSL to do a mass erase. This happened because the good Launchpad, B, had its firmware and USB driver modified when I was conducting another project. There existed an initial ancilliary issue with regard to my MSP430 USB firmware needing to be updated and also a driver. In any case, in a nutshell, I received a message in telling me that a "security fuse" had been blown on when I hot wired the known working FET jumpers to the bad MSP430F Launchpad board. When I attempt to edit this message then the insert option may open up for me. I can't upload anything now because this webpage does not offer me the "insert" option. I will try to upload what I saw on my computer screen when I tried to download a program using debug in CCS6. I "hot wired" the good unit, B, to the bad board, A, and I received an interesting response. I did this because our future correspondences may become confusing to other readers and, possibly, each other, as we are both named "Mike". Please excuse the formality of addressing you by your last name. Please post back the results of this test and we can help debug from here. If test 4 fails, but test 3 passes, then the problem is with the target F5529. If test 3 fails, but 4 passes, then the problem is in the EZFET. EZFET_B programming F5529_B - this should be a known working caseĭepending on which of tests 3 and 4 fail, we should be able to determine if the problem is with the EZFET or the F5529 on the failing launchpads.EZFET_A programming F5529_A - this should be a known failing case.If you have two boards: A (failing board), and B (working board), here are the tests: Doing this both ways with the two LPs will help you isolate the issue and potentially try to debug it. Just use wire jumpers to connect the top pin of the above signals on one LP to the bottom pin of the above signals on the other LP. If you have a second F5529 LaunchPad, you can use one the EZFET on one LP to program the device on the other LP. Since you mention having many LaunchPads, I'm assuming that you have double and triple checked the jumpers on the programming interface to ensure GND, 5V, 3V3, SBW RST, and SBW TST were all connected. Sounds like there may be a connection issue between the EZFET and the F5529. If there exists a maintenance software program in a format so that I can I use the TI Python Firmware Upgrader or other MSP430 flashing program, to reset the MSP430 (reset every memory location) can you please link me to the program?Īlso, f there exists a maintenance software program such that the bootstrap loader can be utilized to check the hardware on the MSP430F5529 or the other IC's on the MSP430F5529 launchpad can you please link me to the program? I was hoping that someone at TI can recognize the source of the problem. However, when I still attempt to use the program in the MSP430 CCS IDE, I still get the that same error message - " Error connecting to the target: Unknown device ". Recently, I used the TI Python Firmware Upgrader and tried the bootstrap loader option and the launchpad that was returning the error message now operates correctly according to the program that was downloaded. MSP430: Error connecting to the target: Unknown device When I try to download a program onto the Launchpad I receive this message in CCS: They all work fine in my CCS IDE, except for one. I was hoping someone at TI can answer this question: Other Parts Discussed in Thread: MSP430F5529, MSP430WARE, MSPBSL
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |