[quote user="Dan Cristy"] We use the BSL feature in the MSP430 to implement our firmware upgrade function. Specifically we use the USB interface for BSL communication. We have had a number of firmware upgrade malfunctions that we believe we have traced to a problem with the embedded BSL firmware residing on the MSP430. Is there a method using our existing development tools (Code Composer IDE and MSP-FET 430UIF Debugger) to test or confirm this belief? Something like a test to read out the BSL code and verify its contents or actually run a self-test on this function? [/quote] I developed my custom CDC BSL using main flash with Mailbox logging. At BSL start, BSL code from flash was copied to RAM and executed from there, leaving main flash to be erased / modified. At the end it was relocated to BSL segment with disabled logging. From my experience, best way for debugging things related to USB is logging without stopping execution, not breakpoint debugging. BSL segment is (protected) flash memory like any other main / info flash segment and it is possible to check it's contest (against file) with any SBW / JTAG tool. Also, after BSL finish updating main flash, main flash contest can be checked (against file) with any SBW / JTAG tool.
↧