@geennaam

Yes same write then verify process for all 3 chips with an offline programmer.
2 work and 1 does not .
also the replacement SST39lF040 chip from ACube does not.
Reads ok as I copied the contents and used to flash the 3
ATMEL AT4BV040B chips.

So your theories re "timing or voltage issue that shows up as a batch related issue" are on the table.

The update process for two of my ATMEL AT4BV040B failed with the ACube updater .

@m3x

Did some more testing today.

Re flashed an AT4BV040B from a Sam440ep-flex with Uboot 2015.b and that works .
Seems that that actual working eeprom from yesterday was actually from the old Sam460ex board and not the current one .

So Working eeproms

-----------------------------------------------
ATMEL AT4BV040B
JU
0834
(From Sam440ef-Flex)
----------------------------------------------
ATMEL AT4BV040B
JU
0906
(From Old Sam460ex)
---------------------------------------------

Not Working

----------------------------------------------
ATMEL AT4BV040B
JU
0907
(From Current Sam460ex)
---------------------------------------------
SST39lF040
55-4C-NHE
214274C
(Replacement from Acube)
---------------------------------------------

@trixie

Took me a day and a half to work this one out by myself
when I got my X5000/40 motherboard .
As mine was a replacement/upgrade deal it was just the bare board
and no emergency boot media .


Quote:

@Isense


Good Luck.

@m3x

Thanks for your assistance .

Finally got My Sam460ex up and running today.

For some reason I cant get the Sam460ex to boot using the replacement U-Boot eeprom from A-Cube with U-boot 2015-b.
The image is good as I saved it and used it to re flash my original eeprom which allows the Sam460 to boot.

Also have the problem of no boot with my oldest eeprom from a damaged Sam460ex. this I also flashed with the same U-boot image form the newest ACube replacement that works with the original eeprom. Weird .

Took this long to get a eeprom programmer then further delay
in getting the PLCC-32 Socket to DIP-32 Adapter that was not actually included .
UPS also misplaced the incoming replacement eeprom from Acube for about a month.


Quote:

@Isense

If this is the X5000/40 then the USB drivers on the install ISO does not work.

Solution is to create a custom ISO or USBBoot drive replacing ehci.usbhcd with the version from the AmigaOS 4.1FE update2 archive or the mouse and keyboard wont work.

See the following thread :
https://forum.hyperion-entertainment.com/viewtopic.php?f=57&t=4852

@Hans


Nobody has managed to get DRM working properly on Sam460 machines with anything from Radeon RV515 cards onwards.

@m3x

there were some lock ups with the DMA under linux with newer Kernels if I recall correctly .

https://lore.kernel.org/lkml/146126254 ... evchenko@linux.intel.com/

Also GART seem to be enabled but ring test for hardware acceleration failed .

[ 3.121797] [drm] radeon: dpm initialized
[ 3.128222] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[ 3.134469] [drm] GART: num cpu pages 524288, num gpu pages 524288
[ 3.151139] [drm] probing gen 2 caps for device aaa1:bed1 = 18cc41/0
[ 3.210767] [drm] PCIE GART of 2048M enabled (table at 0x00000000002E8000).
[ 3.218077] radeon 0000:81:00.0: WB enabled
[ 3.222320] radeon 0000:81:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xee962c00
[ 3.232441] radeon 0000:81:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xee962c04
[ 3.242562] radeon 0000:81:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xee962c08
[ 3.252683] radeon 0000:81:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xee962c0c
[ 3.262805] radeon 0000:81:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xee962c10
[ 3.304324] radeon 0000:81:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xf5135a18
[ 3.341458] radeon 0000:81:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0xee962c18
[ 3.351618] radeon 0000:81:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0xee962c1c
[ 3.361759] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.368404] [drm] Driver supports precise vblank timestamp query.
[ 3.374523] radeon 0000:81:00.0: radeon: MSI limited to 32-bit
[ 3.380446] genirq: Setting trigger mode 3 for irq 45 failed (uic_set_irq_type+0x0/0x160)
[ 3.388716] radeon 0000:81:00.0: radeon: using MSI.
[ 3.393673] [drm] radeon: irq initialized.
[ 4.152902] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
[ 4.161744] radeon 0000:81:00.0: disabling GPU acceleration

@amiganuts

U-Boot is not displayed on Sam460 models currently when using a Radeon Rx card.


Can you check to make sure of the following :

Check the following re the Radeon RX driver installation :


In the file System:Kickstart/kicklayout make sure you that have the following line :

MODULE Kickstart/RadeonRX.chip

in the same directory System:Kickstart/

Make sure you have the following file :

RadeonRX.chip

@PixelHi

Can't answer that.
But Looks like the Sam460ex version may not be available via Amistore until some bug fixes are released.
I would say that is a good think though.

Quote:

@PixelHi

If the R7 240 and 250 show U-Boot then there is a chance
that they may work with RadeonHD drivers after V5.14 .

@PixelHi

Check the following re the Radeon RX driver installation :


In the file System:Kickstart/kicklayout make sure you that have the following line :

MODULE Kickstart/RadeonRX.chip

in the same directory System:Kickstart/

Make sure you have the following file :

RadeonRX.chip

@PixelHi

If you only intend to run AmigaOS 4.1 then the Radeon RX cards are the best option (RX550 or RX560), The latest drivers Radeon RX drivers are available through the A-Eon Enhancer and the A-Eon Updater app.

If you intend to use a Radeon HD card then the best working diver version for the Sam460 models , a bug fixed version of the Radeon HD 5.x with specific fixes for the Sam460 has not been released yet .

I had lock up problems problems on boot with the RadeonHD v3.7 driver version included with the A-Eon Enhancer and also the released Radeon HD 5.x versions . The released 5.x version would work for 2D with the compositing effects turned off.
Note I only used Radeon HD cards for beta testing .
The Radeon HD card I use is an OEM Radeon HD8570 which uses the Oland Chip set .

@PixelHi

Re: R7 240 and 250 .

Try booting with Compositing effects turned of in the Gui prefs.
You would have to change the settings with a working card then change cards and restart the machine unless yo have a bootable
USB drive of some sort with gui settings disabled in prefs.

Most of the Sam460ex issues with this were fixed in a Radeon HD 5.x update that has not been released yet .

@sacc-dude

U-Boot issue indeed .
Some keyboards work some don't .
I have some simple Microsoft and Kensington wired ones that work.
The A-Eon AmigaOne keyboard has the same issue.

@amiganuts

Newer model Sil3112 cards seem to have that problem .
Have one that exhibits the same kinds of issues.

Have 3 of a very old model that work well with standards hard drives. Using one in the Sam460ex and one in my X5000 also .

Have not been able to get my only SSD a (Samsung 250GB model) to work without errors on the Sam46ex with either the working sil3112's, a sil3114 or the sil3512 that came with the original Sam460ex (Both the sil3512 and sil3114 came from Acube).

The SSD does work with the X4000/40 on board sata an that is were I am using it.

@amiganuts


I you have another working AmigaOS 4.1 machine you can create a bootable SDcard with the RadeonRX driver for the Sam460ex using that machine .

Create a Bootable USB Option

Mainstream ones that should work

https://www.amazon.com/OWC-PC2-6400-80 ... pgrade/dp/B00KHK3G5Y?th=1

@geennaam


Nice.
The Previous Sam460ex models and u-boot did not seem to cards other than Ethernet and Audio cards in the pciex1 slot though .

@amiganuts

Some X5000/40 Issues exist in U-Boot

MorphZone Post #1

MorphZone Post #2

SSolie has also said that he has solved some USB issues in the X5000 Uboot at AmiWest 2022. But no release timeline .