Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulator fails with 'trap_store_access_fault' with any test #74

Closed
ghost opened this issue Oct 19, 2016 · 5 comments
Closed

Simulator fails with 'trap_store_access_fault' with any test #74

ghost opened this issue Oct 19, 2016 · 5 comments

Comments

@ghost
Copy link

ghost commented Oct 19, 2016

Any test or benchmark fails at start with error trap_store_access_fault.
any-bit pk.
Why spike can deny storing io?
Latest pull at the time of issue (db6051f)

@evancox10
Copy link
Contributor

evancox10 commented Oct 21, 2017

This happens if you try to load the ELF file to somewhere other than RAM. elf loading goes through HTIF and writes to the sim's bus device. There must be a writable device at this location on the bus.

...At least that's the behavior a now, a year and a day after you posted this. I thought I'd post the explanation so other people could find the reason why this happens.

Make sure that the elf _entry symbol has a corresponding RAM in spike, and that it's big enough to hold the code and other data you're loading.

@ghost
Copy link
Author

ghost commented Oct 21, 2017

@evancox10 I still have this as my project, it's just conservated for now.
I'm sure I can use that info later, thank you

@IC-Dream
Copy link

@alexmechanic Have you solved this issue? if you did, could you please tell me how to do, since i also encounter this issue, Thanks a lot.

@ethanhz
Copy link

ethanhz commented Oct 22, 2018

If Spike does not find a device or MMU to which this address could correspond to, you will get this error.
Having said that, can you share what address you are trying to write to?
And if you have any additional devices attached in Spike?

@ghost
Copy link
Author

ghost commented Oct 23, 2018

Sorry, currently I left working with this project and cannot force this issue anymore.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants