Hardware version: S32G274A EVB
Software BSP version: BSP33.0
Software firmware (use official image):
1. binaries_bsp33.0/s32g274ardb2/fsl-image-auto-s32g274ardb2.sdcard 2. binaries_bsp33.0/s32g274ardb2/fip.s32-sdcard
Debugger: Lauterbach
Startup method: SD card startup
Question: Start the A core from the SD card, stay in uboot, use Lauterbach to attach the A core, check the 0x34000000 memory, and display ????. Another phenomenon is that when using the command md.b 0x34000000 0x1000 under uboot, it will crash and then automatically reset.
Hi,
We understand that you are using an EVB platform but see that you are using an RDB2 image, can you confirm that the behavior remains the same by using the EVB related image?
Also, on regards of the "when using the command md.b 0x34000000 0x1000 under uboot, it will crash and then automatically reset." comment, this seems to be related to the memory not being initialized, we can run the command after writing to the related address:
As for the second behavior you are showing, we are unable to reproduce your outcome due to the lack of tools from our side. Still, we see the following from our side:
Don't know if this information helps.
Please, let us know.
mw.b mw.w mw.l cannot be cleared ???, mw.q and cp can be cleared
