SK-AM62-LP: Regarding Application Image Creation which is loadable by SBL in OSPI NOR Boot mode

Pradeep R

Expert 1100 points

Part Number: SK-AM62-LP
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello Team,

we are using OSPI NOR Boot mode for SK-AM62-LP board.

we are want run our application in Stand alone mode in R5 Core.

Can you please let us know the memory handling between SBL and Application because we are using SBL in OSPI NOR boot mode. we want what should be the address of vector table for application and also when SBL boots to which DDR address the application will be copied and also to which TCM memory the vector table will be copied.

As per TI document, we got to know that for SK-AM62-LP board, we need to generate hs_fs image.

we tried converting application elf to rprc image and then rprc image to hs_fs image.

Can you please let us know the steps to convert to these images.

we have the default SBL cfg file with following images for OSPI NOR mode

# First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
--flash-writer=image/sbl_uart_uniflash_stage1.Release.hs_fs.tiimage

# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files
# Please note this binary is copied to DDR by sbl_uart_uniflash_stage1 and not written to any boot media like flash or eMMC
--file=image/sbl_uart_uniflash_stage2_am62x-sk-lp_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x0

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
--file=image/sbl_ospi_nor_stage1.Release.hs_fs.tiimage --operation=flash --flash-offset=0x0

# DM image is flashed at 0xa00000 or to whatever offset your bootloader is configured for
--file=image/Application.appimage.hs_fs --operation=flash --flash-offset=0xA0000 -----> for R5 core with our application

Is this Cfg file correct to boot multiple cores with app image in OSPI NOR mode?

For rprc generation :

cd ${SDK_INSTALL_PATH}/tools/boot/out2rprc

${NODE} elf2rprc.js {input application executable file (.out)} here what should be the value of Node

For Hs_fs image generation :

cd ${SDK_INSTALL_PATH}/tools/boot/signing
$(PYTHON) appimage_x509_cert_gen.py --bin <path-to-the-binary> --authtype 0 --loadaddr 84000000 --key <signing-key-derived-from-devconfig> --output <output-image-name> --keyversion 1.5
on what basis we should select load address and also how to select core name or Core id
Can you please provide feedback for above queries.
Thanking you.

Regards,

Pradeep R

2 days ago

0 Meet Thakar 1 day ago

TI__Genius 10935 points

Hi Pradeep,

Pradeep R said:
we want what should be the address of vector table for application and also when SBL boots to which DDR address the application will be copied and also to which TCM memory the vector table will be copied.

This is usually defined in the linker file of the application: mcupsdk-core-k3/examples/hello_world/am62x-sk-lp/r5fss0-0_freertos/ti-arm-clang/linker.cmd at k3_main · TexasInstruments/mcupsdk-core-k3 · GitHub

Pradeep R said:
we tried converting application elf to rprc image and then rprc image to hs_fs image.

You can use MCU+SDK tools here:

So the steps would be converting .out to .rprc:AM62x MCU+ SDK: Booting Tools

Then generate the multicore appimage: AM62x MCU+ SDK: Booting Tools

For HS-FS/HS-SE devices you will also have to sign the image using signing script provided in the MCU+SDK: AM62x MCU+ SDK: Booting Tools

Pradeep R said:
on what basis we should select load address and also how to select core name or Core id

This load address is where the SBL temporarily load the appimage for authentication: mcupsdk-core-k3/examples/drivers/boot/sbl_ospi_nand_multistage/sbl_ospi_nand_stage2/am62x-sk-lp/r5fss0-0_nortos/ti-arm-clang/linker.cmd at k3_main · TexasInstruments/mcupsdk-core-k3 · GitHub

There is no need to change this address and should be kept as it is.

You can find core ids in the Multicore Appimage Gen guide I shared previously.

Best Regards,

Meet.

0 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

Thanks for the feedback.

we have few more questions

1 Do we need SBL Stage 2 tii image for this?

2 Can we use same SBL NAND tiimages for OSPI NOR flash as well?

Regards,

Pradeep R

0 Meet Thakar 1 day ago in reply to Pradeep R

TI__Genius 10935 points

Pradeep R said:
1 Do we need SBL Stage 2 tii image for this?

Yes, you need both SBL stage-1 and stage-2 for this: AM62x MCU+ SDK: SBL Booting Linux From OSPI

Pradeep R said:
2 Can we use same SBL NAND tiimages for OSPI NOR flash as well?

No, this would not work. SBL OSPI NAND example was made for am62x-sk-lp board which has a NAND flash, so it has a different flash configuration to support the NAND flash on that board, the same would not work for an OSPI NOR flash.

0 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

Can you please share us the SBL OSPI NOR Flash ti images for both Stage 1 and Stage 2?

Regards,

Pradeep R

0 Meet Thakar 1 day ago in reply to Pradeep R

TI__Genius 10935 points

It is available as the part of the MCU+SDK, which EVM are you using?

0 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

we are using mcu_plus_sdk_am62x_10_01_00_33

we did not find any SBL OSPI NOR images

EVM : SK-AM62-LP board

Regards,

Pradeep R

0 Meet Thakar 1 day ago in reply to Pradeep R

TI__Genius 10935 points

SK-AM62-LP has a NAND flash not a NOR flash, that is why only SBL OSPI NAND example is available for this board.

0 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

Our customer soldered OSPI NOR flash on this board.

So Should we ask our customer share this as well or can we generate this ?

Regards,

Pradeep R

0 Meet Thakar 1 day ago in reply to Pradeep R

TI__Genius 10935 points

You can ask them to use SBL OSPI example for am62x-sk, which is based OSPI NOR flash S28HS512T. If they are using a different flash then you can ask them to refer to this guide on how to add support for custom flash: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/11_01_00_16/exports/docs/api_guide_am62x/CUSTOM_FLASH_SUPPORT_GUIDE.html

+1 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

Sure, thankyou for the feedback

Regards,

Pradeep R

0 Pradeep R 1 day ago in reply to Pradeep R

Expert 1100 points

Hello Meet,

one more question, for hs_fs image shoould we use multicore image generator or signing image generator

Regards,

Pradeep R

0 Meet Thakar 1 day ago in reply to Pradeep R

TI__Genius 10935 points

Hi Pradeep,

To generate the HS-FS Multicore application image, you have to follow both the steps. First you generate the .appimage containing rprc for different cores, and then you sign this appimage using signing scripts to generate the .appimage.hs_fs binary.

0 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

Sure, thankyou for the feedback

Regards,

Pradeep R

0 Pradeep R 1 day ago in reply to Pradeep R

Expert 1100 points

Hello Meet,

For SBL images or examples which is loaded by SBL, we use a different signing script. This is solely because of the x509 certificate template differences between ROM and SYSFW. In GP devices appimages are not signed. The signing happens only in HS devices. The script usage is:

cd ${SDK_INSTALL_PATH}/tools/boot/signing
$(PYTHON) appimage_x509_cert_gen.py --bin <path-to-the-binary> --authtype 0 --loadaddr 84000000 --key <signing-key-derived-from-devconfig> --output <output-image-name> --keyversion 1.5
Here what should be the signing-key-derived-from-devconfig , Is it In the case of HS device, BOOTIMAGE_CERT_KEY is custMpk_am62x .pem
Regards,
Pradeep R

0 Meet Thakar 1 day ago in reply to Pradeep R

TI__Genius 10935 points

Pradeep R said:
Here what should be the signing-key-derived-from-devconfig , Is it In the case of HS device, BOOTIMAGE_CERT_KEY is custMpk_am62x .pem

Regards,

Yes, this is correct.

0 Pradeep R 1 day ago in reply to Meet Thakar

Expert 1100 points

Hello Meet,

Sure, thankyou for the feedback

Regards,

Pradeep R

0 Pradeep R 1 day ago in reply to Pradeep R

Expert 1100 points

Hello Meet,

we have followed these steps to generate final HS_FS app image for SK-AM62-LP board for R5 core

1 ELF to RPRC
C:\ti\mcu_plus_sdk_am62x_10_01_00_33\tools\boot\out2rprc>"C:\ti\ccs1281\ccs\tools\node\node.exe" elf2rprc.js "C:\Projects\workspace\simple_demo_eth_rte_IPv6\output\bin\ARM_AM62XXCR5_simple_demo_eth_rte_IPv6.elf" 0x0A010021

here for rprc : it was asking node , so i gave path of node exe from CCS. Is this correct ?

2 RPRC to APP_IMAGE
C:\ti\mcu_plus_sdk_am62x_10_01_00_33\tools\boot\multicoreImageGen>"C:\ti\ccs1281\ccs\tools\node\node.exe" multicoreImageGen.js --devID 55 --out "C:\Projects\workspace\simple_demo_eth_rte_IPv6\output\bin\ARM_AM62XXCR5_simple_demo_eth_rte_IPv6.appimage" "C:\ti\mcu_plus_sdk_am62x_10_01_00_33\tools\boot\out2rprc\ARM_AM62XXCR5_simple_demo_eth_rte_IPv6.rprc"@4

3 APP_IMAGE to HS_FS_IMAGE
C:\ti\mcu_plus_sdk_am62x_10_01_00_33\tools\boot\signing>python appimage_x509_cert_gen.py --bin "C:\Projects\workspace\simple_demo_eth_rte_IPv6\output\bin\ARM_AM62XXCR5_simple_demo_eth_rte_IPv6.appimage" --authtype 0 --loadaddr 84000000 --key custMpk_am62x.pem --output "C:\Projects\workspace\simple_demo_eth_rte_IPv6\output\bin\ARM_AM62XXCR5_simple_demo_eth_rte_IPv6.appimage.hs_fs" --keyversion 1.5

Are these steps correct?

Regards,

Pradeep R

0 Meet Thakar 16 hours ago in reply to Pradeep R

TI__Genius 10935 points

Hi Pradeep,

The steps seem correct, by the way you don't explicitly need to do these steps if you are trying to generate an image using default makeflle, as these are already taken care of, see makefile of hello world as an example: https://github.com/TexasInstruments/mcupsdk-core-k3/blob/k3_main/examples/hello_world/am62x-sk/r5fss0-0_freertos/ti-arm-clang/makefile

You can check this as a reference.

Processors

Processors forum

SK-AM62-LP: Regarding Application Image Creation which is loadable by SBL in OSPI NOR Boot mode