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.

TMS320F28075: CodeStart suddenly stopped working, any suggestions?

Part Number: TMS320F28075

HI guys, This is weird. I'm using TMS320F28075 LQFP 176Pin on standalone board and suddenly codestart stopped working. In the past months it's been working fine but now no go.

I write ASM code using CCS12.8.1 and download my assembler code to the MCU and it would always run fine. Power off then on and the MCU would start exactly how it should with no problems.

Now I download my code, power off and then on and the MCU will not run. Very Strange.

I then loaded up CCS20.4.1 and wrote a small ASM program ( BLINKY ) and downloaded the code to the MCU, powered off and then on and the MCU would startup fine and LED's on PORTA would start flashing but using CCS12.8.1 it just won't run after powering off and then on again.

I haven't changed anything in CCS12.8.1, just written ASM code. The MCU works fine using CCS20.4.1 so its definatly something to do with CCS12.8.1. 

Oh, I'm using an iMac with OS 15.7.1 Sequoia.

Any suggestions would be very much appreciated.

Thanks guys, Peter.

  • Hi Peter,

    Please note that CCS 12.x has been obsoleted. Hence the amount of support for it will be limited. 

    That said,

    Now I download my code, power off and then on and the MCU will not run. Very Strange.

    So if I understand correctly, you using CCS 12.8 to flash the program to your device. Then you disconnect the board/device from CCS, power cycle the board and expect it to run but it is not running as expected. 

    I then loaded up CCS20.4.1 and wrote a small ASM program ( BLINKY ) and downloaded the code to the MCU, powered off and then on and the MCU would startup fine and LED's on PORTA would start flashing but using CCS12.8.1 it just won't run after powering off and then on again.

    Then you tried with a simple example on 20.4. but that works. But when flashing the SAME executable generated from 20.4 using 12.8, it does not run as expected?

    Did I understand correctly?

  • Hi Ki, thank you for your reply. YES all is correct except I didn't load in an example of BLINKY, I wrote my own BLINKY in assembler and flashed the 28075 as I would every other time, powered the board off then on and the MCU won't run. 

    Please don't tell me I have to use CCS 20.4.1 now because CCS 20.4.1 assembly support is absolutly terrible. CCS12.8.1 is so much better with assembly support. 

    So what do you think why CodeStart is not starting the chip when powering on? Last month it was fine. I've checked the boot pins and both are high when powering up because I have 4.7k pull-ups connected to them. 

    I haven't changed anything in the 28075_FLASH_lnk.cmd file either. CodeStart has it's own .section in my assembler code and that has not been changed either, it's exactly the same as it was last month when everything was working perfectly. I totally stuck with this one and that's why I'm asking for some support with this. 

    The only thing I can think of is to save my ASM code and reinstall CCS 12.8.1 and see how I go. 

    Oh, if you remember last week every time I'd start CCS12.8.1 it would remind me to install the seggar update every time I'd start CCS12.8.1. I've turned off automatic updates so this doesn't happen. Do you think that has something to do with my MCU not running when powering on?

    Peter

  • Hi Ki, cancel this as I found the problem. One of my colleagues soldered one of the BOOT pins to another MCU IO pin which was pulling the boot pin to ground so of course the 20875 would not start up. Grrrrrrr. I wish they had told me this in the first place. CCS12.8.1 is working perfectly as it does, it's my colleagues that is not. LOL.

    Peter Slight smile

  • Ok, glad you resolved the issue and thanks for the update!