Hi,
We have two devices (both using AM2432_ALX) with different flash, one is Winbond W25Q64JV (for goal) , and the other is S25HL512TDPNHI010 (for test).
Using UART bootloader Python script, download sbl_null.release.hs_fs.tiimage into flash S25HL512TDPNHI010.
RBL could successfully load SBL and SBL run well in the test device with flash S25HL512TDPNHI010 under OSPI boot.
Then we used memory browser to read flash data from 0x60000000 to 0x60080000, and save data into image.
Using this image file, burn its image into the goal device with flash W25Q64JV via an external burner. (The data burned into the device has been confirmed to be correct)
But RBL could not successfully load SBL and SBL not run in the goal device with flash W25Q64JV.
From the measured SPI waveform, RBL has been continuously querying the ID under 50MHz clock.
Therefore, we checked whether the problem is 50MHz clock.
Under UART boot, through XMODEM to transmit sbl_null.release.hs_fs.tiimage to the goal device with flash W25Q64JV.
Using ospi_flash_diag_am243x-lp, test whether the flash ID can be correctly read at 50MHz. (ospi_flash_diag_am243x-lp project is attached)
Unfortunately, the flash ID was read incorrectly. (returned manufacturer id = 0xF7, returned device id = 0xA00B)
The correct answer should be: manufacturer id = 0xEF, deivce id = 0x4017.
But if clock is modified to 25MHz, the flash ID was read correctly.
1. Is the above method feasible for burning the image into flash W25Q64JV?
2. What are the possible reasons that could cause RBL could not successfully load SBL and SBL not run?
3. Why would the flash ID be read incorrectly at 50MHz? (W25Q64JV)
BR,
Chaowen
ospi_flash_diag_am243x-lp_r5fss0-0_nortos_ti-arm-clang_W25Q64JV.rar
