Page 2 of 2

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Fri May 25, 2018 8:20 pm
by Skateman
Yep

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Sat Jun 02, 2018 5:41 am
by chmeee
Skateman wrote:Like mentioned in the FreeBSD readme i have adjusted the setenv loadaddr from 1000000 to 0x3ffffc0

Ubuntu booted and all functional. The DPAA network issues still appear. To bad..
I will revert the the setenv loadaddr 0x3ffffc0 to 1000000

It was worth the try :-)


Did it boot at all, and fail to attach the ethernet controller? I've been running FreeBSD on my X5000 for 6 months without any major issues. One thing to note, if the ethernet controller is just failing, the device tree may need updated. The device tree included with Linux is incomplete/incorrect, as the X5000 PHYs are attached via RGMII, not TBI. I have a device tree that works, at https://people.freebsd.org/~jhibbits/cy ... _amiga.dts , that you will need to compile with: dtc -I dts -O dtb -s 65536 -o cyrus_p5020_amiga.dtb cyrus_p5020_amiga.dts . The "-s 65536" is important, so that there's enough room for uboot fixups.

If you have a good device tree, or your kernel just isn't booting at all (gets stuck before even printing the Copyright message) you may need to recompile your dtb file to grow it, as mentioned above.

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Sat Jun 02, 2018 10:46 pm
by xeno74
Hi All,

Here you are:

Download: cyrus_p5020_x5000.dtb

Compiled with the command:

Code: Select all
dtc -I dts -O dtb -S 65536 -o cyrus_p5020_x5000.dtb cyrus_p5020_amiga.dts


Download: cyrus_p5020_x5000-2.dtb

Compiled with the command:

Code: Select all
dtc -I dts -O dtb -S 131072 -o cyrus_p5020_x5000-2.dtb cyrus_p5020_amiga.dts


Download: cyrus_p5020_x5000-3.dtb

Compiled with the command:

Code: Select all
make CROSS_COMPILE=powerpc-linux-gnu- ARCH=powerpc cyrus_p5020.dtb


Code: Select all
cp arch/powerpc/boot/cyrus_p5020.dtb ../cyrus_p5020_x5000-3.dtb


Please test them.

Thanks,
Christian

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Sun Jun 03, 2018 10:29 pm
by Skateman
@Xeno74

Just replacing the new Blob for the one i am using now does not solve the DPAA network issues.
I have tried all three but not luck yet.

I will spend some more time on this later.

Thanks

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Mon Jun 04, 2018 8:45 am
by xeno74
Skateman wrote:@Xeno74

Just replacing the new Blob for the one i am using now does not solve the DPAA network issues.
I have tried all three but not luck yet.

I will spend some more time on this later.

Thanks


Thank you for testing. Were you able to boot the X5000 with all three blobs?

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Mon Jun 04, 2018 2:36 pm
by Skateman
Yeah the X5000 booted without problems with all blobs

Re: AmigaOne X5000 - FreeBSD Only

PostPosted: Mon Jun 04, 2018 10:50 pm
by daz
chmeee wrote:
Skateman wrote:Like mentioned in the FreeBSD readme i have adjusted the setenv loadaddr from 1000000 to 0x3ffffc0

Ubuntu booted and all functional. The DPAA network issues still appear. To bad..
I will revert the the setenv loadaddr 0x3ffffc0 to 1000000

It was worth the try :-)


Did it boot at all, and fail to attach the ethernet controller? I've been running FreeBSD on my X5000 for 6 months without any major issues. One thing to note, if the ethernet controller is just failing, the device tree may need updated. The device tree included with Linux is incomplete/incorrect, as the X5000 PHYs are attached via RGMII, not TBI. I have a device tree that works, at https://people.freebsd.org/~jhibbits/cy ... _amiga.dts , that you will need to compile with: dtc -I dts -O dtb -s 65536 -o cyrus_p5020_amiga.dtb cyrus_p5020_amiga.dts . The "-s 65536" is important, so that there's enough room for uboot fixups.

If you have a good device tree, or your kernel just isn't booting at all (gets stuck before even printing the Copyright message) you may need to recompile your dtb file to grow it, as mentioned above.


I've had a look at this (yuk, it'd be a lot easier to read if you used symbols for phandles) and the changes seem to be the same as the ones we tried last year/earlier this year.

We've had the ethernet running with kernels derived from NXP's SDK, but not from main line. Where have you got your driver from? Can you try one of our hacked dtb files and see if it boots OK on FreeBSD? If it does we know we need to hassle the NXP guys to get it fixed. They think it could be an iommu config error in our firmware, which I assume would also break your driver.

Can you try the one here, seems to be the best option.
http://forum.hyperion-entertainment.biz/viewtopic.php?f=58&t=3945

Thanks
Darren