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.

How to design the circuit when EMIF1 ,SCI and SCI-boot0 are used ?

Other Parts Discussed in Thread: TMS320F28377D, CONTROLSUITE

Hi ,

The product use SCI to communication on SCI-BOOT0 pins(GPIO84,GPIO85).
Only a SCI port is on the product.
TMS320F28377D SCI-BOOT0 SCIRXDA (GPIO85) and EM1D0 are the same pin.
This situation has a conflict between SCI and EMIF1 .

How to design the circuit when EMIF1 ,SCI and SCI-boot0 are used ?
(when MP, does not want off-line programming OTP to change SCI pin define.  )

best regards,
Simen

  • Hi Simen,

    Can EM1D0 be muxed with any other pin? If not then you hardly have any choice but to shift your SCI pins to other muxed GPIO instead of 85.

    Regards,
    Gautam
  • Hi Simen,

    A few thoughts (some which you may already comprehend):

    1. You are correct - there is a conflict which may cause contention.
    2. There is a method in place so that during production a customer can program the OTP.  If done correctly, the boot mode will then use a different set of SCI pins (namely GPIO28, GPIO29).
    3. Note that the SCI boot-loading pins will only be utilized at power up AND when the boot pins configure the device to use SCI boot mode.  In all other circumstances, these pins may be used in other ways - such as for EMIF. 
    4. During mass production programming, you could have the first portion of your flash program be a partial bootloader.  You could refer to the boot ROM code in controlSUITE (particularly the code in SCI_Boot.c) as a reference.  This would enable your customer to potentially use any GPIO (and SCI module) for bootloading.
      \controlSUITE\libs\utilities\boot_rom\F2837x_revb\


    Thank you,
    Brett

  • Gautam and Brett, thanks for your answer.

    I decide to use bus switch for this case.

    Simen