updating my pistorm 1200 : not working anymore.

[Kin Hell]

Originally Posted by mja65

buptest errors means the PIstorm has some connection issue. Did you remove the pistorm when taking out the SD card? If so it's possible you haven't reseated it properly. Sometimes removing it a millimetre or so from the edge can help.

In terms of the config file, if you are specifying a file of kick.rom you need to have this file on the sd card and the name is case sensitive.

Originally Posted by demether

the pistorm card was perfectly working, and the rom chip and CF card too...until I tried to upgrade my setup. So no hardware problem here.

Maj has already confirmed a connection issue which I have already lamented about.

Do check & double check everything is as it should be, please!

Sometimes, just pulling it all apart & reassembling can resolve issues like this & all due to bad contact.

Also, there should be no need to edit any of the CONFIG or exec files from the Archive you download from GitHub. You only need the kickstart ROM on the root of the 32Bit partition where you copied EMU68 files to.

[demether]

I'll do tonight, but I didn't move or remove the pistorm, only removed (carefully) the sd card.

Concerning the rom, as I said I'm using a physical 3.2 rom, not a file.


thank you all for your help !

[Kin Hell]

Originally Posted by demether

I'll do tonight, but I didn't move or remove the pistorm, only removed (carefully) the sd card.

Concerning the rom, as I said I'm using a physical 3.2 rom, not a file.


thank you all for your help !

You're very welcome but missing the point....

EMU68 needs a ROM file present on the same FAT32 partition as it's own files or it will not work.

Workbench 3.2 ships with ROM files in the archive. Copy the ROM file to the root of the Fat32 partition & name it kick.rom

See the link I posted to Wiki earlier

https://wiki.amiga.org/index.php?title=Pistorm32-Lite

I'm off to work now & won't be home till late evening....

[Liqourice]

Originally Posted by demether

the pistorm card was perfectly working, and the rom chip and CF card too...until I tried to upgrade my setup. So no hardware problem here.

If there's one thing I've learned after 40+ years with computers, don't ever rule anything out until you've tested it.

I don't know how many times I've solved problems by simply reseating hardware. Accelerators for old CPU sockets are notorious in this regard, it takes so very little to cause a bad connection and just giving it a slight push back can make things work again.

Not saying that this is the issue, just saying don't be to quick to brush it off because you think you haven't touched it. Removing an SD card and putting it back can be enough to disturb the connection.

[ShK]

Cleaning motherboard's side edge connector plates with deoxidizer spray will not harm.

[demether]

Originally Posted by Kin Hell

You're very welcome but missing the point....

EMU68 needs a ROM file present on the same FAT32 partition as it's own files or it will not work.

Workbench 3.2 ships with ROM files in the archive. Copy the ROM file to the root of the Fat32 partition & name it kick.rom

See the link I posted to Wiki earlier

https://wiki.amiga.org/index.php?title=Pistorm32-Lite

I'm off to work now & won't be home till late evening....

thanks




One thing I don't understand, is that I do not have a kick.rom file in my sd card....I didn't erased the files before upgrading, just putting the new files instead. So I don't understand.



TOnight I' will also double check the connections of the hardware, but I really have been very carefully...




I really think that sending the sd card (and maybe the pistorm itself) to the amiga store i bought it will be easier but since he's on holidays, I have a couple of days to try to do it by myself.

[mja65]

Originally Posted by demether

thanks




One thing I don't understand, is that I do not have a kick.rom file in my sd card....I didn't erased the files before upgrading, just putting the new files instead. So I don't understand.



TOnight I' will also double check the connections of the hardware, but I really have been very carefully...




I really think that sending the sd card (and maybe the pistorm itself) to the amiga store i bought it will be easier but since he's on holidays, I have a couple of days to try to do it by myself.

You don't need a rom file - if it can't find the one specified in the config file or you have commented it out it will use the onboard one. I must have missed where you mentioned you were previously using the physical ROM. You don't really want to do this by choice as it is significantly slower but it will work.

Upgrading the EMU68 files in of itself can't explain the issues you are having. Based on the bup test error and that it was working before I'm still suspecting its the connection. It's possible it was marginal before and you removing the SD card moved the pistorm sufficiently to cause a problem.

[alexh]

Originally Posted by Kin Hell

EMU68 needs a ROM file present on the same FAT32 partition as it's own files or it will not work.

No it doesn't. If you leave the line out of the config.txt it will copy the Physical ROM to RAM when it boots. It obviously makes Power-on first boot longer, and you have to comment the appropriate line out of the default config.txt

Originally Posted by mja65

You don't really want to do this by choice as it is significantly slower but it will work.

Only during the boot time following a power-on. From then on it is in RAM and works as fast as including a file on the SD card.

[wiz12]

[QUOTE=demether;1696000]


This confirms you have a RAM communication error between the Amiga and PiStorm. Best way to solve this would be to clean the Amiga's edge connector with a pencil eraser and then IPA. Then reseat the PiStorm and retry Buptest, if it still fails you might have to leave the PiStorm out 1 or 2mm from the edge connector.

[Kin Hell]

Originally Posted by Kin Hell
EMU68 needs a ROM file present on the same FAT32 partition as it's own files or it will not work.

Originally Posted by alexh

No it doesn't. If you leave the line out of the config.txt it will copy the Physical ROM to RAM when it boots.

4) Open root of SD card copy across a valid kickstart file across (i.e. Kickstart 3.1) and rename it kick.rom.

From here:

https://wiki.amiga.org/index.php?title=Pistorm32-Lite

It's all I know and have seen so many just grey & dead screens and ALL for not having put a kickfile on the root for being a noob;

OMFG!!!

If I'd actually known putting # initramfs kick.rom would copy the physical ROM where needed,
I'd probably still have hair now & spent less on MicroSD cards for a bonus!

@ demether

Any luck fella?

[demether]

Here we go :

I tried to use the amiga without anything : no ide CF, no pistorm. Just the bare machine. when it launches nothing happen. THe green light is lighted, but no "clic" from the floppy drive, and nothing displayed (black screen).

So there is a rom problem apparently, am I right ?

[Kin Hell]

Originally Posted by demether

Here we go :

I tried to use the amiga without anything : no ide CF, no pistorm. Just the bare machine. when it launches nothing happen. THe green light is lighted, but no "clic" from the floppy drive, and nothing displayed (black screen).

So there is a rom problem apparently, am I right ?

Possibly....

When you power on, watch the Power LED brightness.....

Does it go from Dim to brighter or is it staying the same brightness after powering on?

Pressing or wiggling the roms in their respective sockets & then pressing firmly may help alleviate the pink Screen.
I've seen RED screens on my Rev 1.5 Re-Amiga before now but resetting gets rid of it. RED screens are usually ROM issues afaik.

[demether]

it stays bright. I tried to plug and unplug, nothing new happening. Would it be a solution to put a software rom instead of the physical one ?

[Kin Hell]

Originally Posted by demether

it stays bright. I tried to plug and unplug, nothing new happening. Would it be a solution to put a software rom instead of the physical one ?

I presume this is without the PiStorm assembly in the Amiga?
If so....

If it stays bright, you might not be seeing the subtle change from dim to "brighter". There are two stages for the LED brightness.... Dim for about 1 to 2 seconds when powering on & then you should see it get brighter once the basic system check routines are done. It might sit there for 30 seconds looking for a hard drive (certainly on 3.1 ROM) if there isn't a drive on the internal 44pin header & then you should get the ROM screen on RGB output.

Out of the door for work now. Good luck!

[demether]

I tried to remove the roms, cleaningf all the stuff with alcohol, firmly reinserting them, nothing new happened.

[Mr-Z]

Originally Posted by demether

it stays bright. I tried to plug and unplug, nothing new happening. Would it be a solution to put a software rom instead of the physical one ?

Using a software ROM won't hurt for testing purposes.
You don't have to remove the physical ROM's on the motherboard for this.

But does the Amiga go to the kickstart screen when the PiStorm is disconnected ?

And what revision A1200 do you have ?
On Discord there's somebody with A1200 1A revision that's having trouble with newer builds of Emu68.
Revision of number of your A1200 is printed on the motherboard near the edge connector.