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.

TMS320F28388D: GPIO72 conflict with EMIF1 data line 12 ( boot mode at startup with external RAM in circuit)

Part Number: TMS320F28388D

Tool/software:

Hello All, 

We are designing an extremely compact board with F28388D , and using a 16bit SDRAM, per user manual the only available pin for "External memory interface 1 data line 12" is GPIO72.

So now having a SDRAM connected to GPIO72, what will happen in start-up to boot mode? will we end up in some unknown boot mode situation? -- If yes, what to do?

For us, we want the application to work like below ideally:

  1. Turn ON the device
  2. The USB Boot loader looks at a single specific GPIO, if that pin is LOW, we go to DFU mode, if not we load the program from Flash to RAM and execute normally
  3. If we are in DFU mode, we will wait for the application to update the firmware through USB
  4. if the firmware is updated, we ask the user to recycle the power and put that DFU GPIO in high state
  5. After power recycling the device runs with updated Firmware

This is pretty much what we did before with other DSPs ( F28069 ), and it works great.

Having this context in mind, how should we deal with GPIO72 that is shared with EMIF1 ?

John

  • Hi,

    In the TRM, we have a section called 'Device Boot Configurations'.

    You will be able to set up F28388D so that it only uses 1 boot pin.

    Then you can select which two boot modes are selected by this boot pin.

    Best Regards,

    Ben Collier

  • Thank you @Benjamin Collier, so basically the first thing we do with a new DSP should be programming the OTP through a JTAG, selecting properly the Boot pins, and then from that point on we will be good to go? -- so there will be no need to worry about GPIO 72's conflict with EMIF?

    John

  • John,

    basically the first thing we do with a new DSP should be programming the OTP through a JTAG, selecting properly the Boot pins, and then from that point on we will be good to go?

    Yes that's right. On an unprogrammed device, this should not be an issue. You should be able to connect regardless of the boot mode.

    Best Regards,

    Ben Collier