Bootloader on 'F28377

Brain,

Brian Fortman said:

For programming the C2000 TMS320f28377  in serial mode (for production and other without jtag interface) please advise what is the best method to use.
In the previous project using TMS320F28355  we used SDFLASH as specified in application note (SPRAAL3).
Can you check for configuration for SDFLASH .driver file  and project file (algorithm file)?

For above:-

On a production board, we should advise customers to use GPIO84, GPIO85 as SCI pins. 

We have examples in our controlSuite (C:\ti\controlSUITE\device_support\F2837xD\v190\F2837xD_examples_Dual\F2837xD_sci_flash_kernels) and this app note (http://www.ti.com/lit/an/sprabv4a/sprabv4a.pdf ) should help.

The SCI Boot mode on F2837x is backward compatible with F28355, so the host tools should work as long. The differences are GPIOs and probably the memory map of the device.But the HEX format that the loaders use should be able to handle that.

Brian Fortman said:

Programming using SCI:
in the EB the SCI is connected to GPIO 28,29.
I didn’t manage to program the flash through the SCI until I configured the device through JTAG to work with this SCI.
Even when I soldered  the SCI to GPIO 84,GPIO 85 I didn’t manage to program.
In my design I am using EMIF SRAM 16 bit and GPIO 85 is assigned to XD0 .I get pin conflict if I try to use the SCI in GPIO 84,GPIO 85 .(GPIO 84 is already BOOTMODE 1).

For Above:- 

There are two problems above, if customer moves to GPIO28 and GPIO29 for SCIBOOT then this works for the HW mapping? the question is how to use GPIO28 and GPIO29 for SCIBOOT.

If customer wants to use GPIO28/GPIO29 for SCIBOOT then there are two ways.

1.> He can program the OTPBMODE to use SCIBOOT2, but then he will loose the boot to flash. 

2.> He can always boot to flash (leaving the OTPBMODE unprogrammed or by programming it to boot to flash) and in the flash application customer can determine if there is a need for FW upgrade and start SCIBOOT2.

Now, in the second scenario is customer saying that he cannot use GPIO84/85 for SCIBOOT because of pin conflict? Does EMIF has to be active during BOOT? Can the pin be both SCI and EMIF depending on SW set up?

Also on this device, customer can change the default boot mode select pins by programming OTP. So for ex: he can program OTP such that boot ROM reads GPIO 72 for Bootmode pin1 and the same for Boot mode pin2. So if GPIO72 is pulled HIGH then device will boot to flash. 

Hope this helps.

Best Regards

Santosh Athuru

Hello Santosh,

1.Can I use SCI GPIO 84 & GPIO 85 with EMIF1 (Pin conflict on GPIO85)?

2.Can I use "C2PROG" in order to program TMS320F28377D FLASH in SCI BOOT mode?

Best Regards,

Yaron

Hello Yaron,

Yaron bar said:

1.Can I use SCI GPIO 84 & GPIO 85 with EMIF1 (Pin conflict on GPIO85)?

on above, you will not be using EMIF1 when you are booting from SCI, would it be possible to simply connect the signal to both the SCI and EMIF and have EMIF disabled when using SCI and vice-versa? 

Yaron bar said:

2.Can I use "C2PROG" in order to program TMS320F28377D FLASH in SCI BOOT mode?

on above, I'm not sure on the latest, please check with C2Prog.

Hope this helps.

Best Regards

Santosh Athuru