TDA4VM: add the ability to write/erase OSPI Flash in SBL

Hi,

Is the intention to just erase the flash? Can you use UNIFLASH tool for that purpose? If yes, please follow the instructions at https://e2e.ti.com/support/processors-group/processors/f/processors-forum/943810/tda4vm-how-to-use-uniflash-easeing-emmc-flash/3514788#3514788. The steps mentioned in the e2e are for erasing eMMC, to erase OSPI just change the device ID (argument after -d) from 4 to 3.

-e argument specifies the size of region to be erased.

# This will send the flash programmer over UART and then send the sysfw
dslite.bat --mode processors -c COM7 -f C:\ti\uniflash_5.3.1\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0

# This will erase the OSPI, here size is in Bytes (in HEX)
dslite.bat --mode processors -c COM7 -d 3 -e 7c0000

Uniflash doc: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_03_00_07/exports/docs/pdk_jacinto_07_03_00_29/docs/userguide/jacinto/board/uniflash.html 

Regards,

Karan

It's not just about erase Flash,I want to write read some partition in Flash, erase that partition, and then write new data to that partition，and in that case, call Board_flashWrite, and then the program hangs there。Are we sure the Board_flashWrite function works in SBL？

Hi,

I see from the code snippet you attached, that you have made some changes on the SDK.

Can you provide me a patch of your changes on top of SDK7.2?

Regards,

Karan

Based on your hardware, add the Board_FlashWrite function to my picture above and test if it works properly.

thank you！

Hi,

Can you provide a patch of your changes which I can use to check this on the EVM?

Regards,

Karan

diff --git a/modules/pdk/pdk_jacinto_07_01_05_14/packages/ti/boot/sbl/src/ospi/sbl_ospi.c b/modules/pdk/pdk_jacinto_07_01_05_14/packages/ti/boot/sbl/src/ospi/sbl_ospi.c index b91f776..726fa12 100755 --- a/modules/pdk/pdk_jacinto_07_01_05_14/packages/ti/boot/sbl/src/ospi/sbl_ospi.c +++ b/modules/pdk/pdk_jacinto_07_01_05_14/packages/ti/boot/sbl/src/ospi/sbl_ospi.c @@ -231,6 +231,7 @@ int32_t SBL_ReadSysfwImage(void **pBuffer, uint32_t num_bytes) #if defined(SIM_BUILD) || defined(SOC_J7200) ospi_cfg.phyEnable = false; #endif + ospi_cfg.phyEnable = false; /* Set the default SPI init configurations */ OSPI_socSetInitCfg(BOARD_OSPI_NOR_INSTANCE, &ospi_cfg); @@ -242,10 +243,16 @@ int32_t SBL_ReadSysfwImage(void **pBuffer, uint32_t num_bytes) h = Board_flashOpen(BOARD_FLASH_ID_MT35XU256ABA1G12, BOARD_OSPI_NOR_INSTANCE, NULL); #endif + uint8_t buf[11]; + memset(buf, 0x00, sizeof(buf)); + int writemode = 0; if (h) { SBL_ADD_PROFILE_POINT; + SBL_log(SBL_LOG_ERR, "test\n"); + Board_flashWrite(h, 0x1380000, buf, sizeof(buf), (void *)&writemode); + SBL_log(SBL_LOG_ERR, "SBL\n"); #if defined(SIM_BUILD) || defined(SOC_J7200) /* Disable PHY pipeline mode */

Hi,

I'm sorry but I am not able to understand the diff from your response.

One thing that I see as an issue is that the writeMode you are using should be 1 not 0. See pdk*/packages/ti/drv/spi/test/ospi_flash/src/main_ospi_flash_test.c#757 and pdk*/packages/ti/board/src/flash/nor/nor.h#107

You can refer the OSPI Unit Test for the correct sequence. Source code at pdk*/packages/ti/drv/spi/test/ospi_flash/.

Regards,

Karan

i set writeMode value to 1, I test found that the Board FlashWrite did not return properly。I refer to the routine you said,Board_FlashWrite does not return properly。

Add the following code to line 249 of the sbl_ospi.c file and test it to see if it works.

Have you made any progress?

Hi,

We will try to reproduce this at our end tomorrow & get back to you on this.

In future for any pdk related diff sharing. Please do the following:

cd $PSDKRA_PATH/pdk_jacinto_07_03_00_29
git init
git add .

The above will create a pdk git repository.

After that you can jus give us the diff output easily:
git diff path_to_file > diff

And share it. This will make it very easy for us to apply the diff directly to test & reproduce.

Best Regards,
Keerthy

Have you made any progress?

Hi,

I will try this and have an update for you shortly.

Regards,

Karan

I am able to replicate the issue, I see the below logs from your test:

No prints after test.

Regards,

Karan

so how can we solve this problem?

is there any progress ？

Hi,

Apologies for delay, I will have an update for you by end of this week.

Regards,

Karan

Hi,

Can you take reference from the board_diag_ospi application? That has the sequence for writing, reading and erasing the flash. Run that from the SBL as an application and do not integrate the code in SBL as that will increase the size of the SBL. I tried that and it doesn't fit in the OCM RAM.

Use the default OSPI SBL and then flash the board_diag_ospi_mcu1_0_release.appimage at 0x100000.

Build the app using:

cd pdk/packages/ti/build/

make board_diag_ospi

Source code: pdk/packages/ti/board/diag/ospi/src/ospi_test.c

Regards,

Karan

• Verify that the board_diag_ospi application is working properly?

Verify that the board_diag_ospi application is working properly?