• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 1203 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?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Simulator: Mapping filesystem to not existent memory area

Martin Gerth

I would like to test file-system related functions using the simulator. The real hardware (AT91SAM7S) accesses an external SPI-Flash containing the file system. In the simulator, i wanted to MAP the filesystem image using the LOAD and MAP command to memory address 0x400000 (which does not exist on the real hardware). When I access this region during simulator runtime, i get the following error message:

Data Abort: ARM Instruction at 002014B4H, Memory Access at 00400000H

which is a trap of the arm core which would be correct on the real system, but which makes it impossible for me to simulate my file system.

Is there a way to disable the abort trap, or does anyone know another solution to simulate a file system?

Thanks!

Parents
  • 0 in reply to Eugen Mailaender

    Hi Eugen

    Thanks for your reply. Thats a good idea, but my filesystem is 4MB which doesnt fit in this area.

    Actually I found a workaround. I load the whole filesystem to address 0x400000 and instead of accessing this memory directly, I rewrote the memory access function of my filesystem to call a simulator function, which copies a memory block from the filesystem memory to a location in the ram. I can then access the data in the ram. Its a bit tricky but it works fine too.

    Martin

Reply
  • 0 in reply to Eugen Mailaender

    Hi Eugen

    Thanks for your reply. Thats a good idea, but my filesystem is 4MB which doesnt fit in this area.

    Actually I found a workaround. I load the whole filesystem to address 0x400000 and instead of accessing this memory directly, I rewrote the memory access function of my filesystem to call a simulator function, which copies a memory block from the filesystem memory to a location in the ram. I can then access the data in the ram. Its a bit tricky but it works fine too.

    Martin

Children
No data