Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

TMS320F28384S: Unable to run application code as it is stuck in reset

Part Number: TMS320F28384S

Tool/software:

Hi Team,

we have recently procured 28384s ICs to replace with 28377s ICs with same hardware (Only change is 56 Ohm resistor placed between VDD and VSS in place of the decoupling capacitor). I have gone through migration guide and made the project for 28384s. Even with any of the example projects run with flash or RAM linker files also same issue.

I am able to flash the code and connect the emulator but application code is not running. I am thing its stuck in boot mode itself. GPIO72 & GPIO84 connected 3.3V through 4.7k pullups so both are always high so flash boot mode will be selected as it is already programmed once.

When I checked XRSn pin its getting low every 14.44ms once with 52us low.

Kindly check the screenshots attached for the reference

  • Observations:

    Its stuck at boot rom and getting reset with watch dog. When I manually selected EMU Boot Mode Select as EMU_BOOT_FLASH then its going to flash otherwise its in reset condition. I have few doubts,

    1. Is it required to select EMU Boot Mode Select as EMU_BOOT_FLASH every time (as I don't do with 28377s)?

    2. When its entered into application code, its getting stuck at us_delay routine, When I replaced all the inbuilt DELAY_US() routines with normal for loops then its running normally, Anything do we need to do in 28384s (f2838x_usdelay.asm) as I dont see the issue in 28377s?

    Thanks,  

  • Hi,

    Sorry for late response.

    1. Is it required to select EMU Boot Mode Select as EMU_BOOT_FLASH every time (as I don't do with 28377s)?

    It is required if you are connected to JTAG (CCS)

    2. When its entered into application code, its getting stuck at us_delay routine, When I replaced all the inbuilt DELAY_US() routines with normal for loops then its running normally, Anything do we need to do in 28384s (f2838x_usdelay.asm) as I dont see the issue in 28377s?

    I don't think it gets stuck there. It's just that whenever you halt CPU, it'll halt in side this function because execution of this function is bulk of the code runtime.

    Vivek Singh

  • Hi Vivek,

    I just wants to know why we need to select Boot Mode as EMU_BOOT_FLASH every time where as with 28377s it's not required. What's the difference in emulation boot with 28377s and 28384s?