PN7462 Boot Error on check PH_FLASHBOOT_SUPPORTED_EEPROM_VERSION Issue

[won2rang]

Erase Flash was performed during Flash Write during PN7462 Evaluation.
After that, the booting process stops and does not proceed.
The stuck point is PH_USER_ASSERT(gpkphCfg_EE_Ctrl_VerInfo->major == PH_FLASHBOOT_SUPPORTED_EEPROM_VERISON_MAJOR); line 458 of phFlashBoot.c. It's a step.
It appears that the entire Flash was erased during Flash Write, but I cannot figure out how to write a new Flash.

[danielchen]

Hi @won2rang :

could you please let me know how to reproduce your issue on PN7462 EVK board?  thanks

Regards

Daniel

[won2rang]

Hi Daniel,

Thanks for your reply.
Debug operation was possible through the IDE (MCUXpress) for the first time, and we attempted to operate it as standalone through the Flash tool.
However, even when using the Flash tool, it did not boot as Standalone.
So, while testing repeatedly, after checking Enable Erase All Flash banks, an option in the Erase tab of the GUI Flash Tool for SEGGER J-Link probes Erase flash, the same phenomenon as in the previous post occurred.

[danielchen]

Hi 

PN7462AU flash memory can be updated either by using SWD interface and LPC-LINK 2 debug probe or from primary bootloader mode (USB MSD).

Via SWD interface, a correct flash driver needs to be specified.  

Please check UM10883 (section 8.9, 8.10) for more details.

I would suggest you Update flash and EEPROM via USB MSD interface, it is quite convenient. 

Regards

Daniel

Regards

Daniel

[won2rang]

Dear Daniel Chen,
Following your advice and the contents of the document, I changed the FW of LPC-Link2 from Segger J-Link to CMSIS-DAP and was able to check the status of the EEPROM by operating in USB MSD mode.
As expected, all EEPROMs were initialized to 0xFF.
Due to my lack of analysis, I wasn't able to create my own EEPROM, and I couldn't find the default EEPROM in the IDE and SDK.
Can you tell me a quick way to create an EEPROM?

thank you

Regards 

Kevin

[danielchen]

Hi @won2rang 

I would recommend you refer to UM10948: EEPROM Management of PN746x and PN736x.

UM10948 EEPROM Management of PN746X and PN736X (nxp.com)

section 2.4 Building a new EEPROM binary.

Regards

Daniel

[won2rang]

Hi Danielchen,
Thanks for the reply.
I will check the data you sent again.
Below are additional details.

1. PN7462 eeprom was secured through the Nxpnfcockpit program.
2. After executing the EEPROM Binary according to the procedure of UM10883, when LPC-Link2 is driven in JLink mode, Debug mode operates in MCUXpresso IDE.
(HW configuration: PNEV7462C + LPC-Link2)
2. "LinkServer GUI Flash programmer" like UM10883 does not run in my computer environment.
(If LPC-Link is updated with CMSIS through LPCScrypt_2.1.2_57, Debug does not work in the IDE.)
3. Even if you download the binary file to address 0x203000 using MCUXpresso IDE J-Link Programmer, it does not work properly.
4. Even if fW is updated in the same way as the PN7462's eeprom, it does not work properly.
0. Currently, the only normal operation is possible when LPC-Link2 is operated as Jlink and operated in Debug mode in MCUXpresso IDE.

Ask for advice.

Regards

[danielchen]

section 8.10 in UM10883 described how to update flash and EEPROM via USB MSD interface, does it work on your side?

[won2rang]

Cockpit's basic binary file is updated normally through the MSD interface.
However, the binary file of the SDK's example project does not work normally after updating through the MSD interface.
If possible, I have attached the project file, so please review it.

[danielchen]

Hi won2wang:

If you needs to run and debug the examples, you can use SWD interface, please refer to section 8.7 in UM10883 for more details.

I tried to update the application bin file to PN7462 through MSD,  the update process is completed without errors.    if it does not work in your side, do you have any log file?

[danielchen]

Hi

The default EEPROM.bin can be found in cockpit installation tool