Difference between TI and bone kernels.

GoogleGroups
1

uEnv.txt

bootdelay=1

uname_r=4.2.0-rc4-bone2

ipaddr=192.168.254.205
static_ip=192.168.254.205:192.168.254.162:192.168.254.254:255.255.255.0:xanbustester
serverip=192.168.254.162
gatewayip=192.168.254.254
rootpath=/home/william/xanbus
optargs=ipv6.disable=1

loadximage=load mmc 0:1 0x80300000 vmlinuz-${uname_r}
loadxfdt=load mmc 0:1 0x815f0000 /dtbs/${uname_r}/am335x-boneblack.dtb
loadall=run loadximage; run loadxfdt;

netargs=setenv bootargs console=tty0 console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},vers=3 rw ip=${static_ip}
uenvcmd=setenv autoload no; run loadall; run netargs; bootz 0x80300000 - 0x815f0000;

Ok, so this works,. board boots fine - Everything is happy. But change uname_r to uname_r=4.1.4-ti-r8.1 - It does not work. It leaves me in an infinite boot loop. Can anyone spot anything I’ve missed ? I haven’t run depmod yet, but haven’t had the chance . . .

william@xanbustester:~$ ls /boot/uboot/
MLO config-4.1.4-ti-r8.1 u-boot.img vmlinuz-4.1.4-ti-r8.1
System.map-4.1.4-ti-r8.1 config-4.2.0-rc4-bone2 uEnv.txt vmlinuz-4.2.0-rc4-bone2
System.map-4.2.0-rc4-bone2 dtbs uEnv.txt.bak zImage
william@xanbustester:~$ ls /boot/uboot/dtbs/
4.1.4-ti-r8.1 4.2.0-rc4-bone2
william@xanbustester:~$ ls /boot/uboot/dtbs/4.1.4-ti-r8.1/
am335x-arduino-tre.dtb am335x-boneblack-overlay.dtb am335x-lxm.dtb am43x-epos-evm.dtb
am335x-base0033.dtb am335x-boneblack-replicape.dtb am335x-nano.dtb am57xx-beagle-x15.dtb
am335x-bone.dtb am335x-boneblack-wl1835mod.dtb am335x-pepper.dtb am57xx-evm.dtb
am335x-boneblack-bbb-exp-c.dtb am335x-boneblack.dtb am437x-gp-evm-hdmi.dtb dra7-evm.dtb
am335x-boneblack-bbb-exp-r.dtb am335x-bonegreen.dtb am437x-gp-evm.dtb dra72-evm.dtb
am335x-boneblack-emmc-overlay.dtb am335x-chiliboard.dtb am437x-idk-evm.dtb omap5-cm-t54.dtb
am335x-boneblack-hdmi-overlay.dtb am335x-evm.dtb am437x-sk-evm.dtb omap5-sbc-t54.dtb
am335x-boneblack-nhdmi-overlay.dtb am335x-evmsk.dtb am43x-epos-evm-hdmi.dtb omap5-uevm.dtb

2

By the way . . .

william@xanbustester:~$ cat /etc/fstab

UNCONFIGURED FSTAB FOR BASE SYSTEM

/dev/nfs / nfs defaults 0 0
/dev/mmcblk0p1 /boot/uboot auto defaults 0 0

3

Anyhow, this is the kernel’s fault. Somehow it’s different, and to be honest I do not have the time or energy to mess with it.

4

It was config_mii=m.... yeah we need that =y for nfs root, as the phy
won't load.. kernel fix pushed out...

Regards,

5

It was config_mii=m… yeah we need that =y for nfs root, as the phy
won’t load… kernel fix pushed out…

Regards,

Yeah figured it was something like that. Was a bit upset at the time . . . Had just spent all day messing with that, among many other things related - When All I wanted to do was write code . . . So, just took the easiest shortest route to getting the kernel stable - shorting Vusb to USB ground.

Had to power down the board yesterday( switched to generator from solar ), otherwise I’d be pushing a 2 day uptime.

Thank you for the fix :slight_smile: