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.

28F37xD SCI boot pins

Other Parts Discussed in Thread: CONTROLSUITE

Hello,

I'm using the F2837x controlCARD and want to use SCI-A to flash the device through bootloader.

Standard pins of SCI-A are GPIO84 & GPIO85 (TX & RX).

I want to use GPIO28 & GPIO29 instead. Is there a way to change this in the bootloader?

Regards,

Bart

  • Hi Bart,

    You can use the SCIBOOT1 boot mode, which is on GPIO28 & GPIO29. To use this mode, you would need to program the appropriate value into the OTP_BMODE and set your control card boot pins to GetMode.

    See sections 2.10 and 2.20 of SPRUHM8.

    Regards,

    Sam

  • yes, you can use EMUBOOT procedure and run bootROM with debugger connected before you program the OTP.

    once the OTPBMODE is programmed device would always boot to that boot mode when in GETMODE. So if this doesn't fit well in your design you might have to implement the SCI BOOT in your application, you can refer to the ROM Sources released in controlSuite (C:\ti\controlSUITE\libs\utilities\boot_rom\F2837x_rev0)

     

    Best Regards

    Santosh

     

  • Thx for the response.

    What I want to reach is to reasign the bootpins and use SCIBOOT1 when pins are assigned to SCI Mode.

    When Get mode is selected the device should start the program in FLASH BOOT like in the default state.

    Is this possible with OTPBMODE?

    Regards,

    Bart

  • If you program SCIBOOT1 option in OTPBMODE then the device would always boot to SCIBOOT1 when GETMODE option is selected on the boot mode pins. It will boot to flash only if a BAD KEY (!=0x08AA) is received from the SCI or you can send a specific HEX file over SCI which would make the device branch to flash, but if you are willing to send something over SCI when you want the device to boot to flash I would suggest you to send a bad key after autobaud lock.

    You can also go corrupt the OTPKEY in the OTPBOOTCTRL to let the device always boot to flash after you are done with the SCIBOOT1. But if you have a requirement of jumping between boot-to-flash and boot-to-SCIBOOT1 via the GETMODE function then you will have to use the procedure defined in above para. or you have to allways boot to flash (not program SCIBOOT1 in OTPBMODE) and implement the SCIBOOT1 function in your application in flash.

     

    Hope this helps.

     

    Best Regards

    Santosh