Fixing my Milan 040 (or not) blog

[peters]

Fantastic, welcome to the club, a very exclusive club.

[exxos]

Nice!! Great work!

[exxos]

Fantastic, welcome to the club, a very exclusive club.

[exxos]

That screwdriver must have landed on the EEPROM in just the right way to reprogram it with the bootblock at the top and no OS!

Yep, and blown a big chip at the same time!


I guess screwdriver landed on the ISA card, blew the chip on the MB, then user tried to fix it by burning the flash wrong.

[peters]

Fantastic, welcome to the club, a very exclusive club.

[peters]

Mine is running boot block 1.04

[dml]

\o/ \o/ \o/

That screwdriver must have landed on the EEPROM in just the right way to reprogram it with the bootblock at the top and no OS!

I was thinking the same when I asked about the accidental mis-flash :p "that's one really advanced screwdriver! where can I get one?"

[alexh]

Nice to see it booting. I hope that you can restore full functionality.

If you had a spare 060 (and there is any support for 060 in the Milan ecosystem) then you could possibly use one of the Amiga 040->060 adapter by Mozart & Matze (a1k.org). These are practically passive adapters that translate from 3.3v to 5v

https://eab.abime.net/showthread.php?t=100942

[exxos]

Mine is running boot block 1.04

Where is that ? I have 1.02 and it doesn't boot with it.

EDIT:

nevermind, it listed as TEST so I never looked at it.

https://www.schwingen.org/files/milan/tos/

[SteveBagley]

I get a single beep but no boot up. So not sure whats going on there. Will go back to the previous flash and try again...

The change log for v1.01 lists:

V1.01 13.5.2002:
- support Milan V2.1 board: map new config registers, disable watchdog
and RS232/RS485 drivers during startup
- display board revision during startup

- new error beep codes:
1 short beep - normal startup
1 long, 1 short beep: no SIMM in slot 0
1 long, 2 short beeps: wrong type of SIMM in slot 0
1 long, 3 short beeps: bad (defective) SIMM in slot 0
1 long, 4 short beeps: bus error in bootblock during startup

So a single beep sounds positive. Looking at the source, the next thing the bootblock does is try and initialise the keyboard, which is on the SuperIO chip so I suspect it might be stuck waiting for that to respond (which is difficult if it is removed ).

Steve