Another alternative is to use simpletransfer:

http://os4depot.net/share/network/server/misc/simpletransfer.lha

Supports OS 4, OS 3, Windows, and Android.

Cheers
Bill "tekmage" Borsari

For 2D our best benchmark is:
http://www.os4depot.net/share/utility/benchmark/gfxbench2d.lha

For 3D stuff I found starboxdemo:
http://www.os4depot.net/share/graphics/misc/starboxdemo.lha


I ran starbox on my X5000 with RX580:
StarBox Benchmark 1.0
Resolution: 1366 * 768
Windowed
FPS: 907.55

Cheers,
Bill

I took a look at the code on GitHub (https://github.com/keirf/greaseweazle/tree/master/). That code base is written in Python 3.8, so I can understand why they would not want to maintain a Python 2.5 target along with all the libraries our native OS4 Python does not support.

What I'm thinking now is that I'll stick an RPI in my case, have the PI talk to the Greaseweasle, and build a Hollywood GUI to send commands to the PI to work with the floppy. Should not be all that hard to create something that detects a floppy insert and automates the process to have that floppy popup on the workbench :)

Cheers,
Bill "tekmage" Borsari

Any update on this support? If any dev wants to commit to making it work, PM me and I'll buy you one.

Cheers,
Bill "tekmage" Borsari

@Gregor

My X5000/20 has had this problem over the years, and it just started getting worse and worse.

I have the MCU connected to serial so I can monitor the error and see the output. I used the 1 second output option and watched the vdd_3v3_xorro drop from 3.21 to 2.95 over the period of about 15 minutes.

Here is a measure meant about halfway through:
- vcc_cpld: 3.32
- vdd_3v3_xorro: 3.04
- vdd_1v0_idt: 1.00
- vdd_1v0_xorro: 1.00
- vdd_3v3: 3.32
- vdd_2v5: 2.46
- vdd_1v2_eth: 1.19
- vdd_pl: 1.03
- vdd_ca: 1.09
- vdd_cb: 1.09
- vdd_ddr3_io: 1.49
- vdd_xvdd_fl: 1.80



Here is the output when the problem happened:
- vcc_cpld: 3.32
- vdd_3v3_xorro: 2.98
- vdd_1v0_idt: 1.00
- vdd_1v0_xorro: 0.99
- vdd_3v3: 3.32
- vdd_2v5: 2.46
- vdd_1v2_eth: 1.19
- vdd_pl: 1.03
- vdd_ca: 1.09
- vdd_cb: 1.08
- vdd_ddr3_io: 1.49
- vdd_xvdd_fl: 1.80


- pcb_temp: 40 deg C
- cpu_temp: 56 deg C
- pex_temp: 66 deg C


- FAN RPM: 0

ERROR: vdd_3v3_xorro out of range. Expected 3.30, got 2.95
WARNING: Supplies Turned off. Shutting down.
ATX supply turned off.

My case differed from Sinans in that only one voltage line was impacted.

I would hook up the MCU to serial so you can get a better view of the issue. I use this part to access the MCU:
https://www.amazon.com/gp/product/B07R ... _asin_title?ie=UTF8&psc=1

The manual has the pins. Let me know if you need those as well.

Cheers,
Bill "tekmage" Borsari

@Gregor

My X5000/20 has had this problem over the years, and it just started getting worse and worse.

I have the MCU connected to serial so I can monitor the error and see the output. I used the 1 second output option and watched the vdd_3v3_xorro drop from 3.21 to 2.95 over the period of about 15 minutes.

Here is a measure meant about halfway through:
- vcc_cpld: 3.32
- vdd_3v3_xorro: 3.04
- vdd_1v0_idt: 1.00
- vdd_1v0_xorro: 1.00
- vdd_3v3: 3.32
- vdd_2v5: 2.46
- vdd_1v2_eth: 1.19
- vdd_pl: 1.03
- vdd_ca: 1.09
- vdd_cb: 1.09
- vdd_ddr3_io: 1.49
- vdd_xvdd_fl: 1.80



Here is the output when the problem happened:
- vcc_cpld: 3.32
- vdd_3v3_xorro: 2.98
- vdd_1v0_idt: 1.00
- vdd_1v0_xorro: 0.99
- vdd_3v3: 3.32
- vdd_2v5: 2.46
- vdd_1v2_eth: 1.19
- vdd_pl: 1.03
- vdd_ca: 1.09
- vdd_cb: 1.08
- vdd_ddr3_io: 1.49
- vdd_xvdd_fl: 1.80


- pcb_temp: 40 deg C
- cpu_temp: 56 deg C
- pex_temp: 66 deg C


- FAN RPM: 0

ERROR: vdd_3v3_xorro out of range. Expected 3.30, got 2.95
WARNING: Supplies Turned off. Shutting down.
ATX supply turned off.

My case differed from Sinans in that only one voltage line was impacted.

I would hook up the MCU to serial so you can get a better view of the issue. I use this part to access the MCU:
https://www.amazon.com/gp/product/B07R ... _asin_title?ie=UTF8&psc=1

The manual has the pins. Let me know if you need those as well.

Cheers,
Bill "tekmage" Borsari

@geennaam

It looks like this is the line you are thinking of on the X5000:

hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1;usb1:dr_mode=host,phy_type=utmi;usb2:dr_mode=host,phy_type=utmi

Here is the hwconfig on the A1222:

hwconfig=esdhc;audclk:12;usb1:dr_mode=host,phy_type=ulpi

@rjd324

I was having an issue with the machine randomly shutting down. The error message was coming out on the MCU:

>> ERROR: vdd_3v3_xorro out of range. Expected 3.30, got 2.96
WARNING: Supplies Turned off. Shutting down.
ATX supply turned off.

It looks like it was the PSU. I bought one of those excellent battery-powered air blowers and chased LOTS of dust bunnies away. After that, it has been much more stable.

Thanks for asking.

@all

I have an MCU connected to my X5000, and it has been very helpful!

I recently upgraded my FTDI device with this one from Amazon:

https://www.amazon.com/dp/B07RBKCW3S?p ... o2ov_dt_b_product_details

The connection was easy. The MCU header is labeled "DEBUG FTDI" and is located near the PCI connectors. The header has 6 pins.
The cable has 3 wires, Black, Green, and White. Here is how I have it connected:
PIN - Cable
1 - Black
4 - White
5 - Green

To access the MCU I use screen on Linux:

$screen /dev/ttyUSB1 38400

Here is some of the output:

>> help

command description
======= ======================================================
help Print this help list
id Identify (report h/w and f/w revisions)
id date Identify (report h/w and f/w revisions build date)
p Power up all supplies
s Shut down all supplies
q Toggle printing
v Print voltages and temperatures
OK
>> v

- vcc_cpld: 3.33
- vdd_3v3_xorro: 3.17
- vdd_1v0_idt: 1.00
- vdd_1v0_xorro: 1.00
- vdd_3v3: 3.32
- vdd_2v5: 2.47
- vdd_1v2_eth: 1.19
- vdd_pl: 1.03
- vdd_ca: 1.09
- vdd_cb: 1.09
- vdd_ddr3_io: 1.49
- vdd_xvdd_fl: 1.80


- pcb_temp: 42 deg C
- cpu_temp: 58 deg C
- pex_temp: 72 deg C


- FAN RPM: 0

OK

For the record, the serial connection settings are:
* 38400 Baud
* 8 bit data
* No Partiy
* 1 Stop bit
* No Flow Control

Enjoy!

Bill "tekmage" Borsari

@All

@ALL

I just sent mcleppa some beer money via the donation link on his site:

https://www.amateursoftwaregroup.no/about

Keep up the great work mcleppa!

Bill "tekmage" Borsari

@ALL

I just sent mcleppa some beer money via the donation link on his site:

https://www.amateursoftwaregroup.no/about

Keep up the great work mcleppa!

Bill "tekmage" Borsari

@klesterjr

This is common. To install AmiSSL I have to shutdown the following:

ZitaFTP
AAMP Apps
VNCd
Synergy

You can use "status" to see what apps are running. To end a task use "break <#>". Looks like this:

> status
Process 3: Loaded as command: AAMP:Common/bin/xlaunch
Process 4: Loaded as command: AAMP:Common/libexec/mysqld
Process 5: Loaded as command: AAMP:Common/bin/httpd
Process 9: Loaded as command: LIBS:Hollywood/polybios.ext
Process 10: Loaded as command: alt-wb:OtherUtilities/Hostsmgr-1.0/HostsMgr
Process 11: Loaded as command: sys:UHC/c/SynergyClient
Process 12: Loaded as command: Work:Internet/VNC/RVNCd/RVNCd
Process 13: Loaded as command: CSD2:Internet/ZitaFTPServer/ZitaFTPServer
Process 14: Loaded as command: FilerCX
Process 15: Loaded as command: AmIRC.os4-3.1.5
Process 16: Loaded as command: status
Process 17: Loaded as command: Odyssey
Process 19: Loaded as command: alt-wb:OtherC/wb2filer
Process 22: Loaded as command: alt-wb:OtherUtilities/Filer/Filer


To shutdown ZitaFTPServer use "break 13"

Hope this helps!
Bill "tekmage" Borsari

I just checked my Xerox Versalink 8000, and it has Airprint support! This printer has 4 paper trays and supports up to 12x18 paper. Happy to beta test and provide feedback!

Cheers,
Bill "tekmage" Borsari

@AlfredOne

Any chance of releasing some form of Multi-touch SDK? I'd love to see some games or paint programs using Multi-touch!

Cheers,
Bill

Hi balaton,

First, thank you for your work on Qemu for the AmigaOne systems; I'm super excited to see this coming to fruition.

I read through the forum here and came up with this process to git and build Qemu with AmigaOne support for my Ubuntu 20.04 Intel-based Linux box:


# git clone http://scm.osdn.net/gitroot/qmiga/qemu.git
# cd qemu
# git checkout amigaone
# ./configure
# make
# make install

The result was this:

# qemu-system-ppc -M help
Supported machines are:
40p IBM RS/6000 7020 (40p)
amigaone Eyetech AmigaOne/Mai Logic Teron
...

It looks good so far.

I then used AmiDVD to build a custom AmigaOne 4.1 Final Edition ISO image with the siliconmotion502.chip and updated both kicklayouts as directed in:

https://www.amigans.net/modules/newbb/ ... id=138684#forumpost138684

I created the u-boot-amigaone.bin and obtained the VGABIOS-lgpl-latest.bin file.

Then I start the machine with:
qemu-system-ppc \
-M amigaone \
-device VGA,romfile=VGABIOS-lgpl-latest.bin \
-device sm501 -accel tcg \
-drive if=none,id=cd \
-device ide-cd,drive=cd,bus=ide.1 \
-drive if=none,id=hd,file=AmigaOne.img,format=raw \
-device ide-hd,drive=hd,bus=ide.0 -m 2048 \
-device es1370 \
-rtc base=localtime \
-device rtl8139,netdev=network01 -netdev user,id=network01 \
-display sdl \
-serial stdio \
-d unimp,guest_errors \
-trace enable="via*"

At this point, I configured U-Boot to boot CDROM and started getting errors:

articia_reg_write: Unimplemented register write 0x80 1 <- 3a
articia_reg_write: Unimplemented register write 0x80 1 <- 3b
articia_reg_write: Unimplemented register write 0x80 1 <- 50
articia_reg_write: Unimplemented register write 0x80 1 <- 53
articia_reg_write: Unimplemented register write 0x80 1 <- 56
via_isa_write addr 0x85 val 0x3 len 0x1
via_superio_write addr 0xe2 val 0x1c
via_superio_cfg: unimplemented register 0xe2
via_superio_write addr 0xe6 val 0xde
via_superio_cfg: unimplemented register 0xe6
via_superio_write addr 0xe7 val 0xfe
via_superio_cfg: unimplemented register 0xe7
via_superio_write addr 0xe8 val 0xbe
via_superio_cfg: unimplemented register 0xe8
via_isa_write addr 0x85 val 0x1 len 0x1

Then this repeats forever:

via_isa_write addr 0x10 val 0xffffffff len 0x4
via_isa_write addr 0x14 val 0xffffffff len 0x4
via_isa_write addr 0x18 val 0xffffffff len 0x4
via_isa_write addr 0x1c val 0xffffffff len 0x4
via_isa_write addr 0x20 val 0xffffffff len 0x4
via_isa_write addr 0x24 val 0xffffffff len 0x4
via_pm_write addr 0x10 val 0xffffffff len 0x4
via_pm_write addr 0x14 val 0xffffffff len 0x4
via_pm_write addr 0x18 val 0xffffffff len 0x4
via_pm_write addr 0x1c val 0xffffffff len 0x4
via_pm_write addr 0x20 val 0xffffffff len 0x4
via_pm_write addr 0x24 val 0xffffffff len 0x4
Invalid read at addr 0xFD0E0000, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0001, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0002, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0003, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0004, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0005, size 1, region '(null)', reason: rejected
...
Invalid read at addr 0xFD0E0FFD, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0FFE, size 1, region '(null)', reason: rejected
Invalid read at addr 0xFD0E0FFF, size 1, region '(null)', reason: rejected
articia_reg_write: Unimplemented register write 0x80 1 <- b0
articia_reg_write: Unimplemented register write 0x80 1 <- b0

My virtual Sam460 is working well.

Thoughts on what I've done wrong?

cheers,
Bill "tekmage" Borsari

@all

Mr Toast put together this killer poster for AmiWest 2023, just a few weeks away!

Hi All,

I've put together a quick Devcon survey to help inform the AmiWest 2023 Devcon. You can take the survey here: https://forms.gle/S9bvJsqPzqN6TfPeA

Thanks!
Bill "tekmage" Borsari

@AmigaOldskooler

I always love reading the blog and getting a refresher on the monthly news. Also, I appreciate the AmiWest shoutout!

Cheers,
Bill

I have an X5000, and I'm also looking at getting an A1222+. I agree that limited hardware in the marketplace means every sale to an existing user does not grow our community. We know that A-Eon purchased 1500 CPUs back in the mid-2010s. We also understand that the T1022 is a challenging CPU choice due to SPE.

Let's assume AAA has used the full CPU inventory in this production run, and they will have 1500 units for sale when it's released (We don't know the production number, and there have been CPUs used in dev boards, etc., but let's assume for now.) If willing customers who already have OS 4 machines decide not to buy these systems so that other, net new AmigaOS 4 customers can, we open ourselves to more stagnation. That could create the worst-case situation with boards sitting on the shelf, unsold.

That will signal to the producers not to further invest in future boards or production. These sales generate revenue that can be used to further development. Right now, we are in a downward spire, and we need to change this to an upward spiral.

Consider this, Amedia Computer has two different OS 4 systems for sale right now, the X5000/40 and the Sam460le. All indications show that the A1222+ will be available this year too. That means we will have 3 different AmigaOS 4 compatible systems commercially available in 2023. We have not seen that since the early 2010s with AmigaOne and Sam's.

Bottom line, if you want to buy one of those boards, do it! Buy 10. The only way AmigaOS 4 will survive is if these systems sell.

We must reward those who take the risk to produce HW for our beloved OS.

Hi All,



It looks like I'm unable to reply to the news thread with links, so here are the photos I took on Friday. The Amiga's presence at the event was much more significant than I had expected. My visit was cut short, so I only at a chance to take a few photos.

Click here to view the gallery


Bill "tekmage" Borsari
Don't forget to check out AmiWest