Well, you can examine the running live ROM code in hubRAM after boot, via Taqoz/Monitor/whatever, but I don't think there is a way to re-extract from the ROM itself. I think it vanishes after the initial COGINIT. One special case for Cog0 only.
I will check those differences in the files to see what's happened but I checked the listing against the actual ROM contents since the ROM is copied to $FC000 and TAQOZ ROM doesn't touch this area (or $7C000) so that it is still intact.
I'll post my list version(s) when I get home tonight.
IIRC there were some last minute changes and a rush to get the code to OnSemi, so the three of us (Chip, Peter and I) had to combine our blocks together quickly.
There is no difference in Versions B & C.
Versions A to B had some minor tweeks by Chip, TAQOZ has some good extras added, and the SD boot code had a few tweeks to fix the DO release problem. The Monitor did not change, and it's position remained static in the ROM.
Yes, I would get Chip's and Ray's code and run them through with all my individual build files through an M4 preprocessor and then through Dave Hein's p2asm and loadp2 so I could get a proper listing to check the mapping etc. Then I would load it onto my CVA9 board that was plugged into another board with all the test stuff on it and with Flash and an SD socket then also verify the timings with a scope etc. I would then shoot the combined and processed files back to Chip and Ray to check.
Chip didn't have any SD on his board.
I have a feeling that the last version was an "i" but ended up labelled as "g" in the code.
Comments
Yes, but I think it is not in the zip files, lately. I will start adding it in again and I'll post it here, too, in about an hour.
I've been getting my versions mixed up but this one checks out.
Thanks Peter & Chip
Thanks, Peter.
I did give the link earlier - https://forums.parallax.com/discussion/comment/1521913/#Comment_1521913
Peter, thank you for all those files with listings and binaries. Evanh, the website (github) has some missing files (for v32i).
Main differences between those versions:
(Note: v33k has much less size (bytes) due to use of tabs instead of spaces but only 12 lines changed)
How can we dump the ROM? I am thinking three ways:
Well, you can examine the running live ROM code in hubRAM after boot, via Taqoz/Monitor/whatever, but I don't think there is a way to re-extract from the ROM itself. I think it vanishes after the initial COGINIT. One special case for Cog0 only.
The initial copy is placed in the last 16 KB of hubRAM ($fc000 .. $fffff) - https://forums.parallax.com/discussion/comment/1520358/#Comment_1520358
I will check those differences in the files to see what's happened but I checked the listing against the actual ROM contents since the ROM is copied to $FC000 and TAQOZ ROM doesn't touch this area (or $7C000) so that it is still intact.
I think that there should be no issue. I was comparing rev. A to rev. B. Reading the ROM is just some learning exercise.
I'll post my list version(s) when I get home tonight.
IIRC there were some last minute changes and a rush to get the code to OnSemi, so the three of us (Chip, Peter and I) had to combine our blocks together quickly.
There is no difference in Versions B & C.
Versions A to B had some minor tweeks by Chip, TAQOZ has some good extras added, and the SD boot code had a few tweeks to fix the DO release problem. The Monitor did not change, and it's position remained static in the ROM.
Yes, I would get Chip's and Ray's code and run them through with all my individual build files through an M4 preprocessor and then through Dave Hein's p2asm and loadp2 so I could get a proper listing to check the mapping etc. Then I would load it onto my CVA9 board that was plugged into another board with all the test stuff on it and with Flash and an SD socket then also verify the timings with a scope etc. I would then shoot the combined and processed files back to Chip and Ray to check.
Chip didn't have any SD on his board.
I have a feeling that the last version was an "i" but ended up labelled as "g" in the code.
Here's comments section, post-v32, from ROM_Booter_v33k.spin2
and the version string
These are what I believe was final code for P2 Rev2 known as v33j