AM2612: How to make Custom Flash Download BSL

Ted Huh

Part Number: AM2612
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG

Hello Champs,

I want to download the firmware to the custom board's flash so I did below.

(got the flash parameters using ospi_flash_diag, and confirmed these flash parameters working well with application code)

import "flasher_jtag_uniflash_am261x-lp_r5fss0-0_nortos_ti-arm-clang" and changed the flash settings and built the image - flasher_jtag_uniflash_am261x-lp_r5fss0-0_nortos_ti-arm-clang.out
import "sbl_ospi_multicore_elf_am261x-axium_r5fss0-0_nortos_ti-arm-clang" and changed the flash settings and built the image
load custom flasher -> built in 1.
load SBL, built in 2 "sbl_ospi_multicore_elf_am261x-axium_r5fss0-0_nortos_ti-arm-clang.tiimage"
load application "hello_world_board_syscfg_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf"
Download

But it fails download.

Is there something wrong with this sequence?

Regards,

Ted

12 days ago

+1 Nilabh Anand 12 days ago

TI__Guru 59390 points

Hi Ted,

Sequence is correct,

Can you do one more step before this

-> Run OSPI flash io example, validate that read /write to flash is working properly, once this is done, follow the steps again

For your reference:

e2e.ti.com/.../faq-am2612-unable-to-program-on-custom-board

0 Ted Huh 12 days ago in reply to Nilabh Anand

TI__Expert 3475 points

OSPI flash io example works okay with parameters.

I will try with reference e2e you shared.

-Ted

0 Nilabh Anand 12 days ago in reply to Ted Huh

TI__Guru 59390 points

Sure let me know how it goes.

0 Ted Huh 11 days ago in reply to Nilabh Anand

TI__Expert 3475 points

Hello Nilabh,

While I was running ospi_flash_io example, while following your guide I found the issue.

It turns out the clock setting has some problem. because customer is using ZNC 500MHz, I divided OSPI clock into 100MHz.(Flash supports up to 133MHz) but it makes runtime error.(no build error at all)

Cortex_R5_0: ASSERT: 0.4s: soc/am261x/soc_rcm.c:SOC_rcmGetModuleClkDivVal:1650: actOutFreq == outFreq failed !!!

but when I set the OSPI clock to 83.33MHz, which can be generated by 400MHz device, it passes. I think soc_rcm.c does not fit for the 500MHz device. it should be fixed. I will release SBL using 83.33MHz but I hope this will be fixed in the future.

Regards,

Ted

0 Ted Huh 11 days ago in reply to Ted Huh

TI__Expert 3475 points

83.33MHz is not related to the 400MHz... sorry for the confusion. is there special condition to select the proper clock?

Regards,

Ted

+1 Nilabh Anand 7 days ago in reply to Ted Huh

TI__Guru 59390 points

Ok, Could you clarify what is the last question

0 Ted Huh 7 days ago in reply to Nilabh Anand

TI__Expert 3475 points

by selecting divider, I can generate 125MHz and 100MHz also, but it makes error below, only 83.33MHz does not make issue.

Cortex_R5_0: ASSERT: 0.4s: soc/am261x/soc_rcm.c:SOC_rcmGetModuleClkDivVal:1650: actOutFreq == outFreq failed !!!

Is there a rule to decide memory base clock? Sysconfig does not show any error.

Regards,

Ted

+1 Nilabh Anand 7 days ago in reply to Ted Huh

TI__Guru 59390 points

Hi Ted,

This is a known issue, due to incomplete support for ZEJ/ZNC package, we will fix this in next sdk release.

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2612: How to make Custom Flash Download BSL