BeagleBone Black Industrial 4G compliant BBB logo?

GoogleGroups
1

Hi, ALL

I found some BeagleBoard.

That is BeagleBone Black Industrial 4G provided by elemnt14 as below:

-element14 BeagleBone Black Industrial 4G

http://www.element14.com/community/docs/DOC-78671/l/element14-beaglebone-black-industrial-4g

So, I have some questions:

1)Does element14 compliant the BeagleBoard Compliant Logo?

2)Does the “BeagleBone Black Industrial 4G” acquire BeagleBoard Compliant and certification?

In product folder of element14, it describes that the board has compliant:

Is it correct?

-Current “beagleboard compliant” logo licensee(s):

Element14 BeagleBone Black

http://beagleboard.org/logo

best regards,

kytkg

2

Ask Element 14. They are the ones making the claim.

Gerald

3

I cross-posted this elsewhere - here might be more appropriate.

I have now ordered extended temp. BBB’s from two different sources and both failed to work.
We use them by first loading Debian 3.8.13-bone50 via the USB stick.
In one case it failed to boot (just power light on), in the other it sometimes power boots, sometimes not and
even if it boots, it doesn’t load the drivers for the USB stick consistently.

Never had any problems with the std. units, even loading a 2GB OS and then running resize2fs.

4

I cross-posted this elsewhere - here might be more appropriate.

I have now ordered extended temp. BBB's from two different sources and
both failed to work.
We use them by first loading Debian 3.8.13-bone50 via the USB stick.
In one case it failed to boot (just power light on), in the other it
sometimes power boots, sometimes not and
even if it boots, it doesn't load the drivers for the USB stick
consistently.

Never had any problems with the std. units, even loading a 2GB OS and then
running resize2fs.

Can you share your serial boot log?

My guess, it's the newer eMMC used on the board..

around bone80 ( Jun 15, 2016 ) we added support for v5.1 emmc..

But since your light on the details, that's just a guess..

Regards,

5

A serial log? Haven’t done that in years - need to find/dust off the hardware cables for that. Will try - thanks.

6

remember 3.3v serial only

7

I used to work with BBB std and BBB industrial from element14. My favorite is BBB industrial. Never fail, no errors with Debian 7.5, 8.4, 8.7-rt.
Alex

8

Hi Robert - had to get serial cable - the log is attached.

boot log.txt (2.86 KB)

9

That almost looks like the eeprom is messed up. But that uboot is probably ~3 years old too, and the kernel is probably equally as old( roughly ). Anyway . . .

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
**[    0.378237] omap2_mbox_probe: platform not supported**
**[    0.532863] tps65217-bl tps65217-bl: no platform data provided**
[    0.596721] bone-capemgr bone_capemgr.9: slot #0: No cape found
[    0.633829] bone-capemgr bone_capemgr.9: slot #1: No cape found
[    0.670938] bone-capemgr bone_capemgr.9: slot #2: No cape found
[    0.708047] bone-capemgr bone_capemgr.9: slot #3: No cape found
**[    0.749535] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed**
<b>[    0.784820] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by
 44e10800.pinmux; cannot claim for gpio-leds.8</b>
<b>[    0.796524] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[    0.803808] pinctrl-single 44e10800.pinmux: could not request pin 21 on devic
e pinctrl-single</b>
Loading, please wait...
Scanning for Btrfs filesystems
systemd-fsck[289]: rootfs: clean, 58181/230144 files, 359918/919296 blocks
<b>[    5.659576] c_can_platform 481cc000.d_can: invalid resource
[    5.709232] c_can_platform 481d0000.d_can: invalid resource</b>
[    7.601032] libphy: PHY 4a101000.mdio:01 not found
[    7.606104] net eth0: phy 4a101000.mdio:01 not found on slave 1


None  of that in bold is god news, but it starts here: **[    0.378237] omap2_mbox_probe: platform not supported** 


Which could be an indication that the on board eeprom somehow got corrupted, which is fixable. But let's see what Robert has to say first.
10

Since Robert isn’t saying I assume he’s talking to the factory - I’ll ship them back.

11

Nope, been traveling for the day job. Nothing obvious in your serial boot log. Just give the 3/19 image a try, probably work fine.

Regards,

12

So we can’t move a 2G quasi-production image from std BBB to the industrial 4G BBB? I have to build a whole new image?
And - “probably” work fine? Not exactly a smooth upgrade path. How do I even go from Debian 3.8.13-bone50 to whatever
3/19 is without having to do a selective backup. Is that an official designation - 3/19? Can’t find it.
I’d like to stick to Debian, but this is kind of a major bump.

13

So we can't move a 2G quasi-production image from std BBB to the industrial
4G BBB? I have to build a whole new image?

I didn't say that.. I "said" try 3/19, feel free to stay on
3.8.13-bone50 for as long as you like. (i don't give a rat's ass about
supporting 3.8.13-boneX line)

And - "probably" work fine? Not exactly a smooth upgrade path. How do I even
go from Debian 3.8.13-bone50 to whatever
3/19 is without having to do a selective backup. Is that an official
designation - 3/19? Can't find it.
I'd like to stick to Debian, but this is kind of a major bump.

Regards,

14

I use Debian 3.8.13-bone50 and -bone79 on few my BBB industriasl with no issues. 5 BBB industrial had been deployed into production field of my company for December-January. Others BBB industrial set with Debian 8.4, not in deployment yet, but 8.7 is in deployment for a month so far. No issues
Alex

15

Thank you Alexander - how do you load them?
I just do a dd from my backup image on the USB stick onto /dev/mmcblk1, running from a bone40 sd.