Page 2 of 2

Re: AmigaOS 3.2.3 + ehide.device 1.2

Posted: 07 Apr 2025 16:32
by masterofdisaster
What's your A1200 version? Also what RTC module?
Mines Rev 2B and the RTC is the basic one from AmigaKIT
Battery is good, it holds date and time just fine, not sure what the problem is then.

Re: AmigaOS 3.2.3 + ehide.device 1.2

Posted: 07 Apr 2025 16:38
by supaduper
Rev 1d4 and the RTC is also Amigakit but has a built in temp sensor,tried a standard RTC also from Amigakit and that is also ok

Re: AmigaOS 3.2.3 + ehide.device 1.2

Posted: 12 Apr 2025 12:40
by drwhy
Hi !

I have to report some kind of the same problems with TF1230 and TF1260 too !!

I am using:
AOS3.2.3 with ehide1.2 compiled with Capitoline (April 2025 v2.00)
TF1230 128MB: FW tf1230r1_2021_10_01_beta (by the way: is there a newer FW around ??)
TF1260 128MB: FW 68090
ReAmiga 1200 1.5

No TF1230 or TF160 connected:
AOS3.2.3 ROM is working like is should.
(BootLogo after about 1 minute when no disk is inserted)

TF1230:
When I use the TF1230 card and no CF-Card at the ehide.device, the A12K boots into AOS3.2.3 but ehide1.2.device will not be loaded.
(I am not seeing it in sys-info)
When I use the TF1230 with a 64GB CF-Card at the ehide, the A12K starts to boot for a few second, but the it stops working !
(no clicking floppy devices, no activity on the internal HDD, no Software Guru, only the Power-LED and the RED-Led on the CF-Card reader is lit !!!)

But now:
In case a TF1230 is connected, no infernal CF/HDD but a Bootable Floppy everything seems fine here:
(Booting from Floppy and BootLogo when no Floppy is inserted)
In case a TF1260 is connected, no infernal CF/HDD but a Bootable Floppy the Amiga won´t boot !!!
(only black screene minutes !!!)

otherwhise:
With the TF1260, a internal CF-connected, booting from it and a CF-card at the ehide.device everything seems to be fine !
Amiga Boots like is should and I can boot from Floppy.

... so am I doing something wrong here ?

... and, for me it doesn´t matter if a clock module is connected or not !

Re: AmigaOS 3.2.3 + ehide.device 1.2

Posted: 12 Apr 2025 13:08
by supaduper
No problems here with the new 3.2.3 rom with ehide running the TF1230 or the TF1260, I have tested both on my A1200, and yes that firmware on your TF1230 is older than the dinosaurs, I have put the latest firmware below, just make sure you flash the correct one for your xilinx chip, either 144 or the 288 one
tf1230r1_2024_06_17_alpha.zip

Re: AmigaOS 3.2.3 + ehide.device 1.2

Posted: 12 Apr 2025 13:43
by drwhy
... thank you for the FW

Re: AmigaOS 3.2.3 + ehide.device 1.2

Posted: 12 Jun 2026 00:48
by masterofdisaster
drwhy wrote: 12 Apr 2025 12:40 Hi !

I have to report some kind of the same problems with TF1230 and TF1260 too !!

I am using:
AOS3.2.3 with ehide1.2 compiled with Capitoline (April 2025 v2.00)
TF1230 128MB: FW tf1230r1_2021_10_01_beta (by the way: is there a newer FW around ??)
TF1260 128MB: FW 68090
ReAmiga 1200 1.5

No TF1230 or TF160 connected:
AOS3.2.3 ROM is working like is should.
(BootLogo after about 1 minute when no disk is inserted)

TF1230:
When I use the TF1230 card and no CF-Card at the ehide.device, the A12K boots into AOS3.2.3 but ehide1.2.device will not be loaded.
(I am not seeing it in sys-info)
When I use the TF1230 with a 64GB CF-Card at the ehide, the A12K starts to boot for a few second, but the it stops working !
(no clicking floppy devices, no activity on the internal HDD, no Software Guru, only the Power-LED and the RED-Led on the CF-Card reader is lit !!!)

But now:
In case a TF1230 is connected, no infernal CF/HDD but a Bootable Floppy everything seems fine here:
(Booting from Floppy and BootLogo when no Floppy is inserted)
In case a TF1260 is connected, no infernal CF/HDD but a Bootable Floppy the Amiga won´t boot !!!
(only black screene minutes !!!)

otherwhise:
With the TF1260, a internal CF-connected, booting from it and a CF-card at the ehide.device everything seems to be fine !
Amiga Boots like is should and I can boot from Floppy.

... so am I doing something wrong here ?

... and, for me it doesn´t matter if a clock module is connected or not !
If you are using an extended 3.2.3 rom then possibly you are having the same issue I stumbled upon when it comes to booting from TF1260.
Check my other topic regarding this:
viewtopic.php?t=8355