AM2432: stuck in Sciclient_waitForBootNotification

sigong

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

Hi experts,

I'm facing a problem that the program is stuck in Sciclient_waitForBootNotification and the mcu is AM2432.

Before this,I had flashed 2 tiimage files successfully to my board via USB2.0 DFU in DFU BOOT MODE and the 2 files is sbl_dfu_uniflash.release.tiimage and sbl_ospi.debug.hs_fs.tiimage.

After that,I have set the board in OSPI BOOT MODE.

Because the flash my board uses is not S25HL512TFAMHI010 (that AM243x-LP uses) and its driver is not completed currently,so I want to debug the board to pefect drive code.

However,when I clicked the"load program ..." button and resume the code,I found it stuck in Sciclient_waitForBootNotification.

what's wrong with these steps or what operations I ignored?

Please tell me,thank you.

over 1 year ago

0 Prashant Shivhare over 1 year ago

TI__Guru 69741 points

Hi Sigong,

How was the flashing even successful if you don't have the working driver for your custom part?

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant，

The flash's driver is not completed currently.

Maybe I'm wrong because I just judge it from the information in the cmd window.

Here is the entire content.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Microsoft Windows [版本 10.0.19042.928]

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>python usb_dfu_uniflash.py --cfg=sbl_prebuilt/am243x-lp/default_sbl_null.cfg

Parsing config file ...

Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...

Found flash writer ... sending sbl_prebuilt/am243x-lp/sbl_dfu_uniflash.release.tiimage

----------------------------------------------------------------------------

Executing DFU command with alt_setting=0 interface=0 transfer_size=512

----------------------------------------------------------------------------

dfu-util 0.8

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to dfu-util@lists.gnumonks.org

Invalid DFU suffix signature

A valid DFU suffix will be required in a future dfu-util release!!!

Opening DFU capable USB device...

ID 0451:6165

Run-time device DFU version 0110

Claiming USB DFU Interface...

Setting Alternate Setting #0 ...

Determining device status: state = dfuIDLE, status = 0

dfuIDLE, continuing

DFU mode device DFU version 0110

Copying data from PC to DFU device

Download [=========================] 100% 310119 bytes

Download done.

state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present

state(2) = dfuIDLE, status(0) = No error condition is present

Done!

Sent flashwriter sbl_prebuilt/am243x-lp/sbl_dfu_uniflash.release.tiimage of size 310119 bytes in 1.95s. Bandwidth = 155.31kbps

Executing command 2 of 2 ...

Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_ospi.debug.hs_fs.tiimage --operation=flash --flash-offset=0x0

------------------------------------------------------

Waiting for DFU device to be enumerated ....

------------------------------------------------------

Waiting for DFU device to be enumerated ....

------------------------------------------------------

Waiting for DFU device to be enumerated ....

------------------------------------------------------

----------------------------------------------------------------------------

Executing DFU command with alt_setting=0 interface=0 transfer_size=512

----------------------------------------------------------------------------

dfu-util 0.8

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to dfu-util@lists.gnumonks.org

Invalid DFU suffix signature

A valid DFU suffix will be required in a future dfu-util release!!!

Opening DFU capable USB device...

ID 0451:6165

Run-time device DFU version 0110

Claiming USB DFU Interface...

Setting Alternate Setting #0 ...

Determining device status: state = dfuIDLE, status = 0

dfuIDLE, continuing

DFU mode device DFU version 0110

Copying data from PC to DFU device

Download [=========================] 100% 354717 bytes

Download done.

state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present

unable to read DFU status after completion

Sent sbl_prebuilt/am243x-lp/sbl_ospi.debug.hs_fs.tiimage of size 354685 bytes in 2.01s. Bandwidth = 172.32kbps

True

All commands from config file are executed !!!

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Could you tell me what works should be done next?

Thank you.

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

If the flashing is successful then the flash driver is mostly working.

The issue then comes because of using the wrong image. I see the flashing was successful with `sbl_dfu_uniflash.release.tiimage`. This means you are using a GP device otherwise the flashing itself wouldn't have been successful.

Since you are using GP device, you need to use the GP image for SBL OSPI. This is identified by `sbl_ospi.release.tiimage` (no `hs_fs` in the extension).

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

I have just tried with the `sbl_ospi.release.tiimage` file.

After that,I resumed the code again and found it stuck in Sciclient_waitForBootNotification.

Here is the debug view:

Here is the cmd window information:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Microsoft Windows [版本 10.0.19042.928]

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>python usb_dfu_uniflash.py --cfg=sbl_prebuilt/am243x-lp/default_sbl_null.cfg

Parsing config file ...

Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...

Found flash writer ... sending sbl_prebuilt/am243x-lp/sbl_dfu_uniflash.release.tiimage

----------------------------------------------------------------------------

Executing DFU command with alt_setting=0 interface=0 transfer_size=512

----------------------------------------------------------------------------

dfu-util 0.8

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to dfu-util@lists.gnumonks.org

Invalid DFU suffix signature

A valid DFU suffix will be required in a future dfu-util release!!!

Opening DFU capable USB device...

ID 0451:6165

Run-time device DFU version 0110

Claiming USB DFU Interface...

Setting Alternate Setting #0 ...

Determining device status: state = dfuIDLE, status = 0

dfuIDLE, continuing

DFU mode device DFU version 0110

Copying data from PC to DFU device

Download [=========================] 100% 310119 bytes

Download done.

state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present

state(2) = dfuIDLE, status(0) = No error condition is present

Done!

Sent flashwriter sbl_prebuilt/am243x-lp/sbl_dfu_uniflash.release.tiimage of size 310119 bytes in 1.93s. Bandwidth = 156.92kbps

Executing command 2 of 2 ...

Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_ospi.release.tiimage --operation=flash --flash-offset=0x0

------------------------------------------------------

Waiting for DFU device to be enumerated ....

------------------------------------------------------

Waiting for DFU device to be enumerated ....

------------------------------------------------------

Waiting for DFU device to be enumerated ....

------------------------------------------------------

----------------------------------------------------------------------------

Executing DFU command with alt_setting=0 interface=0 transfer_size=512

----------------------------------------------------------------------------

dfu-util 0.8

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to dfu-util@lists.gnumonks.org

Invalid DFU suffix signature

A valid DFU suffix will be required in a future dfu-util release!!!

Opening DFU capable USB device...

ID 0451:6165

Run-time device DFU version 0110

Claiming USB DFU Interface...

Setting Alternate Setting #0 ...

Determining device status: state = dfuIDLE, status = 0

dfuIDLE, continuing

DFU mode device DFU version 0110

Copying data from PC to DFU device

Download [=========================] 100% 299903 bytes

Download done.

state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present

unable to read DFU status after completion

Sent sbl_prebuilt/am243x-lp/sbl_ospi.release.tiimage of size 299871 bytes in 1.85s. Bandwidth = 158.29kbps

True

All commands from config file are executed !!!

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Additionally,I also tried a python script 'uart_boot_socid.py' to check the chip type.It shows the AM2432 in use belong to hsfs.These results are puzzling to me.Could you explain it?

Thank you.

0 sigong over 1 year ago in reply to sigong

Prodigy 250 points

Here is the script analysis result:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

-----------------------
SoC ID Header Info:
-----------------------
NumBlocks : [2]
-----------------------
SoC ID Public ROM Info:
-----------------------
SubBlockId :
SubBlockSize :
DeviceName : am64x
DeviceType : HSFS
DMSC ROM Version : [0, 2, 0, 0]
R5 ROM Version : [0, 2, 0, 0]
-----------------------
SoC ID Secure ROM Info:
-----------------------
Sec SubBlockId : 2
Sec SubBlockSize : 166
Sec Prime : 0
Sec Key Revision : 0
Sec Key Count : 0
Sec TI MPK Hash :

....

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

sigong said:
Additionally,I also tried a python script 'uart_boot_socid.py' to check the chip type.It shows the AM2432 in use belong to hsfs.These results are puzzling to me.Could you explain it?

If the device is indeed HSFS then the `sbl_dfu_uniflash.release.tiimage` won't even boot and so the flashing will not be successful at all.

Can you follow the below thread that suggets booting SBL NULL over UART

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1329012/am6442-sbl-is-blocked-in-an-loop-of-bootloader_socwaitforfwboot

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

When I used the 'sbl_null.release.tiimage' file via TeraTerm 3 times,the window cannot display info about frequency.

So,I tried the 'sbl_null.release.hs_fs.tiimage' later and the result show as below:

However,the same stuck phenomenon appeared again when I resumed the program and the chip is in OSPI mode.

Note:this time I tried the projet 'sbl_null_am243x-lp_r5fss0-0_nortos_ti-arm-clang'.

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

Can you please flash the exact same image to OSPI as well that is successfully booted in UART via Teraterm? More specifically, take the `sbl_null.release.hs_fs.tiimage` image and confirm it boots successfully in UART via Teraterm. Then, take the same image, flash it and boot the board in OSPI bootmode.

Does it still stuck get?

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

I have followed these steps and the process shows as below:

Firstly,I transfered the `sbl_null.release.hs_fs.tiimage` to the AM2432 chip in UART MODE via TeraTerm.

Here is the result:

If the board is still powered on,I found it impossible to use 'uart_uniflash.py' script.So I made it repower on.

Secondly,I used the 'uart_uniflash.py' script to flash 'sbl_uart_uniflash.Release.hs_fs.tiimage' and 'sbl_null.release.hs_fs.tiimage'.But it failed at the time of flashing 'sbl_null.release.hs_fs.tiimage'.

Here is the record:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Microsoft Windows [版本 10.0.19042.928]
(c) Microsoft Corporation。保留所有权利。

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>python uart_uniflash.py -p COM40 --cfg=sbl_prebuilt/am243x-lp/default_sbl_null_hsfs.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...
Found flash writer ... sending sbl_prebuilt/am243x-lp/sbl_uart_uniflash.Release.hs_fs.tiimage
Sent flashwriter sbl_prebuilt/am243x-lp/sbl_uart_uniflash.Release.hs_fs.tiimage of size 296821 bytes in 29.36s.

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage --operation=flash --flash-offset=0x0
Sending sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage: 0%| | 0/260636 [00:00<?, ?bytes/s]send error: error_count reached 10, aborting.
Sending sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage: 0%| | 2/260636 [11:00<47783:58:42, 660.01s/bytes]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

At this time,keep it powered on ,I can use the project 'sbl_uart_uniflash_am243x-lp_r5fss0-0_nortos_ti-arm-clang' by clicking the 'load symbols... ' button and find that the program can excute through 'Drivers_open();'.

What puzzled me is why the 'sbl_null.release.hs_fs.tiimage' cannot be flashed successfully via py script?

Thank you.

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

sigong said:
At this time,keep it powered on ,I can use the project 'sbl_uart_uniflash_am243x-lp_r5fss0-0_nortos_ti-arm-clang' by clicking the 'load symbols... ' button and find that the program can excute through 'Drivers_open();'.

This makes sense. Probably you don't have the `sbl_uart_uniflash` setup correctly for your custom board. I would like to know what changes you have made in `sbl_uart_uniflash` for your custom board.

Also, please share your `sbl_uart_uniflash` syscfg file.

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

This is the current 'main' function and no more changes:

uint32_t usercnt0=0;
int main(void)
{
int32_t status = SystemP_SUCCESS;
uint32_t done = 0U;
uint32_t fileSize;
Bootloader_UniflashConfig uniflashConfig;
Bootloader_UniflashResponseHeader respHeader;


usercnt0 = 1;
loop_forever();
Bootloader_socWaitForFWBoot();

Bootloader_socOpenFirewalls();


Bootloader_socNotifyFirewallOpen();


System_init();

usercnt0 = 2;
loop_forever();
Drivers_open();


usercnt0 = 3;
loop_forever();
status = Board_driversOpen();

usercnt0 = 4;
loop_forever();
DebugP_assert(status == SystemP_SUCCESS);


usercnt0 = 5;
loop_forever();
while(!done)
{
/* Xmodem Receive */
status = Bootloader_xmodemReceive(CONFIG_UART0, gUniflashFileBuf, BOOTLOADER_UNIFLASH_MAX_FILE_SIZE, &fileSize);

/*
* The `fileSize` wouldn't be the actual filesize, but (actual filesize + size of the header + padding bytes) added by xmodem.
* This adds ~1KB. We can't know exactly how many bytes will be padded without checking the file header. But doing that
* will unnecessary complicate the logic, so since the overhead is as small as ~1KB we could check for file size exceed
* by checking * this `fileSize` returned by xmodem as well.
*/

if(fileSize >= BOOTLOADER_UNIFLASH_MAX_FILE_SIZE)
{
/* Possible overflow, send error to host side */
status = SystemP_FAILURE;

respHeader.magicNumber = BOOTLOADER_UNIFLASH_RESP_HEADER_MAGIC_NUMBER;
respHeader.statusCode = BOOTLOADER_UNIFLASH_STATUSCODE_FLASH_ERROR;

Bootloader_xmodemTransmit(CONFIG_UART0, (uint8_t *)&respHeader, sizeof(Bootloader_UniflashResponseHeader));
}

if(status == SystemP_SUCCESS)
{
uniflashConfig.flashIndex = CONFIG_FLASH0;
uniflashConfig.buf = gUniflashFileBuf;
uniflashConfig.bufSize = 0; /* Actual fileSize will be parsed from the header */
uniflashConfig.verifyBuf = gUniflashVerifyBuf;
uniflashConfig.verifyBufSize = BOOTLOADER_UNIFLASH_VERIFY_BUF_MAX_SIZE;

/* Process the flash commands and return a response */
Bootloader_uniflashProcessFlashCommands(&uniflashConfig, &respHeader);

status = Bootloader_xmodemTransmit(CONFIG_UART0, (uint8_t *)&respHeader, sizeof(Bootloader_UniflashResponseHeader));
}
}

Drivers_close();
System_deinit();

return 0;
}

7206.example.zip

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

I see the DDR and eMMC is not enabled in the Sysconfig. While the eMMC is correctly disabled in case your custom board doesn't have eMMC, the DDR should be enabled as it is used by the `sbl_uart_uniflash`.

Also, I see no changes in the flash configurations for your custom flash part. You will need to modify these before proceeding with flashing.

You can refer to the following guides

AM243x MCU+ SDK: Adding Support For a Custom Flash Device (ti.com)

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

Maybe I didn't understand the idea.

I reconfigured the sysconfig like this two way ,meanwhile I replaced the 'sbl_uart_uniflash.Release.hs_fs.tiimage',but they all failed.

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Microsoft Windows [版本 10.0.19042.928]
(c) Microsoft Corporation。保留所有权利。

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>python uart_uniflash.py -p COM40 --cfg=sbl_prebuilt/am243x-lp/default_sbl_null_hsfs.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage --operation=flash --flash-offset=0x0
Sending sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage: 0%| | 0/260636 [00:00<?, ?bytes/s]send error: error_count reached 10, aborting.
Sending sbl_prebuilt/am243x-lp/sbl_null.release.hs_fs.tiimage: 0%| | 2/260636 [11:00<47784:32:49, 660.02s/bytes]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

You can ignore the DDR for now. You first need to modify the flash configurations to make the flash driver compatible with your flash part.

sigong said:
At this time,keep it powered on ,I can use the project 'sbl_uart_uniflash_am243x-lp_r5fss0-0_nortos_ti-arm-clang' by clicking the 'load symbols... '

When you load the symbols did you check where it was failing.

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

OK.I got the idea.Thank you.

0 sigong over 1 year ago in reply to sigong

Prodigy 250 points

Hi Prashant,

I have modified the flash configurations and the cmd window shows as below:

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Microsoft Windows [版本 10.0.19042.928]
(c) Microsoft Corporation。保留所有权利。

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>python uart_uniflash.py -p COM40 --cfg=sbl_prebuilt/am243x-lp/default_sbl_ospi.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 4 command(s) !!!

Executing command 1 of 4 ...
Found flash writer ... sending sbl_prebuilt/am243x-lp/sbl_uart_uniflash.Release.hs_fs.tiimage
Sent flashwriter sbl_prebuilt/am243x-lp/sbl_uart_uniflash.Release.hs_fs.tiimage of size 307461 bytes in 29.07s.

Executing command 2 of 4 ...
Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_ospi.Release.hs_fs.tiimage --operation=flash --flash-offset=0x0
Sent sbl_prebuilt/am243x-lp/sbl_ospi.Release.hs_fs.tiimage of size 301781 bytes in 28.45s.
[STATUS] SUCCESS !!!

Executing command 3 of 4 ...
Command arguments : --file=helloworld/hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x80000
Sent helloworld/hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs of size 40207 bytes in 6.64s.
[STATUS] SUCCESS !!!

Executing command 4 of 4 ...
Command arguments : --file=helloworld/hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage_xip --operation=flash-xip
Sent helloworld/hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage_xip of size 52 bytes in 3.08s.
[STATUS] SUCCESS !!!

All commands from config file are executed !!!

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

However,when I made the board repowered on in ospi boot mode with keeping the uart terminal open,the terminal window showed these info:

DMSC Firmware Version 8.6.4--v08.06.04 (Chill Capybar
DMSC Firmware revision 0x8
DMSC ABI revision 3.1

Some tests have failed!!

So,what reason may cause this?

Thank you.

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

sigong said:
So,what reason may cause this?

I am suspecting authentication failure here. Can you please check the "Disable Auth for Application Image" option in SBL_OSPI sysconfig file and see if this boots the application?

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

The operation works that checking the 'Disable Auth for Application Image' option in SBL_OSPI sysconfig file.

And the uart terminal outputs as below：

DMSC Firmware Version 8.6.4--v08.06.04 (Chill Capybar
DMSC Firmware revision 0x8
DMSC ABI revision 3.1

[BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH
[BOOTLOADER_PROFILE] Boot Media Clock : 10.000 MHz
[BOOTLOADER_PROFILE] Boot Image Size : 37 KB
[BOOTLOADER_PROFILE] Cores present    :
r5f0-0
[BOOTLOADER PROFILE] SYSFW init                       :      12004us
[BOOTLOADER PROFILE] System_init                      :        266us
[BOOTLOADER PROFILE] Drivers_open                     :        272us
[BOOTLOADER PROFILE] Board_driversOpen                :        204us
[BOOTLOADER PROFILE] Sciclient Get Version            :      10016us
[BOOTLOADER PROFILE] CPU load                         :     416851us
[BOOTLOADER_PROFILE] SBL Total Time Taken             :     439615us

Image loading done, switching to application ...
Hello World!
Hello World!!!!

However，it seems that some info about the cpu frequency doesn't appear.

By the way,I tried the 'sbl_null.Release.hs_fs.tiimage' image via uart_uniflash.py before.

The cmd window showd as below:

///////////////////////////////////////////////////////////////////////////////////

Microsoft Windows [版本 10.0.19042.928]
(c) Microsoft Corporation。保留所有权利。

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>python uart_uniflash.py -p COM40 --cfg=sbl_prebuilt/am243x-lp/default_sbl_null_hsfs.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_null.Release.hs_fs.tiimage --operation=flash --flash-offset=0x0
Sent sbl_prebuilt/am243x-lp/sbl_null.Release.hs_fs.tiimage of size 260604 bytes in 24.82s.
[STATUS] SUCCESS !!!

All commands from config file are executed !!!

C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot>

///////////////////////////////////////////////////////////////////////////////////

The cpu frequency info also did not appear in terminal when I repowered it in ospi mode.This time I checked the 'Disable Auth for Application Image' option in SBL_NULL sysconfig file.

What may cause this?

Thank you .

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

sigong said:
However，it seems that some info about the cpu frequency doesn't appear.

The SBL OSPI doesn't print any cpu frequency so those logs are expected. It seems SBL OSPI is working.

sigong said:
The cpu frequency info also did not appear in terminal when I repowered it in ospi mode.This time I checked the 'Disable Auth for Application Image' option in SBL_NULL sysconfig file.

Are there no logs when SBL NULL is booted from OSPI?

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

The problem seems related with the spi driver mode.

I reconfigure the mode as 1s-1s-4s,and currently the terminal can output logs including info abou cpu frequency using SBL_NULL in OSPI BOOT MODE.

Here it is:
Starting NULL Bootloader ...

DMSC Firmware Version 8.6.4--v08.06.04 (Chill Capybar
DMSC Firmware revision 0x8
DMSC ABI revision 3.1

INFO: Bootloader_runCpu:155: CPU r5f1-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU m4f0-0 is initialized to 400000000 Hz !!!
INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_runSelfCpu:217: All done, reseting self ...

before this,I just configured the mode as 1s-1s-1s .

Thank you for you help!!

But what makes me confused is why the spi mode influences the SBL_NULL.Because according to the info in cmd window,it displayed that all the images are executed and verified successfully.

0 Prashant Shivhare over 1 year ago in reply to sigong

TI__Guru 69741 points

Hi Sigong,

sigong said:
Because according to the info in cmd window,it displayed that all the images are executed and verified successfully.

SBL NULL doesn't actually boot any images. The sole purpose of SBL NULL is to initialize all the cores so that we can use CCS to connect to the cores. So, you do not even need to enable OSPI module in Sysconfig of SBL NULL.

Please let me know if you have any other queries related to this thread.

Apart from this, can you please share what flash part you are using and what flash configurations worked for you?

Regards,

Prashant

0 sigong over 1 year ago in reply to Prashant Shivhare

Prodigy 250 points

Hi Prashant,

No more questions now.

The flash is W25Q32.Here is the sysconfig file in use. Maybe there's another mismatch that hasn't been found. If you find,please notify me.Thank you.

1715.example.zip

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2432: stuck in Sciclient_waitForBootNotification