TMS320F28388D: Emulation boot fails after customizing boot pin

the first image you showed is a configuration for writing into user OTP setting, not for emulation boot.

For emulation boot you need to write to 0xD00, D04, D06.

Also when you load the application from CCS to RAM there is no involvement of boot mode identification logic. CCS will directly give control to application after loading it.

Hi Baskaran-san,

Thank you for your reply.

Baskaran Chidambaram said:

the first image you showed is a configuration for writing into user OTP setting, not for emulation boot.

Yes, I understand it.

Until now, I have evaluated without setting the user OTP, and at that time I was able to debug without any problems.
However, after setting OTP once, I can no longer debug.
I would like to know a workaround for this.

Best regards,
Sasaki

please share the values at these locations. I am not sure if this is causing the issue or something else,

OK. I share it.

why do you have 5AFFFFFF - i dont think this is causing the issue you are seeing. But just for me to understand.

Also when you are loading via CCS the emulation/standalone boot flow doesn't come into picture at all. Try some other example and check if it works.

Alternatively if you have another setup you can try loading the same example and see if it works.

Baskaran Chidambaram said:

why do you have 5AFFFFFF - i dont think this is causing the issue you are seeing. But just for me to understand.

This was changed because I wanted to change the stand-alone boot setting.

Baskaran Chidambaram said:

Also when you are loading via CCS the emulation/standalone boot flow doesn't come into picture at all. Try some other example and check if it works.

I have tried the SPI and LED programs in the examples folder in C2000ware, but they are all the same and do not work correctly.

The device stops at 0x3fe96f when I load the program. Then reset and restart with CCS and it still stops at 0x3fe96f.

I have read the boot chapter of the TRM and do not understand why it works this way.

Best regards,
Sasaki

seems you are getting itrap exception. Can you check the value at address 0x5e from memory window - this is the address which caused itrap exception.

When I checked the operation again today, Example(led_ex1_blinky) worked without any problems. But the customer's program still doesn't work.

When I debugged their code, address 0x5E contained 0x0005.

Device is able to execute _c_int00() in RAM boot.
When I debug _c_int00() by "Assembly step", I get a TRAP when stepping through __TI_auto_init below.

I investigate inside __TI_auto_init and it goes TRAP at the following code.

Do you know what caused it?

Best regards,
Sasaki

Can you compare the contents of below locations between working (yours) and non-working (customer's) setups.

seems like one of these locations is programmed incorrectly in customers setup.

Hi,

I compared these and the values were the same.Both emulation boot is flash boot.

Non-working (customer's) setups

Working (my) setups

By the way, my project is led_ex2_blinky_dcsm with Build Configrations set to CPU1_FLASH.

Also, in my project, led_ex2_blinky_dcsm, if Build Configrations is set to CPU1_RAM, it will not proceed to main like the customer's project.

Best regards,
Sasaki

the led_ex2_blinky_dcsm is supposed to be executed only once to program the values to OTP locations given in my previous response.

once the values are programmed you can try any other example to check if it works.

And the CPU1_RAM configuration is not needed as the intention of this example is to program the OTP values.

Thank you for your support.

I also tried another project (gpio_ex3_interrupt) and it works fine as does the led_ex2_blinky_dcsm. Similarly, the registers are as follows.

Do you know what is causing this?

Best regards,
Sasaki

As i mentioned earlier the DCSM project involves writing to OTP locations and you can do that only once. So this is not a problem.

looks like you are not facing issues with running other projects. so that's good then.

I want to know why the program doesn't jump to main.Do you know why the program doesn't jump to main?

i am not sure how the c_init function is implemented. I am suspecting there is some access to DCSM registers or to corresponding OTP and that is causing ECC error. this could be a possible reason why the program doesn't reach main.