TMS320F28377S: BIOS cannot run

Green Deng

Part Number: TMS320F28377S

Dear team:

My customer uses CCS10.3 to build a project based on the F28377S chip. There is no error after compilation, but the BIOS cannot be started after burning into the chip. After executing BIOS_start(), it prompts "Break at address "0x3FE493""

And he found that after changing the name of the .lib file(As shown below) in the Debug folder generated by the compilation to .Lib, recompiling and burning it into the chip, the BIOS can be started. During Debug, the error did not occur, and the interruption and task execution were normal.

Or directly delete the "lib" folder in the Debug folder, create a new "Lib" folder and recompile, at this time...>Debug>Lib folder is empty, but the program can also be run.

Is the client's library usage incorrect? Or is there a problem with the CCS settings?

Best regards

over 4 years ago

0 Whitney Dewey over 4 years ago

TI__Guru 54295 points

If breakpoints are placed in his Task and Hwi functions, they are never hit? It just crashes somewhere in BIOS_start? Can he single step through the code to find if there's a specific line that seems to be the one at which it crashes?

I believe the address 0x3FE493 is the ITRAP handler in the boot ROM, meaning the program appears to be crashing before SYS/BIOS can even plug its illegal instruction handler. Stack overflow or corruption is a frequent cause of ITRAP issues. Can the customer look for signs of stack issues in the Memory Browser or ROV?

It doesn't really make sense to me that changing the RTS library would solve the problem.

Whitney

0 Green Deng over 4 years ago in reply to Whitney Dewey

TI__Expert 4490 points

Hi Whitney:

After debug runs to this step, an error occurs: “Break at address "0x3fe2ed" with no debug information available, or outside of program code.”

+1 Whitney Dewey over 4 years ago in reply to Green Deng

TI__Guru 54295 points

I think that address might be WaitBoot, so something seems to be resetting the device. Can they check the reset cause register to see what it might be? If they have not already, can they configure the SYS/BIOS Boot module to disable the watchdog and see if that makes a difference?

Whitney

0 c c over 4 years ago in reply to Whitney Dewey

Prodigy 20 points

This occurs after the watchdog is banned

0 Whitney Dewey over 4 years ago in reply to c c

TI__Guru 54295 points

Hi c c, I see you posted this question in another thread. I've responded there.

Whitney

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28377S: BIOS cannot run