SoPine SPI booting
#1
I pushed quite recent u-boot with sunxi and apritzel patches that allows to enable SD/eMMC/USB/PXE booting of SoPine.

This new u-boot can also be put on SPI to allow booting without SD/eMMC.

You can find sources and releases here: https://github.com/ayufan-pine64/bootloa...d/releases.
Homepage: https://ayufan.eu

Releases:
Rock/Pro 64/Pinebook Pro: LinuxChromium OS
So/Pine A64/Pinebook: LinuxAndroid 6.0Android 7.1

Buy me a Beer
  Reply
#2
Great ! Looking forward to the clusterboard for PXE booted sopine clusters at home Smile

@ayufan: As I lack knowledge related to kernel build and Linux builds for the SoPine, do you think it might be possible to "hack" the LinuxKit toolkit (https://github.com/linuxkit/linuxkit) and build SoPine compatible rootfs images instead of RPi3 images : https://github.com/linuxkit/linuxkit/blo...rm-rpi3.md ?

In this toolkit they use u-boot to start the RPi3 so I think we might even be able to adapt the process to boot from a ".img" image no ?

Thanks in advance Smile
  Reply
#3
Maybe. But I would look for 64-bit.
Homepage: https://ayufan.eu

Releases:
Rock/Pro 64/Pinebook Pro: LinuxChromium OS
So/Pine A64/Pinebook: LinuxAndroid 6.0Android 7.1

Buy me a Beer
  Reply
#4
So I am trying to use this SPI build with the new Sopine clusterboard and am having a ton of issues. It'll boot, and start looking to boot from dhcp, but it isn't connecting to the network(I don't even see a dhcp request come across when I tcpdump the upstream port). 

It works fine when a node is in the sopine baseboard, and I am also having networking issues with all images except your minimal xenial build. Things will boot, but they won't make any network requests.
  Reply
#5
(02-14-2018, 10:13 PM)aww Wrote: So I am trying to use this SPI build with the new Sopine clusterboard and am having a ton of issues. It'll boot, and start looking to boot from dhcp, but it isn't connecting to the network(I don't even see a dhcp request come across when I tcpdump the upstream port). 

It works fine when a node is in the sopine baseboard, and I am also having networking issues with all images except your minimal xenial build. Things will boot, but they won't make any network requests.

I also have not been able to get the sopines to do either BOOTP or DHCP requests when in the clusterboard, but don't have a sopine baseboard to compare against. However, with the same test setup, but substituing a rock64 which will PXE boot, I see the requests come through just fine, on dnsmasq and tcpdump.

I'm trying to set up a pine64 as a DHCP+PXE master for the clusterboard. Testing for the DHCP/BOOTP requests using:

Code:
sudo tcpdump -i eth0 port 67 or port 68 -e -n
  Reply
#6
I have the same issue. I think it lies with the fact that there are network issues on the kernel side (as explained here : https://forum.pine64.org/showthread.php?tid=5712) and this has not been fixed in @ayufan u-boot build for now. I don't have enough knowledge to create a pull request or make a new build.

@aww Could you replicate the network fix here maybe : https://github.com/ayufan-pine64/u-boot-...i-a64.dtsi ?

That way we would just have to rebuild u-boot and use @ayufan's makefiles to recreate a new version working with the clusterboard ?
That would be awesome !

EDIT: It seems you already did it ! : https://github.com/andrewl3wis/u-boot-su...41e5603dd7
  Reply
#7
(05-04-2018, 03:35 AM)hexalyn Wrote: EDIT: It seems you already did it ! : https://github.com/andrewl3wis/u-boot-su...41e5603dd7

Nice! Now just have to work out how to get it onto the sopine modules! Wink
  Reply
#8
@pfeerick : I managed to build the image using ayufan's scripts but with @aww u-boot version.
I do not have any sopine module at reach right now, could you try it ?

Here is the link to download my build : https://transfer.sh/OOvBr/u-boot-sopine-...spi.img.xz

It works the same as ayufan's as it was built in the same manner. Thanks !
  Reply
#9
That's my attempts to get it working. I wasn't successful, but I was trying things late at night so might of missed something.


I think the root issue is that ayafan's fork(and u-boot upstream) are currently missing the patches for realtek network timing that are in Mainline. The reason that rgmii-txid works in Armbian looks like a side affect of another patch that adds the "magic" timing numbers in that someone got from realtek.
  Reply
#10
@aww I see... If I understand correctly, here: https://patchwork.ozlabs.org/patch/873752/ they patch mainline u-boot with the realtek stuff.
As I have seen, every modified file in this patch has the same "pre-patch" state as the files in your modified u-boot version.
Couldn't we juste apply this patch onto your repo if this is the realtek only patch ?

Thanks
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Armbian - Xenial (SOPINE) pineadmin 6 4,742 08-05-2019, 01:17 AM
Last Post: pineadmin
  Sopine baseboard / A64 base board as OTG mixotricha 0 71 07-08-2019, 07:11 PM
Last Post: mixotricha
  LibreELEC(KODI) for LTS/ SOPine pineadmin 0 400 05-10-2019, 03:19 AM
Last Post: pineadmin
  NEMS Linux for LTS/ SOPine Luke 1 277 05-09-2019, 05:46 PM
Last Post: pineadmin
  Volumio (PINE A64-LTS / SOPINE) pineadmin 1 1,281 01-18-2019, 04:42 PM
Last Post: Luke
  SoPine/Pine64 LTS: Ubuntu Mate is not booting jaganteki 0 267 11-20-2018, 10:49 PM
Last Post: jaganteki
  Arch Linux mainline XFCE (PINE A64-LTS / SOPINE) pineadmin 1 2,111 11-09-2018, 03:07 AM
Last Post: pineadmin
  Xenial Mate @ Sopine: no graphic acceleration & high CPU load AI_newsettler 0 234 08-11-2018, 10:26 AM
Last Post: AI_newsettler
  Trying to boot archlinux-minimal-sopine-20170708-1.img kris240376 0 367 05-25-2018, 10:30 AM
Last Post: kris240376
  Sopine Complete Guide parmleyhunt 4 1,284 02-01-2018, 11:54 AM
Last Post: parmleyhunt

Forum Jump:


Users browsing this thread: 1 Guest(s)