On 2014-07-04 at 11:02:03, Jim Brain (brain@jbrain.com) wrote: [...] > Sadly, no change. > > But, instead of stopping there, I decided to diagnose my test harness a bit. > > And, I found that I had accidentally turned on JTAG on this AVR via the > fuse settings, and so the incorrect opcodes were being sent. Fixed, and... > > SUCCESS! YESSS!!! > A couple notes: [...] > Thanks to all for the ML code. I never would have figured that part out > (well, maybe I would have, but I would have probably quit out of > frustration before I did so) I think I know what you mean ;-) Exactly the reason why I pushed to gain more clear information before trying anything. Thank you Jim for stepping in and getting this eventually done. Excellent job!! Hopefully this will also help VICE people and we may see a _full_ 1520 emulation at some point with e.g. SVG output... > And ran the code 16 times to read out RAM/ROM. I got two different > reading for page 2 and 3, so I need to determine which bytes are > different and I can read them out by themselves, but it's 3AM here, and > I've worked on this all night, so maybe someone else can help... http://dl.dropboxusercontent.com/u/58002657/cbm/1520/page2_diffs.png http://dl.dropboxusercontent.com/u/58002657/cbm/1520/page3_diffs.png Now the obvious question if this is just an idiosyncrasy of the chip we deal with or is it some kind of unreliability of the method? Were all other readings fully consistent? Those pages are supposedly "Unassigned" so it shouldn't be much of a problem if it is just inner life of the chip bit We have to verify now the remaining parts. I'll make a binary of the ROM part in a moment and have a look at it. -- SD! Message was sent through the cbm-hackers mailing listReceived on 2014-07-04 11:00:02
Archive generated by hypermail 2.2.0.
