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.
Hi,
I am working on MSP430F5659 controller, using USB developer package. I have implemented CDC for communication with PC.
For firmware upgrade, as mentioned USB developer package i am using "Python firmware upgrade GUI" which is HID tool.
Now i am able to load firmware on 1st time programming (fresh board) - i.e fresh board detect my board as HID device and i am able to load firmware.
For the second time and so on, i am pushing the device to BSL mode and i am able connect the device with "Python firmware upgrade GUI" tool, i.e on GUI opening and scanning i am getting
message "ready....."
On selecting user firmware(xyx.txt file) it starts mass erase and does the programming and prints "programming ok.". I am guessing this means a proper loading of firmware, am i correct?
After firmware upgrade using tool, i am seeing code changes are not working properly( i have done some pin configuration but its not working after firmware upgrade using tool, works well with JTAG programming)
Is there anything i need to do before i am building the my project, even i am seeing difference in .txt files for different build. ( i have the compiled the code in "Release mode")
Or whether this GUI is not supporting MSP430F5659 controller, please clarify.
Or any optimization issue causing this issue, Just a thought!!!!!!
Please help me in resolving this issue, Thanks in advance
Nitesh
Hi Nitesh,
The Python firmware upgrade GUI is supported for the MSP430F5529, I will ask an expert whether support for the F5659 should be expected as well or if you will need to make any changes to the source in order for it to work. After programming your device with the GUI, can you read back the memory contents and confirm that they are exactly as intended from your TXT files? If differences are present then this would indicate an issue with the python tool. But if they are identical (as expected since the tool should be verifying the memory contents after programming) then we should investigate what changes you are making to the firmware. Are you testing your code inside of an IDE debugger to verify that it works before relying on the GUI? What exact changes are made between functional and broken revisions? Is this your first time compiling the code in release mode?
Regards,
Ryan
Hi Ryan,
Yes, We resolved the issue, It was our board issue, So we tried in other board it is working.
Thanks
Nitesh
**Attention** This is a public forum