dml attempts a Raven

[dml]

This was the output from flashing the full TOS ROM to the SMD ROM board:

Code: Select all

> i
[$00bf:$233a] SST : SST39LF/VF802C  
> e
Erase...Done
> p
Erasing flash...
Receive file at $00000000

Done. 894976 bytes written

One difference in behaviour I noticed while flashing the larger image - the green blinking LED paused for a second or two after the first 1/4 or 1/3 of the transfer, then resumed blinking until it completed. It seems as if the USB link is running behind the programmer? How can I verify this is the case? Wrong number of bytes transferred?

...anyway the bytes written matches the byte size of the image on disk. maybe its ok? o_O

[agranlund]

the green blinking LED paused for a second or two after the first 1/4 or 1/3 of the transfer, then resumed blinking until it completed.

...anyway the bytes written matches the byte size of the image on disk. maybe its ok? o_O

Yep that is normal behaviour.
The led pause would be during a large-ish section of unused space, just filled with FF, which it will receive but doesn't actually need to program so the led will not blink at that point.
It made sense in my head to blink on programming but now that you mention it I think it would make more sense if it blinks on chunks received instead.

[agranlund]

Is there a good way to verify the contents of the whole ROM?

Nope, there are no seatbelts here :)

(verify after write would be a useful feature though)

[dml]

Ok thanks for keeping me grounded :)

Going to call it good enough for now. Will update the two small ATFs with the latest.... then turn my attention to the ATF1508 and everything new that comes along with that...

[dml]

...have started looking at what is involved with programming Nessi. This is exacty where I will normally end up in a rabbithole with the wrong software version, wrong connectors, doing something in the wrong order or other missing assumed knowledge of some kind. But I'll see what I can figure out!

I have ATMISP downloaded somewhere. I should even try installing it next.

[dml]

Off to a fantastic start already!

yay.png

The worst part is, it did ask if I wanted the drivers installed during the ATMISP install - to which I agreed.

Doubly bad that I already had FTDI drivers installed for something else... which now might not be working too.

[exxos]

Off to a fantastic start already!

Thats about the kinda luck I have with all software :lol: :roll: , which is why I try and avoid all software, especially new software :lol:

[dml]

Thats about the kinda luck I have with all software :lol: :roll: , which is why I try and avoid all software, especially new software :lol:

^^^ this, yes

[dml]

Ok managed to get past the driver hurdle and ATMISP agreed to load this time.

The programmer board is plugged into USB and with the app loaded, the onboard LED changed from dead to pale sickly green colour. Looks promising.

[dml]

Have played a bit with ATMISP now and think I follow what's going on with the device chain etc. (probably)

However I'm assuming the board will need external power during programming - and I haven't tried powering the Raven at all. So some cursory power-up testing should probably happen first.

I don't *think* the CPU needs to be present during programming. If I'm wrong about that, please let me know o_O