updating my pistorm 1200 : not working anymore.

[demether]

Hi,



I recently tried to update my pistorm 1200, using this archive :



https://github.com/michalsc/Emu68/re...torm32lite.zip


I copied the files (except config.txt) to the pistorm SD card (using linux). I then reinstalled it and started the amiga...the screen displays the famous grey pistorm screen, the version in the corner is the new one, but...no disk activity. No boot. I destroyed my amiga




Any help will be appreciated.

edit : by the way, I'm running 3.2 os, 3.2 physical rom, and my system is installed on a internal compact flash.

[Nor Bert]

What do you get on the Amiga screen from the RGB port or composite video ?

[demether]

from the rgb port, I obtain a pink screen : no disk activity.

From the hdmi port, I've got the grey splash screen of the pistorm : and no disk activy either.

It seems that the pistorm start and don't find the physical rom and/or the compact flash harddrive where I have the system installed.

[alexh]

Go back to your backup uSD card?

Did you edit config.txt? If you didn't put a kickstart ROM "kick.rom" on the uSD card I *think* you need to comment out the following line by adding # e.g.

# initramfs kick.rom

Originally Posted by demether

by the way, I'm running 3.2 os, 3.2 physical rom, and my system is installed on a internal compact flash.

You do know that significantly hampers Emu68? Performance will be a fraction of normal Emu68 performance.

[Kin Hell]

Something not right there. You have 16 files dated 02/06/2024

I have 19 files dated 01/06/2024

& yes..... Why are you not using the MicroSD interface? - It's over 20X faster using branded media than CF on the the internal IDE.

You're missing the following files:

bcm2710-rpi-2-b.dtb - 31.4KB 01/06/2024
bcm2711-rpi-cm4-io.dtb - 37.5KB 01/06/2024
bcm2711-rpi-cm4s.dtb - 52KB 01/06/2024

[alexh]

He's got a lite and not a CM4

[Kin Hell]

I did see the file names alexh & did wonder. Thx for the pointer....

In all honesty, not knowing which files are which or what exactly does what & without knowledge of the rudimentary functionalilty of the individual files, it appeared the most logical thing to suggest when having seen similar instances myself.
For my own experience, it was my own stupidity for not using the 32lite version of EMU68 archive. FOL is testament to that goof up & I spect I'm not the only one to have done that.
RE the link the OP provided, it checks out okay & if he hasn't modded the CONFIG file, re-download the archive & extract to the media again. I'm using the same un-modded files on Caffeine OS that has had numerous patches applied without issue.

The CF install must be dog slow though. I'm getting around 24Mb/sec from branded media & seen as high as 28 when overclocked to 2.5Ghz.

Pls excuse any typos, it's early & I'm on my phone posting this & my back is broken some more.....

[demether]

thank you all for your help. I'm pretty sure the pistorm start, and does not "see" the rom, and maybe the cf hard drive. I'll try to copy the files again, but I don't think it will work.

I'm using a CF as hardrive simply because I had it before the pistorm. I'm a lame (as you see) in configurate things.

[alexh]

Originally Posted by demether

I'm sure the pistorm start, and does not "see" the rom

It won't "see" the ROM unless you comment out the line in config.txt.

Without a ROM it won't do anything.

I would really recommend that you take the time to follow the guide to setting up a new boot drive on the PiStorm uSD card. It unlocks the true power of PiStorm. You can still keep the CF card and it will appear as another drive and you can either keep it as is or copy things over to the uSD card.

[demether]

thank you,

the thing is that I didn't edit the config.txt file. It's the same I was using when it was working, so the problem is elsewhere.

Anyway, I will probably send the SD card to my local amiga store and let the professionals do their stuff. I will take advantage of the situation installing amiga OS on the SD card instead of the CF card.

[Mr-Z]

Originally Posted by alexh

It won't "see" the ROM unless you comment out the line in config.txt.

Without a ROM it won't do anything.
card.

Since he mentioned that RGB gives pink/red-ish color it must be a ROM issue indeed.

[wiz12]

Try the following:

Create a text file called "cmdline.txt" containing:

buptest=2048 bupiter=1

and place this file in the BOOT directory of your microSD card, when you next turn on the Amiga it will run automatically and you should see the Emu68 screen performing chipmem write tests. If there's any problems it should report them.

[demether]

Definitly. But I didn't edit the config file, wich is the original one (when it was working). So the problem came from another file from the archive.


wiz12 I'll try it.


edit : here's my config file. PS : I tried to comment the initramfs line, no diference.

# Sample config.txt file for booting Emu68 with Pistorm
kernel=Emu68-pistorm32lite
disable_splash=1
arm_64bit=1

# Limit total memory size to 2GB for now. Necessary for CM4/Pi4
total_mem=2048

# Default boot delay is one second. Uncomment this line if you want zero second delay
boot_delay=0

# This is important so that GPU firmware does not add its overlay icons on the screen
# If you also want to disable speed throttling in case of undervoltage, set this value to 2
avoid_warnings=1

# Enable the options below to increase speed of ARM cpu to 1.5GHz
# Keep in mind this may render your RasPi3 unstable and eventually void the warranty!
#force_turbo=1
#over_voltage=4
#arm_freq=1800
#core_freq=500
#sdram_freq=600

# Force HDMI signal even if nothing is connected
hdmi_force_hotplug=1

# Limit GPU memory a little, force 1080p video mode. Comment out the hdmi_mode line if your monitor
# does not like it. For list of all modes please refer to RasPi documentation
# https://www.raspberrypi.com/documentation/computers/config_txt.html#hdmi-mode
gpu_mem=32
hdmi_group=2
hdmi_mode=82

# Experimental 2560x1440 50Hz mode for RaspberryPi which you can give a try. If you do, 
# comment the hdmi_mode above
#hdmi_group=2
#hdmi_mode=87
#hdmi_cvt=2560 1440 50 3 0 0 1
#max_framebuffer_width=2560
#max_framebuffer_height=1440
#hdmi_pixel_freq_limit=400000000

# The ROM is selected through initramfs parameter. As a file name give the full name of your
# kickstart file which you have placed on the RasPi boot partition. If there is a FPGA firmware
# to load (PS32Lite) or to upgrade (all others), it must be gzip-compressed and passed **before**
# the ROM name, separated from the rom with a comma.
#initramfs firmware.bin.gz,kick.rom
initramfs kick.rom

[ShK]

Can the old Emu68 build be so old, that old config file is not fully compatible anymore with the latest build?

[alexh]

You left some of the old files on the SD card? I wouldn't "mix-n-match" if it was me.

Are you sure the old config file is compatible with the new Emu68? I would do a fresh install with only the files from the new Emu68 archive and then comment out the line I mentioned above from config.txt

[demether]

Here's the result of the cmdline.



edit : here's the config.txt from the 1.x version of pistormlite. I commented the initframs line, we'll see.

# Sample config.txt file for booting Emu68 with Pistorm
kernel=Emu68-pistorm32lite
disable_splash=1
arm_64bit=1

# Limit total memory size to 2GB for now. Necessary for CM4/Pi4
total_mem=2048

# Default boot delay is one second. Uncomment this line if you want zero second delay
boot_delay=0

# This is important so that GPU firmware does not add its overlay icons on the screen
# If you also want to disable speed throttling in case of undervoltage, set this value to 2
avoid_warnings=1

# Enable the options below to increase speed of ARM cpu to 1.5GHz
# Keep in mind this may render your RasPi3 unstable and eventually void the warranty!
#force_turbo=1
#over_voltage=4
#arm_freq=1800
#core_freq=500
#sdram_freq=600

# Force HDMI signal even if nothing is connected
hdmi_force_hotplug=1

# Limit GPU memory a little, force 1080p video mode. Comment out the hdmi_mode line if your monitor
# does not like it. For list of all modes please refer to RasPi documentation
# https://www.raspberrypi.com/documentation/computers/config_txt.html#hdmi-mode
gpu_mem=32
hdmi_group=2
hdmi_mode=82

# Experimental 2560x1440 50Hz mode for RaspberryPi which you can give a try. If you do, 
# comment the hdmi_mode above
#hdmi_group=2
#hdmi_mode=87
#hdmi_cvt=2560 1440 50 3 0 0 1
#max_framebuffer_width=2560
#max_framebuffer_height=1440
#hdmi_pixel_freq_limit=400000000

# The ROM is selected through initramfs parameter. As a file name give the full name of your
# kickstart file which you have placed on the RasPi boot partition. If there is a development version
# of FPGA firmware to load (PS32Lite) or to upgrade (all others, not yet implemented), it must be
# gzip-compressed and passed **before** the ROM name, separated from the rom with a comma.
# NOTE: The default firmware for PS32Lite is already embedded in Emu68!!! Above instruction is
# for test/development purposes **ONLY**
#initramfs firmware.bin.gz,kick.rom
#initramfs kick.rom

edit 2 : not working.

[Kin Hell]

I've had Buptest fails similar to that for the hardware not being correctly assembled. - I can't offer you support on that particular code though, sorry.
Make sure the Keyboard isn't shorting on the pins on the top of the PiStorm lite assembly.

See here for setting up your CF card.

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

There are other tutorials around the web too.

[demether]

tonight after work I'll try without commenting the initframs line. We'll see. But except that line, the files are all brand new from the latest archive.

And now you understand why I kept the old build so long on my amiga...I hate configuration and stuff like that, it's always a mess.

[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.

[demether]

Originally Posted by Kin Hell

I've had Buptest fails similar to that for the hardware not being correctly assembled. - I can't offer you support on that particular code though, sorry.
Make sure the Keyboard isn't shorting on the pins on the top of the PiStorm lite assembly.

See here for setting up your CF card.

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

There are other tutorials around the web too.

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.