- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
Hello TI
We changed defalut flash in lp-am243 board to a custom flash device(IS25LP128F), we changed syscfg of demo "mcu_plus_sdk_am243x_09_02_01_05\examples\drivers\boot\sbl_ospi" based on the flash SFDP printed out by OSPI FLASH Diagnostic demo.
This is all the change we made in syscfg.
And we also added "OSPI_enableDacMode(gFlashObject_IS25LP128F.ospiHandle)" after initialized ospi and flash.
But when we flashed this ospi_sbl and helloworld application binary to the target flash, we got the result as below.
DMSC Firmware Version 9.2.8--v09.02.08 (Kool Koala)
DMSC Firmware revision 0x9
DMSC ABI revision 3.1
Some tests have failed!!
We are sure that the helloworld application binary is correctly flashed as we read out each byte from the flash and verified each byte. Actually ospi sbl failed in function "Sciclient_procBootAuthAndStart ", it returned -1.
But before we changed the flash device, we did the same proceduces, and application runs correctly.
We need help for this issue, looking forward to your reply. Thanks.
We did three experiments.
1. turn phy-enable on, function Bootloader_socAuthImage returns -1
2. Call OSPI_disableDacMode before Bootloader_socAuthImage, Bootloader_socAuthImage returns -1.
3.Change 4s_4s_4s to 1s_1s_1s can't read flash data properly,ERROR: Flash_norOspiOpen:1317: Flash_norOspiOpen : PHY enabling failed!!!! Continuing without PHY...
ERROR: Board_flashOpen:183: FLASH open failed for instance 0 !!!!
ASSERT: 0.174283s: ... /main.c:main:136: status == SystemP_SUCCESS failed !!!!!
2. as you mentioned, "And we also added "OSPI_enableDacMode(gFlashObject_IS25LP128F.ospiHandle)" after initialized ospi and flash.". Please help clarify why you add this code by manual?
In Bootloader_findSeq function it is the flash data directly accessed by passing in the address of flashArgs->appImageOffset + SOC_getFlashDataBaseAddr(), while after we change the flash, this operation can only be done manually by calling OSPI_ enableDacMode(gFlashObject_IS25LP128F.ospiHandle), otherwise, data abort will occur.
3. as discussed, you replace " S25HL512TFAMHI010" with new device "IS25LP128F" on TI LP-AM243 EVM, then found this issue. Please help provide the spec.
5. as discussed, SBL set OSPI controller in DAC mode, then send an address which mapping to the image in flash, to DMSC for authentication. Could you please help do an experiment? add code to read whole image to local variable, then send to DMSC for authentication?
The authentication using this approach is passed
Dear all,
The waveform was grabbed after the Bootloader_socAuthImage function was called, and we compared the beginning of the waveform to the beginning of hello_world.appimage.hs_fs, and they are the same, but in the end Bootloader_socAuthImage returned -1.
Hello，
When enabling PHY mode, SystemP_FAILURE was returned on line 1315.
And SystemP_FAILURE status set in line 1842 in function OSPI_phyTuneDDR.
Is the PHY mode enabled related to Flash configuration? How can we properly enable PHY.
Dear Jinliang.
as found by Prashant, The reason of the failure is "Issue with Hash operation". This is possibly because of the PKTDMA read incompatibility with the custom OSPI flash in DAC mode.
then I found the replied as below.
may I ask your help to clarify the status? and also help make clear below items?
1. on which board? LP_AM243 or your board?
2. PHY enable or not?
3. DAC mode is enable or not?
thanks a lot!
yong
