Jump to content

Recommended Posts

Posted

So this is failing for some odd reason. Armbian command line configuration is:

 

/compile.sh BOARD=nanopik1plus BRANCH=next KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=jessie BUILD_DESKTOP=no ROOTFS_TYPE=fel

 

FEL device mode is activated:

 

@ubuntu-1804:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 1f3a:efe8 Onda (unverified) V972 tablet in flashing mode
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 

Armbian interaction is then ...

[ o.k. ] Calling image customization script [ customize-image.sh ]
[ o.k. ] Starting FEL boot [ nanopik1plus ]
[ o.k. ] Connect device in FEL mode and press [ <Enter> ]

[ o.k. ] Loading files via [ FEL USB ]
Failed to open input file: No such file or directory
[ o.k. ] Press any key to boot again, <q> to finish [ FEL ]


[ o.k. ] Connect device in FEL mode and press [ <Enter> ]

[ o.k. ] Loading files via [ FEL USB ]
Failed to open input file: No such file or directory
[ o.k. ] Press any key to boot again, <q> to finish [ FEL ]

 

Posted
Just now, g40 said:

Thanks. Have you had any 64bit boards working with NFS? 

No.

Root on NFS should not be hard by itself (similar to H3, loading u-boot and kernel from SD).

FEL support, on the other hand, is not implemented in the mainline u-boot for 64-bit chips, so it requires either using prebuilt u-boot binaries or adding patches to u-boot and rewriting the build script.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines