• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Answers 3 answers
  • Subscribers 120 subscribers
  • Views 1871 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?

Import FPV model : Failed to read 4 bytes from address 0

bradn

I'm using ADS Version: 2024.b-1 and have a project where I can run and debug code using the ADS suppled Coretex-A720 FPV model.  I would like to run / debug the same code on a different FPV model not supplied under the ADS install.

I followed the instructions here to create a model connection

https://developer.arm.com/documentation/107644/0100/Using-Arm-Development-Studio-to-debug-Fast-Models-systems/Import-the-FVP-into-Arm-Development-Studio

The error I run into is in the Disassembly: window I see 

"EL1N:0x0000000000000000 : Failed to read 4 bytes from address EL1N:0x0000000000000000"

Any tips or advice would be much appreciated.  Thanks.

Parents
  • 0 Arm Employee Badge in reply to bradn

    Hi again Brad,

    Sorry your message got filtered by the moderation software, it can be very sensitive. Don't worry, no harm done.

    You can use <FVP> --list-params > params.txt to see all the available parameters, bp.secure.memory may be something slightly different on your FVP.

    Looking at the log, I see a lot of REQuests and RESponses, which are likely the debugger detecting the individual blocks inside the FVP.

    IrisGI:REQ:1600: rddi_debug -> component.project.cpu.cpu0 resource_read(instId:10 /*0xau*/, rscIds:[0x2a9])
IrisGI:RES:1600: rddi_debug <- result={data:[0x1]}

    It is worrying that there is no log after trying to perform the write... this says to me that the debugger never manages to pass that request to the model (this log is from the FVPs point of view).

    This may be a difficult one to solve in a public forum... you may need to raise an official (private) support case from the Support section below. You can reference this thread so that the team have some history.

Reply
  • 0 Arm Employee Badge in reply to bradn

    Hi again Brad,

    Sorry your message got filtered by the moderation software, it can be very sensitive. Don't worry, no harm done.

    You can use <FVP> --list-params > params.txt to see all the available parameters, bp.secure.memory may be something slightly different on your FVP.

    Looking at the log, I see a lot of REQuests and RESponses, which are likely the debugger detecting the individual blocks inside the FVP.

    IrisGI:REQ:1600: rddi_debug -> component.project.cpu.cpu0 resource_read(instId:10 /*0xau*/, rscIds:[0x2a9])
IrisGI:RES:1600: rddi_debug <- result={data:[0x1]}

    It is worrying that there is no log after trying to perform the write... this says to me that the debugger never manages to pass that request to the model (this log is from the FVPs point of view).

    This may be a difficult one to solve in a public forum... you may need to raise an official (private) support case from the Support section below. You can reference this thread so that the team have some history.

Children
  • 0 in reply to Ronan Synnott

    Thanks for looking. I opened a support request.

    Just in case this helps here or with the support ticket I found the following in the debugger error log

    !ENTRY com.arm.debugger.ux 4 0 2025-06-23 14:02:37.574
    !MESSAGE Unable to map memory space NON_SECURE
    !STACK 0
    com.arm.debug.interpreter.ds.DSException: Failed to load "my.axf"
    at com.arm.debug.interpreter.ds.commands.file.AbstractFileCommand.executeOrUnload(AbstractFileCommand.java:84)
    at com.arm.debug.interpreter.ds.commands.file.LoadCommand.execute(LoadCommand.java:48)
    at com.arm.debug.interpreter.ds.commands.file.LoadCommand.execute(LoadCommand.java:1)
    at com.arm.debug.interpreter.ds.DSInterpreter$3.run(DSInterpreter.java:369)
    at com.arm.debug.interpreter.ds.DSInterpreter$3.run(DSInterpreter.java:1)
    at com.arm.debug.core.engine.connection.ConnectionEventManager$QueuedTask.run(ConnectionEventManager.java:94)
    at com.arm.debug.core.engine.connection.ConnectionEventManager.processTask(ConnectionEventManager.java:305)
    at com.arm.debug.core.engine.connection.ConnectionEventManager.access$8(ConnectionEventManager.java:303)
    at com.arm.debug.core.engine.connection.ConnectionEventManager$2.run(ConnectionEventManager.java:208)
    at com.arm.debug.control.CommandTask.fillInStackTrace(CommandTask.java:78)
    at com.arm.debug.control.ConnectionController.execute(ConnectionController.java:1959)
    at com.arm.debug.api.AbstractCommands.execute(AbstractCommands.java:115)
    at com.arm.debug.api.Commands.consoleCommand(Commands.java:149)
    at com.arm.debug.views.debugConsole.DebugConsolePage.commandIssued(DebugConsolePage.java:779)
    at com.arm.debug.views.debugConsole.DebugCommandLine.notifyListeners(DebugCommandLine.java:160)
    at com.arm.debug.views.debugConsole.DebugCommandLine.keyTraversed(DebugCommandLine.java:246)

    .....