New - Amiga Romulator for A500 - A600

[Ledfoot]

Originally Posted by mkstr

I forgot about halt triggering the menu, but the memtest did pass before that happened indicating that the SRAM is being programmed properly. It kind of looks like a timing issue with this particular machine (between the SRAM and the motherboard), but it seems to work in the vast majority of machines so I'm not sure what could be different here.

How does the diagrom image behave?

Mike

Seemed to work fine, although it does sometimes report RAM errors, but the RAM tests in AmigaTestKit always come back clean.

I just got my KS 1.3/3.1 switcher rom today. Popped it in, both 1.3 and 3.1 booted right up perfectly and ran just fine. It's gotta be something funky between the Romulator and the board, but if the board is working fine with physical chips, I have a hard time pointing to it being the culprit in the equation...

[RoC]

Like Honey Badger, I am also having issues in getting the A600 romulator working. The Amiga seems to switch-on but the screen is black. The OSSC links the video signal, so something is coming out of it

Both romulator leds are on. I followed the pictures for the orientation (the head towards the trapdooor) and plugged/unplugged a few times. Putting back the orginal 2.05 rom works just fine. The motherboard is without any other expansion, to facilitate the troubleshooting.

I tried to solder the cable both on pin 2 of R511D and pin 3 of Q511. The Q511 is returning a solid caps green on the keyboard, so I assume there is something wrong with that soldering point.
The R511D looks good on the ketboard (no Caps), however the miggy is responding to reset but no screen either.

Tried to format on Windows the 8gigs SD in FAT32, FAT16 on a 4 GB partition but no luck. I understand this should not be the issue, because it should say SD error if something would be wrong with the micro SD.

Beside checking the Romulator with Putty that I am going to do, could I test anything else?

In the worst-case scenario, shall the A600 version be re-utilised for the A500? (I know the form factor is different)

Like Honey Badger, the problem might well be my A600 rev 1.5. It looks good on ATK and never have had problems with that, however it is not recapped and you never know.

[Hercules]

If you ever sell this product through Amiga suppliers, then please do not use Amiga On The Lake (AOTL) for distribution (as with your replacement A1200 keyboards). AOTL's customer service, communication and waiting time were appaling.

[cdh]

The Romulator's STM32 loads ROM code in the SRAM part while holding the Amiga in reset. It's pretty important that the CPU is not on the bus at this point because the STM32 needs to drive the address and data lines on the bus to load code into the SRAM.

Definitely connecting the serial UART will give you a hint as to whether the STM32 CPU is running or not. You can also test access to the SRAM from the UART. As far as I know, there's no easy way to tell that the Romulator is connected to the Amiga bus, but you can at least tell that the SRAM is working and there are no address or data line shorted / floating pins.

If you suspect that the problem is the connection of the reset signal to the Romulator or that the Romulator is not properly driving reset, there might be a simple way to test this. What I've noticed is that even without the reset line connected, if do Ctrl-Amiga-Amiga several times in quick succession right at cold power-on, this will hold the CPU long enough that the Romulator has a chance to load the initial selection program. Then when your CPU begins executing, it will run that selection program. You might have to try this a few times.

[RoC]

Thanks cdh for the advise.

I will test them on the A600, especially the cold-reset trick.

I have an A500 rev 8, can I test it there (paying attention not to short) or the firmware are different?

[cdh]

I'm pretty sure that you can test it in your A500, though you might not have room to put the keyboard in place. I've got an A600 Romulator that I tested in my A2000. Just be aware that the A500/A2000 Romulator has exactly the opposite orientation of the A600 Romulator (the side which has the STM32 sticks out on the other end of the ROM socket). I had to stack a couple 40 pin sockets to raise the Romulator above a board capacitor in my case, but from photos I've seen of the A500 motherboard, it doesn't look like there's anything tall in that area. Just be sure you have pin 1 orientation correct.

[RoC]

The good news is that reset followed by (many) reset actually works. I can get the select screen.

The bad news is that is not lasting long nor it can boot the roms. From what you hinted, it might not hold the reset.

Tried also on a disassembled A500 (just to exclude cold soldering) and the result is the same.
It starts (can hear the Amiga tunes) but then it hangs.

Well looks like my romulator is somehow defective or I have two muggies with issues.

Have more miggies, so I will try on some other system, because sending it back to US is the last measure (if they would be willing to check it)

Thanks for your help

[Pbjr]

Hello, I am in need of some help with the A600 Romulator. I purchased it some time ago from AOTL and finally got around to install it. All I get is a black screen. I read prior posts to test the reset wire with old rom and by grounding. It does indeed reset. I connected to the romulator with serial and here is the output. The A600 is v1.5 if that means anything. Thank you.

946684800.000 boot.c(29): Bad magic number or info block version
946684800.000 main.c(556): Board:       romulator rev B
946684800.000 main.c(557): Version:     1.0-12-059f2bb2/a4236d9a
946684800.000 main.c(558): Built:       Aug  2 2019 09:34:08 by mike@mike-desktop
946684800.000 main.c(559): Debug level: 3
946684800.000 main.c(560): RAM size:    81920 bytes
946684800.000 main.c(561): CPU Vcc:     3300 mV
946684800.000 main.c(562): Core clock:  120000000 Hz (expected 120000000 Hz)
946684800.000 main.c(563): PCLK1:       30000000 Hz
946684800.000 main.c(564): PCLK2:       60000000 Hz
946684800.000 main.c(565): Flash WS:    3
946684800.000 main.c(566): Reset flags: 0E
946684800.000 main.c(567): Boot vers:   NO BOOTLOADER
946684800.000 main.c(568): Wakeup src:  0
946684800.000 mcu-common/chip/stm32f2xx/rtc.c(94): Wrong RTC oscillator selected - forcing initialisation
946684800.000 mcu-common/chip/stm32f2xx/rtc.c(106): Initialising RTC
946684800.000 mcu-common/chip/stm32f2xx/rtc.c(157): Enable WUT init...
CL1388534400.000 main.c(404): Powering up SD card
I> 1388534400.000 mcu-common/chip/stm32f2xx/sd.c(483): sd_open
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(666): sd_configure
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(682): SD clock requested 400000 Hz, got 400000 Hz
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(500): Response to SEND_IF_COND - card is SD v2.0
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(501): IF_COND = 0x000001AA
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(513): Response to APP_CMD - card is SD
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0x00FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(530): voltage range not valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(534): SEND_OP_COND retry
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0x00FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(530): voltage range not valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(534): SEND_OP_COND retry
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0x00FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(530): voltage range not valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(534): SEND_OP_COND retry
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0x00FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(530): voltage range not valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(534): SEND_OP_COND retry
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0x00FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(530): voltage range not valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(534): SEND_OP_COND retry
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0x00FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(530): voltage range not valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(534): SEND_OP_COND retry
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(518): OP_COND = 0xC0FF8000
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(520): voltage range is valid
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(523): Card is high capacity SD v2.0 SDHC
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(159): CSD: 400E0032 5B590000 EE7F7F80 0A404054
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(235): capacity 30528 MiB, r/w block size = 512 bytes
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(252): CID: 1B534D47 42315154 30216955 A7014930
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(275): SD mfg 1B app 0x534D product 'GB1QT' rev 30 sn 216955A7 mfg 09/2001
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(666): sd_configure
1388534400.000 mcu-common/chip/stm32f2xx/sd.c(682): SD clock requested 24000000 Hz, got 24000000 Hz
1388534400.000 main.c(190):                 kickstart205.rom        524288
1388534400.000 main.c(417): Card read OK
1388534400.000 main.c(366): Config open failed error 4

CLI> ls
                kickstart205.rom        524288
CLI> load kickstart205.rom
1388534461.000 main.c(253): Image is <= 512K
1388534461.000 main.c(271): Image is an Amiga ROM


 *** STOP ***

Unhandled exception (74) from THREAD mode
PROCESS stack at 0x200039B8

Fault description:
Instruction at 0x8011924 raised BUS FAULT
Imprecise data access violation (fault address may be inaccurate)

System state:

     r0 = 0x60021000       r1 = 0x20003C00
     r2 = 0x00000400       r3 = 0x60021002
     r4 = 0x9FFDF3FE       r5 = 0x0000022F
     r6 = 0x20000534       r7 = 0x00021000
     r8 = 0x00000000       r9 = 0x00000000
    r10 = 0xA5A5A5A5   fp/r11 = 0xA5A5A5A5
 ip/r12 = 0x00000000

     pc = 0x08011924       lr = 0x08012055
   xPSR = 0x21000200
          (- - C - - T ISR=0)

   HFSR = 0x40000000     AFSR = 0x00000000
   DFSR = 0x00000000     MMAR = 0xE000ED34
   CFSR = 0x00000400     BFAR = 0xE000ED38
                      BASEPRI = 0

[cdh]

The "load" command fault above appears to be caused by a bug in the Romulator's STM32 firmware. Maybe triggered by the SD card format. It doesn't appear to happen at powerup, however, when the Romulator loaded kickstart205.rom the first time. I recommend you try starting up with no microSD installed. You should at least see the blue Romulator screen. If not, either the Romulator is not making good contact with your motherboard socket or the Romulator is defective. If you do get the blue screen, try reformatting your microSD and/or try a different Kickstart ROM image.

[eristocratic]

Just thought I'd throw in my 2 cents on the black screens - I initially had a black screen with my A600 romulator which has a rev 1.5 A600 board, I solved it sort of randomly (sigh... don't ask) by installing a 40 pin socket, leaving, IIRC, pins 1 and 42 on the Romulator dangling in the air. I'd guess you could try stacking a 40 pin socket onto the 42 pin one to accomplish the same thing.

She's been solid since April, but of course, YMMV.

[Pbjr]

Thanks guys for the replies.

No menu without mem card inserted.

Is this okay?
946684800.000 main.c(567): Boot vers: NO BOOTLOADER

I’m also seeing errors when memtest.
Failed at 0x60000000
Failed at 0x60020288...

[Pbjr]

Originally Posted by eristocratic

Just thought I'd throw in my 2 cents on the black screens - I initially had a black screen with my A600 romulator which has a rev 1.5 A600 board, I solved it sort of randomly (sigh... don't ask) by installing a 40 pin socket, leaving, IIRC, pins 1 and 42 on the Romulator dangling in the air. I'd guess you could try stacking a 40 pin socket onto the 42 pin one to accomplish the same thing.

She's been solid since April, but of course, YMMV.

WINNER! Wow, that was it! I didn’t have a socket adapter so I bent out those pins and the blue screen appeared. Can I leave it like this or do I need the adapter?

[cdh]

This is useful information! Thank you eristocratic and Pbjr for following up that disconnecting pins 1 and 42 solved your problem. I think it's perfectly safe to leave these two pins dangling as you have them.

[RoC]

Good finding!

I will try that on my romulator, hoping this fixes the issue

[Pbjr]

Great, I’ll leave as is. Many thanks for your help. I was so convinced I had a bad unit and was concerned that it’s been so long that any warranty had probably passed.

[Sundance2022]

I don't see anything here about the possibility of a Romulator for the 1200 or 4000 so I guess there wasn't the interest in making it?

[braunaudio]

Is there any life in this for the 32bit machines (A1200, A3k, A4k)?

[droopy]

Originally Posted by DofD

Very nifty I must say!

It would have handy to have a diag rom image available when needed.

Oh, and yes to the 32 bit version for the 1200 and 3000!

And the A4000 ofcource...

[jaesonk]

Can romulator be used on a DraCo? I don't think there'd be much use for older ROMs but maybe newer ones like 3.2?

DraCo supposedly uses an Amiga 3000 ROM but there's only 1 chip, I thought Amiga 3000s had 2. Or is it using an A500/A2000 AmigaOS3 ROM?

Also, my DraCo has DraCo ROM1.3 and then it soft kicks 1.5. Is there a way to make a physical 1.5 ROM using a romulator or similar device, or does anyone burn these?

[Calab]

I recently picked up a ROMulator for my A500. It's a very tight fit in my A500. with the keyboard actually touching the components at the end of the board. I needed to add a couple layers of electrical tape insulates against short circuits. If I remember correctly, I have the V600 - which I will double check when I reinstall my TF536 this week.

I can boot up with Kickstart 1.3, 3.1, 3.X and the Diagnostic ROM. I'm hoping to add 3.2.1 to the list, once I purchase a copy.

Once I receive my TF536 back from Alen the fun begins, with setting up the hard drive to handle booting from multiple different kickstarts.

I did have a couple of questions regarding the ROMulator...

1. Are there firmware updates available? Are they easy to flash?

2. Can you specify a custom MOD file to play at the menu?

3. I noticed that sometimes that the system boots with a different KS than the one I selected... usually when I scroll through the menu and hit ENTER quickly. Is this a known issue?

Thanks again for a great piece of hardware!