Debug configuration in Arm Development Studio v2023.1

Hi Stephen,

I am able to connect to board now with on-chip ram as application entry point from BootRom(without Preloader).
But still boot from SD Card doesn't work for me.
I am planning to try some procedures suggested by people in Intel forum to fix that.

Another issue is that the peripheral registers are not accessible in "Registers" window but Core registers are.


Do you know which configuration to verify to make peripheral registers accessible in "Registers" window ?

Best Regards,
Naresh

Hi Stephen,

I am able to connect to board now with on-chip ram as application entry point from BootRom(without Preloader).
But still boot from SD Card doesn't work for me.
I am planning to try some procedures suggested by people in Intel forum to fix that.

Another issue is that the peripheral registers are not accessible in "Registers" window but Core registers are.


Do you know which configuration to verify to make peripheral registers accessible in "Registers" window ?

Best Regards,
Naresh

Hi Stephen,

I am able to connect to board now with on-chip ram as application entry point from BootRom(without Preloader).
But still boot from SD Card doesn't work for me.
I am planning to try some procedures suggested by people in Intel forum to fix that.

Another issue is that the peripheral registers are not accessible in "Registers" window but Core registers are.


Do you know which configuration to verify to make peripheral registers accessible in "Registers" window ?

Best Regards,
Naresh

Hi Stephen,

I have managed to set peripheral description file in debug configuration.

And I can access peripheral registers now

But I have no idea why GPIO registers are still Unavailable.


Best Regards,
Naresh

Hi again

Those peripheral registers are memory-mapped, so the debugger must read from their memory locations to obtain their contents.

"Unavailable" is shown in this case where the debugger tried to read memory from that address, but failed for some reason.

There may be several different reasons why the debugger was unable to read those addresses, for example:
the peripheral might be powered-down
the peripheral might need to be explicitly enabled before use
the peripheral might be disabled for the current processor mode or security state (e.g. some peripherals are only accessible in secure state)
the peripheral might require a certain access width, e.g. 8-, 16- or 32-bit access
the peripheral might not be at the address that the debugger thinks it is at

I guess, for example, that gpio0_gpio_swporta_dr resides at either 0xFFC02900 or 0xFF708000, but maybe it is somewhere else.

I suggest you check Intel's documentation to confirm its exact location and accessibility, then try in the Commands view commands like:

output /x *0xFFC02900 # read using default access width

output /x *(unsigned int *)0xFFC02900 # force a 32-bit read

output /x &gpio0_gpio_swporta_dr # prints the address that the debugger knows

output /x gpio0_gpio_swporta_dr # reads from that address

Hope this helps

Stephen