AM2634: Lauterbach startup script and AM263x

Hi,

I'm consulting on this internally and will get back with you soon.

Regards,
Frank

Hi,

Panda Bear said:

Is that an expected behavior? 

I got this feedback from the person that developed the script:

The script allows burning the main array of flash in a freeform way. I did not try to burn flash using all boot mode combinations.  My main goal was to verify the board and flashing could function from JTAG.  Burning for other boot modes may require some extra system level setup to do work the ROM may have done or due to different option which present in other modes.   For JTAG burning, there sometimes is a complication if the software on the target configures the clocks or flash controller for flash part in a way which is not compatible with what the simple jtag script assumes.  JTAG scripts don’t ‘deconfigure’  every possible setting before burning.  The typical way to make things work is to ensure a ‘safe-clean’ start point.  Often a DIP switch setting to known startup mode is used.  In the case of uniflash we usually require a UART boot with a known small startup.  The other action which is sometimes needed is NVRAM inside the flash part may need to be changed so that it matches what the ROM expects.  This is a burn step beyond the main flash array.  Depending on the part buffer-slew and at-boot-width options exist which can be vendor specific.

Lauterbach offers 2 flash burning APIs, FLASHFILE and FLASH.  Serial flashes uses FLASHFILE and ones which can like linear nor use FLASH (some serial-nor flashes can use either).  The FLASH API allows an option to direct elf loading into a final memory like MCU users are familiar with where FLASHFILE requires you to know the layout of the boot flow to burn flashes.  TIBOOT3 goes to this address, SBL goes to this address the ...

Panda Bear said:

and how can I run the code from flash?

Panda Bear said:

are there more steps after loading the code into flash? 

 Please see these docs concerning boot:

• https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/08_05_00_24/exports/docs/api_guide_am263x/BOOTFLOW_GUIDE.html#autotoc_md302
• https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/08_05_00_24/exports/docs/api_guide_am263x/EXAMPLES_DRIVERS_SBL_QSPI.html

These docs describe the JTAG flashing tools in MCU+SDK:

• https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/08_05_00_24/exports/docs/api_guide_am263x/TOOLS_FLASH.html#BASIC_STEPS_TO_FLASH_FILES
• https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/08_05_00_24/exports/docs/api_guide_am263x/EXAMPLES_DRIVERS_SBL_JTAG_UNIFLASH.html

You'd need to program the SBL QSPI and your application to flash at the required offsets. These are the required offsets:

• SBL QSPI: 0x0
• application: 0x80000

After that, you'd set the boot switches for QSPI boot.

Please let me know if this answers your questions.

Regards,
Frank