Latest image (bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz) not booting on BBW (OK on BBB)

[Stéphane Massot]

Hello,

I have been working on a BBB from the 2015-11-12 image (debian 8.1).

It works well, so I tried to use the image in our older beaglebone (BBW) products, since it is supposed to be compatible.

However it doesn't boot ! I've tried again with the vanilla image (the same image but without my custom modifications), and it doesn't boot either.

In fact, it starts the boot operation, and after 1min30, prints some errors related to the cape manager, and then all the board's lights go off (even the ethternet LEDs), and it goes radio-silent.

You will find attached my complete boot log from the console output on USB. At first glance, what strikes me is :

"

U-Boot SPL 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19)

No AC power, disabling frequency switch

bad magic

U-Boot 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19 -0600), Build: jenkins-github_Bootloader-Builder-274

"

and then, at the end (this is with the "quiet" boot option, contrary to the attached log) :

"

Starting kernel ...

[    4.603825] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

[    5.004287] omap-sham 53100000.sham: initialization failed.

[    5.036255] cpu cpu0: cpu0 clock notifier not ready, retry

[   90.286357] irq 187: nobody cared (try booting with the "irqpoll" option)

[   90.294553] handlers:

[   90.296889] [<c009f34c>] irq_default_primary_handler threaded [<c0677db0>] tps65217_irq

[   90.305077] Disabling IRQ #187

[   90.413154] bone_capemgr bone_capemgr: slot #0: No cape found

[   90.473109] bone_capemgr bone_capemgr: slot #1: No cape found

[   90.533136] bone_capemgr bone_capemgr: slot #2: No cape found

[   90.593106] bone_capemgr bone_capemgr: slot #3: No cape found

"

 

Did I miss something ?

[Robert Nelson]

On Fri, Jan 15, 2016 at 8:53 AM, Stéphane Massot <colom...@gmail.com> wrote:

Hello,

I have been working on a BBB from the 2015-11-12 image (debian 8.1).

use weekly snapshots from:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

That 8.1 image has known issues..

 

It works well, so I tried to use the image in our older beaglebone (BBW) products, since it is supposed to be compatible.

Works fine here..

 

However it doesn't boot ! I've tried again with the vanilla image (the same image but without my custom modifications), and it doesn't boot either.

In fact, it starts the boot operation, and after 1min30, prints some errors related to the cape manager, and then all the board's lights go off (even the ethternet LEDs), and it goes radio-silent.

You will find attached my complete boot log from the console output on USB. At first glance, what strikes me is :

debug: [/boot/dtbs/4.1.12-ti-r29/am335x-boneblack-emmc-overlay.dtb] ...

Why did you do that?

The White is not the Black...

The White doesn't need the special "overlay.dtb"...

Regards,

--

Robert Nelson
https://rcn-ee.com/

[Stéphane Massot]

Le vendredi 15 janvier 2016 16:16:26 UTC+1, RobertCNelson a écrit :

On Fri, Jan 15, 2016 at 8:53 AM, Stéphane Massot <colom...@gmail.com> wrote:

Hello,

I have been working on a BBB from the 2015-11-12 image (debian 8.1).

use weekly snapshots from:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

That 8.1 image has known issues..

Alright, I moved to the bone-debian-8.2-console-armhf-2016-01-10-2gb image.

But so far I get exactly the same results.

You can find my boot log there : http://pastebin.com/WXuv6Xzm

 

It works well, so I tried to use the image in our older beaglebone (BBW) products, since it is supposed to be compatible.

Works fine here..

 

However it doesn't boot ! I've tried again with the vanilla image (the same image but without my custom modifications), and it doesn't boot either.

In fact, it starts the boot operation, and after 1min30, prints some errors related to the cape manager, and then all the board's lights go off (even the ethternet LEDs), and it goes radio-silent.

You will find attached my complete boot log from the console output on USB. At first glance, what strikes me is :

debug: [/boot/dtbs/4.1.12-ti-r29/am335x-boneblack-emmc-overlay.dtb] ...

Why did you do that?

The White is not the Black...

The White doesn't need the special "overlay.dtb"...

My bad, I had removed the corresponding line from uEnv.txt; but I forgot to uncomment "dtb=", so it was still set.

I corrected that, but it didn't solve my problem so far.

Thanks for your help.

Regards,

-- 

Stéphane Massot