We are developing an instrument based on the i.MX 6 and have worked with the alpha and beta releases of Android Lollipop on the Sabre-SD board. The issue is, we want to boot the board through TFTP/NFS but don't know how to, there is also not enough information on the UserGuide of the releases. Can you give me the guidance for booting from NFS/TFTP?
More detailed information:
1. It is okay to load a kernel image through u-boot/TFTP to the memory (0x10008000) of the Sabre-SD board.
2. The uImage is used (compiled with "make uImage LOADADDR=0x10008000), per the user guide of the beta release.
3. I noticed it is necessary for 4.4.3 to set device tree information, should we do this too? But how to specify the addresses?
Here is the u-boot log. It stopped after printing the line "Starting kernel ..."
FEC Waiting for PHY auto negotiation to complete.. done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 129.196.210.225
Using FEC device
TFTP from server 129.196.211.60; our IP address is 129.196.210.225
Filename 'uImage'.
Load address: 0x10008000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##########
1.8 MiB/s
done
Bytes transferred = 6814664 (67fbc8 hex)
## Booting kernel from Legacy Image at 10008000 ...
Image Name: Linux-3.10.53-88177-g589371c
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6814600 Bytes = 6.5 MiB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
No gpc device node -9, force to ldo-enable.
Starting kernel ...
Hello Huanxin,
Now that Lollipop is released are you able to boot through TFTP?
Hi Sergio,
Yes the GA release supports boot through TFTP but I followed the kk.4.4.3 doc (there is no doc about this on 5.0's user guide). It works for me although I rarely use it due to other reasons.
thanks,
Huanxin
Nice to know that it works over NFS.
But I tried it with no success.
When executing "class_start main", eth0 stop so it died...
Is it possible to have your patchs in init.rc & init.freescale.rc to support NFS
Best regards.
HI All,
I am using:
Android™ User's Guide, Rev. L5.0.0_1.0.0-ga, 06/2015
In the doc, there is not info about how to do NFS boot.
I managed this following kk4.3.3 doc.
and can download img and start kernel.
However, there is a problem after started the kernel.
see the bold lines, after that, it seems board cannot have an IP anymore.
Something is wrong in the image.
in Ubuntu, I ping the board all the time, after the the kernel started, I can still ping the brd.
however, after thie msg:
nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Ubuntu ping has no resp anymore.
Something is wrong in the image.
Compare this with KK4.4.3 NFS, I can ping board all the time after kernel started.
Anyone can help on this?
Alan
===============================================
ALSA device list:
#0: wm8962-audio
#1: imx-hdmi-soc
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 340K (80e7b000 - 80ed0000)
init: /dev/hw_random not found
Console: switching to colour dummy device 80x30
init: /dev/hw_random not found
rfkill: BT RF going to : off
init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'
binder: 147:147 transaction failed 29189, size 0-0
init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery'
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno'
init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial'
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
ñread descriptors
read strings
mtp_bind_config
android_work: sent uevent USB_STATE=CONNECTED
android_work: sent uevent USB_STATE=DISCONNECTED
android_work: sent uevent USB_STATE=CONNECTED
android_usb gadget: high-speed config #1: android
android_work: sent uevent USB_STATE=CONFIGURED
healthd: BatteryTemperaturePath not found
healthd: BatteryTechnologyPath not found
root@sabresd_6dq:/ # nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
root@sabresd_6dq:/ # nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
I added this
androidboot.selinux=disabled androidboot.dm_verity=disabled
in bootarg to get my result.
ow, it died early.
Sometimes, nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
does not comes out.
However, ping lost resp around the bold part.
Alan
===============
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
android_usb: already disabled
read descriptors
read strings
mtp_bind_config
android_work: sent uevent USB_STATE=CONNECTED
android_work: sent uevent USB_STATE=DISCONNECTED
android_work: sent uevent USB_STATE=CONNECTED
android_usb gadget: high-speed config #1: android
android_work: sent uevent USB_STATE=CONFIGURED
binder: 147:147 transaction failed 29189, size 0-0
root@sabresd_6dq:/ # healthd: BatteryTemperaturePath not found
healthd: BatteryTechnologyPath not found
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying
nfs: server 10.68.1.88 not responding, still trying