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.

TMS320F28379D: Booting not working

Part Number: TMS320F28379D


Tool/software:

Hi, I have two TMS320F28379D controller of different lot number. i have checked TMS320F28379DPTPS $7C-35AJGLW G4 on one hardware. Burn .out files on CPU1 and CPU2 and it is working properly even after power reset. But on the same hardware when I use TMS320F28379DPTPS   G4, it is working only if I debug the code. If i burn its flash with same .out file and power reset it, it stops working. What could be the difference in these two controllers of different batch lot?Here I have attached file for working and nonworking controller values range from 0x5D00C up to length of 512 bytes. 1 byte = 16 bits here and all data are in 16 bit hex TI format. Compare both files and let me know what could be the issue? Also can you describe the marking details for 3LC-4AAJQHW G4 vs $7C-35AJGLW G4?

//============== Working ($7C-35AJGLW)==========//

0x5D074 - DevCfgRegs_FUSEERR
0000    0000
0000    0000    D029    0C01    EFE3    0C55    0000    0000    0002    3DCE    0000    0000    0000    0000

0x5D1A0    - AnalogSubsysRegs_INTOSC1TRIM
0273    002A
0x5D1A2    - AnalogSubsysRegs_INTOSC2TRIM
0274    002C    0000    0000    0000

0x5D1AE    - AnalogSubsysRegs_LOCK
0000    0000    0000    0000    0000    0000    83F2    03FF
0x5D1B6    - AnalogSubsysRegs_ANAREFTRIMA
7328    0000
0x5D1B8    - AnalogSubsysRegs_ANAREFTRIMB
7B63    0000
0x5D1BA    - AnalogSubsysRegs_ANAREFTRIMC
7C25    0000
0x5D1BC    - AnalogSubsysRegs_ANAREFTRIMD
7425    0000    7BA9    0000    207F    0002    42F0    0000    0000    7000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000

//============== Not Working (3LC-4AAJQHW G4)==========//

0x5D074 - DevCfgRegs_FUSEERR
0000    0000
0000    0000    D009    0C01    EF72    0C09    0000    0000    0002    3D52    0000    0000    0000    0000

0x5D1A0    - AnalogSubsysRegs_INTOSC1TRIM
0231    002D
0x5D1A2    - AnalogSubsysRegs_INTOSC2TRIM
0247    0030    0000    0000    0000

0x5D1AE    - AnalogSubsysRegs_LOCK
0000    0000    0000    0000    0000    0000    836C    03FF
0x5D1B6    - AnalogSubsysRegs_ANAREFTRIMA
73EA    0000
0x5D1B8    - AnalogSubsysRegs_ANAREFTRIMB
7BB0    0000
0x5D1BA    - AnalogSubsysRegs_ANAREFTRIMC
7C26    0000
0x5D1BC    - AnalogSubsysRegs_ANAREFTRIMD
7426    0000    7BE9    0000    207F    0002    42F0    0000    0000    7000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000    0000
0000    0000    0000    0000    0000    0000    0000    0000    0000

NOTE: I am using same hardware and same .out files for both controllers. So problem of hardware and .out files can be ignore

  • Hello,

    To clarify, you are seeing the program run without issue when you are connected to the device; however, when you attempt to reset the device and allow standalone boot to flash, you see an issue, but in only one of the devices?

    A few questions:

    1. Are you able to connect to the device after you see an issue booting standalone?
    2. Have you tried connecting to the device and running emulation boot to see if the issue is still seen? 

    Best Regards,

    Allison

  • Hi,

    Are you able to connect to the device after you see an issue booting standalone?

    Yes

    Have you tried connecting to the device and running emulation boot to see if the issue is still seen? 

    Yes, I tried to debug it again using xds200 Debug Probe and it successfully start debugging.

    Also i tried Pull up resistor on GPIO72 and GPIO84. By doing this, it solve my issue. But My problem is When i used TMS320F28379DPTPS $7C-35AJGLW G4 controller, there was no pull up on these two pins still it was booting properly at power on/off reset. But when I used TMS320F28379DPTPS 3LC-4AAJQHW G4 controller on same hardware, it was not booting but debugging is working. So I want to know, why same controllers are working differently in booting. Both should work similarly. Is there any other way to boot TMS320F28379DPTPS 3LC-4AAJQHW G4 without pull up on GPIO72 and GPIO84?

  • Hi Dhaval,

    GPIO72 and GPIO84 are the default boot mode pins for the F28379D, so these pins need to be at defined logic levels during power-up/reset to properly configure the boot mode. It is always recommended to use external pull-up resistors on boot mode pins for reliable operation.

    While some devices may have sufficient internal pull-up strength to work without external pull-ups (e.g. the device you have that can boot without external), these internal pull ups are weak and this should not be relied upon. For consistent and reliable operation across all devices, external pull-up resistors should be used.

    Alternatively, you can also configure zero-boot-pin boot mode using the Device Boot Configuration in the TRM- i.e. program OTP so that the device will not even check the boot pins.

    Please refer to this other E2E regarding the boot pins and using external pull ups:  TMS320F28379D: About boot mode pin settings of TMS320F28379D  

    Best Regards,

    Allison