I have downloaded the Profinet library from here and am following the PDF files/videos contained in the zip files. This seems to go well until chapter 6 PROFINET protocol validation using ICE tool. When I scan the network at step 2, no device is found.
It seems to me an earlier step, during building or flashing, went wrong, because I also don’t see any UART logging or other indication that the firmware boots. It is also not possible to attach the MCULink debugger.
I suspect there may be an issue with the Secure provisioning/MCUXpresso plugin tool versions and changes that were made to the generation of the bootable image. The PDF and video use the 2509 SDK release, and I assume SEC tool. I started with the latest SDK release (2603) although I have also tried to downgrade to 2509. Still the SEC tool post build step, triggered from the VSCode MCUXpresso plugin after cmake completes, seems to work differently now and creates ELF files in: projects\goal_pnio_rpc_lib\00_cc\vsc\nxp\mimxrt1180_evk_cm33_rtos\.secureprovisioning
I have tried to program the image from the guide projects\goal_pnio_rpc_lib\00_cc\vsc\nxp\mimxrt1180_evk_cm33_rtos\flexspi_nor_release\mimxrt1180_evk_cm33_rtos as well as the secure provisioning one, but the result seems the same.
If I download the Profinet Eval Binarires. When I flash those, I can find the Profinet device, change cyclic data In the ICE tool and see logging from the COM port of the MCULink, so I don’t think there’s anything wrong with the hardware. That image does not seem to be XIP however (when loaded in SEC tool), so it is hard to compare the differences after flashing.
Should this example still work with the 2603 SEC tool and SDK or do I need to downgrade my whole setup?
Is there something I could be doing wrong and if so, how can I test if earlier steps were successful ?
I have tried many things:
- Reading back the programmed flash looking for the FCB (It looks ok, but it's a needle in a haystack to me).
- Trying other demos (blinky works, multicore trigger as well, but the flashing workflow is different, using an additional image for the CM7 core)
- Adding extra logging, right after initializing the board (nothing shows up)
- Using nxpele to look for boot info and events (they seem volatile and require a restart to start the flash loader?).
I have also tried to build the Debug configuration of the example, to see if the firmware hangs instead of the secure boot, but that is not possible. The resulting text section is too big (about 320kB) to be placed in the reserved and remaining RAM, so the linker fails.
Thanks for anyone that can provide a hint. I am out of ideas.
The problem has been reproduced and our team is resolving it internally now. We will promptly update you once a solution is available.
Dear Maurits Fassaert,
I have reverted all the tool version back to 2509, and the Profinet device is now successfully detected：
You could check the mcuxpresso-tools.json file in the project to see the SDK version currently in use:
If you are using a self-compiled ELF file, it is expected that no UART log will be output after boot. You can verify the boot status by checking the ENET3 port and the Ethernet port on your PC. If the orange LED is blinking, it indicates the network is connected, which means the boot process has completed successfully.
Thanks!
That works for now, so I am no longer blocked.