Used debian image:
I booted it from SD Card and then i did:
./update_kernel.sh --bone-kernel --lts-4_4
For now system starts from SD Card fine, but when I try flash eMMC with SD content nothing happend - all leds for a second lights up then no cylon light.
I have uncommented flash cmdline in /boot/uEnv.txt.
If I call flash script manually after system up from SD it starts flashing eMMC but after reboot system wont start from eMMC.
It looks like the device nodes:
are not automaticlly being created in 4.4.39-bone14
okay, 4.1.x get's passed that:
./update_kernel.sh --bone-kernel --lts-4_1
I'll start comparing 4.1.36-bone24 vs 4.4.39-bone14
I did test with TI Kernel:
./update_kernel.sh --ti-channel --lts-4_4
flash eMMC from SD proces started: few cylon led sequence and now all leds are on.
What’s main difference betwen bone and TI kernel? I saw in dmesg log that bone kernel not support omap-shim (whatever it is).
It's a kernel configuration regression in wheezy (which doesn't get
tested anymore).. I've got a version of v4.4.x-bone that works, just
minimizing the config down to the actual breakage..
bone = upstream base + our stuff
ti = upstream base + ti tree + our stuff
I gave a second chance to TI kernel to flash eMMC from SD and it was successful - cylon leds then all leds on and auto power off. So now I have working wheezy with 4.4.39-ti-r75 kernel.
I’ve looked to jessie debian images and I saw that there is TI kernel used - I guess this is the right direction to follow that kernel now and in the future?
the v4.4.x-ti is the default, but the "bone" is slightly more
optimized for the am335x (being a single core)
v4.4.x-bone is now fixed:
and pushed out as 4.4.39-bone15/4.4.39-bone-rt-r15, it'll be in the
apt repo sometime this weekend..