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.

Educational BoosterPack MKII

Other Parts Discussed in Thread: MSP430FR6989, UNIFLASH

Hello! I am having trouble with the Educational BoosterPack MKII. I ordered the BoosterPack as well as the MSP430FR6989 development board. I need both of them for my class at UCF. We used the MSP430FR6989 for the first few weeks and it works perfectly, but the class required the BoosterPack last week for the first time and as soon as I connected it, it makes this popping noise and it blinks the screen on the boosterpack with every small pop. It doesn't let me run anything on it with Code Composer Studio. As soon as I try to, I get an error message that asks me to update the firmware, but every time I do, it gives the exact same error message. I used my friend's microcontroller and boosterpack and it works perfectly, so I know the problem isn't with my computer or software. Any help you could give would be great. Thanks!

  • Hi Hunter,

    That certainly is strange. It could be related to what firmware was loaded previously may be toggling the pin with the buzzer that is triggering the pop noise? The noise is coming from the buzzer I am guessing? I don't think noise can be generated anywhere else on the board.

    The key thing is to get the LaunchPad back to a working state. Disconnect the BoosterPack and try to reload some older code with the LaunchPad only. If you still get request to update firmware, then you may need to try a different tool like UniFlash to attempt to load some new code outside of CCS and get the debugger back to normal. 

    Once you get the LaunchPad loaded with some new code, then I suggest you load a blank program to the LaunchPad, reinsert the BoosterPack, and trying to load in your assignment code. 

    Also contact your professor that you are having this issue. They should be able to offer some additional suggestions on how to debug or swap new hardware.