After I wrote some lines of text to a .txt file,
I got an error on the MTTTY serial monitor which read:
Trap occured
Vector=Acess Error FMT =03 SR =2018 FS =0C
Faulted PC=02028074
D0:FFFFFFFF 00000053 00000000 000000D4 000000D5 000000D6 00000073
A0:00000010 00000011 00000010 20002194 02038BBB 200027A4 20001CCC
Waiting 2sec to start 'A' to abort
Is the NB trying to write to a bad memory sector?
MOD5234 writing to file Trap occured ??
Re: MOD5234 writing to file Trap occured ??
I don't think the NB is trying to write to a bad sector, the code you wrote is. Memory errors like this can be things like stack overflow, bad pointers, etc. I would back up a step and reexamine what the last thing was you added.
-
thomastaranowski
- Posts: 82
- Joined: Sun May 11, 2008 2:17 pm
- Location: Los Angeles, CA
- Contact:
Re: MOD5234 writing to file Trap occured ??
To effective diagnose this, you need to find out what code is at: 02028074.
Use the objdump command to do something like this
objdump -S -g -C -l your-APP.s19
Then, examine the output at/around the PC address. I would give more explicit instructions, but I'm not no my netburner rig right now.
Alternatively, you can use the winaddr2line netburner tool to find out what function that address is in. This is oftentimes all that's needed.
Use the objdump command to do something like this
objdump -S -g -C -l your-APP.s19
Then, examine the output at/around the PC address. I would give more explicit instructions, but I'm not no my netburner rig right now.
Alternatively, you can use the winaddr2line netburner tool to find out what function that address is in. This is oftentimes all that's needed.