TMS320F280049: After a reset, sometimes DSP goes to sys down and get stuck in wait boot address

Hello Nada,

I will let an expert answering the TRACE32 and "wait boot" part.

Regarding the ROM symbols, you need to add the relevant .lib files to the linking process. please see this screenshot if doing it within CCS (add each library file to the -l section and the above path into C2000Ware in the linker -i section), or add the relevant -l and -i commands to your linker command file.

Best regards,
François.

this is the expected behavior. Please refer TRM for more details.

Hello Baskaran and Francois,

Thanks for your answers.

Please Baskaran, why it is an expected behavior? which chapter of TRM are you referring to ?

Regards,

Nada

Hello, 

so it is normal to be in Boot Mode after a reset, and how can we avoid to be in this state using Jtag ?

you can avoid wait boot while jtag is connected by programming the EMU config registers at oxD00, D04, D06.

hello, could you please specify which registers exactly (name and field) ?

Thanks

Thanks Francois, but i'm not using CCS, i'm using DSP with Trace32, so i need to configure this in our code.

Hi Baskaran,

Nada marked by mistake the issue as resolved. Could you advise on how Nada should proceed with TRACE32? Is it sufficient to update the EMU config registers at oxD00, D04, D06? Also should she define _FLASH in her application?

Best regards,
François.

i am not aware of TRACE32 usage. 

to avoid wait boot with JTAG connected it is enough to update EMU config registers. All these details are available in TRM, please read the boot section once to get more clarity.

Hi Baskaran,

We noticed that both EMU-BOOTPIN-CONFIG and the ePIE vector table share the same start address at 0xd00. What makes that accessing 0xd00 from the debugger will access one or the other?

Best regards,
François.

0xD00 will be used by boot rom only during boot after that the application can load the ePIE vector table.

Hi Baskaran,

Thank you. What we wanted to understand is the mechanism that makes that during boot time, address 0xd00 corresponds to the emulation control registers and that during application run time, it corresponds to the ePIE vector table. Is there a control bit somewhere that the ROM code switches so to redirect 0xd00?

Best regards,
François.

there is no mechanism involved.

The usage is serial - boot uses the location 0xD00 during boot time and when the Program counter moves to application, the application can use the same location for vector table.

Hi Baskaran,

Sorry but I do not get it. What makes that when accessing address 0xd00, the debugger or C28x core will access the emulation control register or the ePIE table? Worded differently, how does one just writes to the 0xd00 emulation control register and not the ePIE table, or vice versa?

I must be missing the obvious... Thank you for your patience.

Best regards,
François.

it will overwrite. but the usage is mutually exclusive. when you are using it as emulation control register you wont need pie vector table.

also holds good that when you are using as vector table you wont be needing to use it as emu ctrl reg ?

simply put - emu ctrl reg is boot usage and pie vector table is application usage.