TMS320F28379D: Configuring OTP BOOTCTRL for flash boot using new boot pins

Hi Neil,

Did you try setting the emulation boot with same value  (refer section "4.7 Configuring Emulation Boot Options" in device TRM) and see if it works with emulator connected. This will make sure all the boot pin settings are proper. You need to follow below steps -

• Connect to CCS. 
• Issue reset from debugger (CCS)
• Write correct emulation boot value at 0xD00
• Click on "Run"

This should boot to your code. If not then you need to check where it's stuck.

Regards,

Vivek Singh

If this works fine and still standalone does not work then you should try to emulate standalone by writing 0xFF5A at 0xD00 location and the run after reset. In this case it'll use the BOOT setting programmed in OTP (just like in standalone mode but with debugger connected) and you should be able to debug it using CCS.

Regards,

Vivek Singh

Vivek,

Thank you for the information.  Emulating the standalone boot is exactly what I need (to verify my settings before loading my actual hardware).  However, I am having trouble doing this on the launchpad.  Am I missing some step:

I programmed the Z2-BOOTCTRL OTP register with the code above (0x03040B5A) so GPIO2 and GPIO3 should be my boot pins.  I connect to the Launchpad with CCS and before running it, I put $FF5A into $D00. If the boot pins are tied to 3.3v or GND it seems to make no difference: 1. it runs normally when I hit the run button in CCS in both cases.  2. If I try hitting the hardware reset button in either case, the processor does not run (the blinking lights stops blinking).  3. If I hit the CPU reset button in CCS it stops working as well in both cases and does not run.  Is there an extra step that I am missing for testing this? I am reluctant to potentially ruin my prototype before properly testing this.

I am connecting the 3rd and 4th pin down on the J4 connector (numbered 37 and 38 on the board) with jumper wires to either 3.3v or GND.: They should be GPIO2 and GPIO3

Thank you for the help.

Regards

Neil

Hi,

NEIL SINGER said:

If the boot pins are tied to 3.3v or GND it seems to make no difference: 1. it runs normally when I hit the run button in CCS in both cases.

Are you loading the code after connecting to CCS and then running it ? If yes then you should not be doing that. Just reset the CPU from debugger and then click on "Run" without loading the code.

Regards,

Vivek Singh

Vivek,

I created a debug configuration which only loads symbols. I connect to the Launchpad and load $FF5A into $D00 and hit CPU Reset button followed by the run button.  nothing happens with boot pins connected to 3.3v or GND. If I hit the restart button and then run, the code runs in either case. 

Regards

If it's not running then there is issue. You need to halt the CPU and debug where it's stuck.

When I connect, It immediately looks like this and cannot run:

If I do  a Restart it looks like this:

This make sense but it bypasses any boot options (I guess).  It is definitely not loading code and only connecting. What does a Restart do? What sequence should I be doing.

Regards

I tried to use what was posted here: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/786691/ccs-tms320f28377s-changing-boot-pins-via-bootctrl-emu_bootctrl

If I set the EMU-BOOT to $0b5A in $D00, I hit CPU Reset and then Run,  it boots from flash as expected , however, it does not matter what the boot pins are set to.  This seems to test that the 0B mode is correct but does not test the functionality of the boot pins.

I even tried using $FE5A in $D00 which should use the boot pins to decide on an action.  This does not run no matter what the boot pins are set to.

Regards

Yes, if you set the emulation boot as flash boot then it ignores the BOOTPIN value so it works fine. Also incase of "Restart" CCS forces the PC to project entry point hence it runs fine. Look like there is some issue how you have setup the BOOTPIN or BOOTPINs are not driven properly. Once you connect to CCS, check the GPIO data register in CCS register view and see what value it's capturing for BOOTPIN GPIO. 

Regards,

Vivek Singh

Vivek,

This makes no sense.  I set $D00 to $0b5a and connect to the card, hit run, and it boots and runs.  I set $FE5A in $D00 and it does not boot. I wired BOTH sets of boot pins, GPIO2 and GPIO3 (set in Z2) AND GPIO72 and GPIO84 (default).  Why is this not working?  or What else can I try? See below.

Regards

Neil,

Have you program any value in Zone1 (Z1-BOOTCTRL) OTP locations ?

Regards,

Vivek Singh

Zone 1 was never programmed.

thanks

This is strange then. Other thing to look at is the entry point of project. Where is code_start placed in .map file ?

Just wanted to check if you were able to resolve this issue ? If you have any further queries, please let us know. 

The map file looks like this.  I never got it working.

codestart 

*          0    00080000    00000002     

                  00080000    00000002     F2837xD_CodeStartBranch.obj (codestart)

I am about to try it on a custom board to see if it has anything to do with the Launchpad and/or the demo code.  I'll let you know how it goes.  Thank you.

OK, thank you.