EMU68 Compatibilty Amiga 1000 with Rejuvinator Expansion Board

[jurassiccamper]

Hi,

As you are probably aware the Amiga1000 shipped with a WCS Daughter Board (Write Control Store) to which the Kickstart got loaded into from floppydisk. 48 Pin DIP Agnus in Model A Revision can only address 512K. 256K on Motherboard and 256K Via the front Expansion Port.

With a Model A A1000 in this configuration its possible to use a PISTORM with EMU68 on either a Pi3A or Pi4B with no compatibility issues observed.
Fast Ram OK, RTG OK & Wifi OK etc. Initramfs using A500 kickstart 47.111 from AmigaOS 3.2.2 EMU68 1.0.4

There is a aftermarket Daughter board called the Rejuvinator which gives the Amiga 1000, 2MB Chip RAM via an 8375 Agnus.

see https://www.amigalove.com/viewtopic.php?f=6&t=591

Suffice to say with a stock MC68000 fitted and the rejuvinator installed the Amiga 1000 works OK with 2MB chip and 512K Slow RAM

Chip is located at 00000000 to 001fffff
slow is located at 00c00000 to 00c7ffff

Amiga 1000 passes all tests with Amiga Test Kit.

Now remove the real MC68000 and install the PIStorm with EMU68. The Amiga loads the kernel and i assume its loading the kickstart as defined in initramfs and the Amiga boot loops in a cycle. Load from the Micro SDCARD in Pi (See activity Light) Finishes Amiga Reboots, in a cycle.
Tried all the changes to cmdline and config I can think of such as zero fast ram. No initramfs using a physical rom chip on the Rejuvinator.

Is it possible to configure EMU68 to write a debug file to the fat partition on the microsd card ? for analysis.

Any help would be appreciated.

[jurassiccamper]

No Change with EMU68 1.0.6 default package and config.txt using V40.63 A500 Kickstart 3.1 ROM or V47.115 A500 Kickstart from AmigaOS 3.2.3. Reboot Loop on PI3a and Pi4b. EMU68 Logo does appear via HDMI.

[michalsc]

Hello, thanks for the information and subsequent update. Emu68 cannot write the log to the sd card because Emu68 does not have an access to it - the driver for sd is on the m68k side, only.

Instead, you can attach FT232H (H is important!) adapter to the PiStorm and monitor the log data from Emu68 using additional Windows or Linux based machine. Please let me know if you are interested in it - is this the case then I will write a tutorial how to do that and will make it available on https:://pistorm.github.io page

[jurassiccamper]

Hello. Absolutely interested in helping to debug this. Happy to buy a board. If you could create tutorial that would be appreciated. If soldering is required thats not a problem for me.

[jurassiccamper]

FT232H Boards has arrived, ready to assist in getting logs. I looked on the pistorm discord to see if there was setup instructions there.
board i got is attached.

[michalsc]

Sorry for delay on my side. I have started writing the manual regarding debugging:

https://pistorm.github.io/docs/debugging/

I will attempt to finish it today including software upload. BTW. Will you use Windows or Linux machine to receive debug data?

[jurassiccamper]

Sorry for delay on my side. I have started writing the manual regarding debugging:

https://pistorm.github.io/docs/debugging/

I will attempt to finish it today including software upload. BTW. Will you use Windows or Linux machine to receive debug data?

Windows 10 on the laptop i can use.

[michalsc]

I have updated the manual with the part describing the debug tool and description how to use it - please have a look

[jurassiccamper]

 Cable built. Cheers for the doc.

[jurassiccamper]

@michalsc

I have followed the debugging document right upto the installation of fastserial.exe step. Which I cannot get to run under either windows 10 or windows 11. (x64) With the two files in contained in the zip extracted to the same directory and executing fastserial.exe from administrator command line I get the following errors.

On closer inspection I see the vcruntime140.dll is misnamed and has the "d" missing off the end.
ucrtbased.dll is not in the zipfile.

Edit

So ucrtbase.dll is located in C:\windows\syswow64

However fastserial.exe is looking for ucrtbased.dll, note again the "d" on the end.
Copying the dll to the same directory as fastserial.exe and adding the d on the end resolves the missing file issue but
i still get the following error
The application was unable to start correctly (0xc000007b).

[jurassiccamper]

So I gave up trying to figure out the dll issue with fastserial.exe and just switched to good old reliable putty instead. 926000 8N1

Log below.

putty.log

[michalsc]

This is interesting - it seems that Emu68 reacts to asserted RESET signal quite early in the boot process. Could you please add to cmdline.txt the debug disassemble and paste the log?

[jurassiccamper]

cmdline.txt = debug disassemble
EMU68 1.06
initramfs V40.63 A500 ROM

debug-disassemble.txt