AM625: AM623+mcu+sdk

Hi,

Line 20 is a command to flash stage 2 bootloader. For that, you need to build the Stage 2 bootloader appimage. You can run the following command from the root directory of mcu_plus_sdk_am62x_08_04_00_16 to build the required appimage.

$(MAKE) -s -C examples\drivers\boot\sbl_uart_uniflash_multistage\sbl_uart_uniflash_stage2\am62x-sk\r5fss0-0_nortos\ti-arm-clang all

where $(MAKE) is the command to executable make build system.

Regards,

Prashant

I solved the above problem through the way you provided, thank you very much, but then there was a problem in the transmission of the third file, as shown in the figure

Hi,

Please power cycle the board and then again try flashing. Also, you can skip this operation as this just tunes the OSPI to enable better performance. Skipping this should not cause any problem.

Regards,

Prashant

Following your advice, I closed the transfer of this file, but the next file that followed could not be transferred either. I tried to restart the development board and found that the corresponding directory did contain this tiimage, but the transfer failed

Hi,

Could you please try flashing to eMMC instead of OSPI to narrow down the issue. Change the operation type to flash-emmc as shown:

Do power cycle the board before flashing. Please follow the steps to power cycle at below link and confirm the C characters getting printed before flashing.

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/latest/exports/docs/api_guide_am62x/EVM_SETUP_PAGE.html#EVM_FLASH_SOC_INIT

Regards,

Prashant

I now all the operations are based on software-dl.ti.com/.../EVM_SETUP_PAGE.html M_SOC_INIT this step comes from (which is the user guide you provided) every time you execute python uart_uniflash.py -p COM10 --cfg=sbl_prebuilt/am62x-sk/default_sbl_null.cfg

I always make sure to close the serial port after printing c on the serial port. I can confirm that this step is OK. The development board I am using now has been used by other colleagues before, which is normal, but his startup mode is sd card. I changed the corresponding position in default_sbl_null.cfg to emmc, but it still doesn't work, and the transmission still cannot be done. I don't know if you mean to change the mode to emmc

Hi,

It seems you have solved this problem. Can you please tell us how did you solve the problem which will benefit others also.

Regards,

Prashant

I did not solve this problem. I just changed the way to initialize the flash memory and did not start it in this way. In addition, I would like to know the reason why xds110 could not be connected when I tried to debug m4 kernel

张宝山 张 said:

I just changed the way to initialize the flash memory and did not start it in this way.

Can you please elaborate more on this.

About the other issue, we can take it on that other thread.

Regards,

Prashant

The purpose of sending these files is to normally start the whole chip and debug it. I replaced it with an sd card to initialize the chip as normal. The m4 kernel can be started normally through the sd card and can be seen in the command line