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**[ 0.784820] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8**[ 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* Loading, please wait... Scanning for Btrfs filesystems systemd-fsck[289]: rootfs: clean, 58181/230144 files, 359918/919296 blocks*[ 5.659576] c_can_platform 481cc000.d_can: invalid resource [ 5.709232] c_can_platform 481d0000.d_can: invalid resource* [ 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. On Mon, Mar 20, 2017 at 5:05 PM, maxmike <[email protected]> wrote: > > Hi Robert - had to get serial cable - the log is attached. > > On Monday, March 20, 2017 at 10:55:25 AM UTC-7, RobertCNelson wrote: >> >> 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, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/aef78e11-d77a-4e0f-b7c2-0666bc640709%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/aef78e11-d77a-4e0f-b7c2-0666bc640709%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrXis_iYCW_iFZmDyCYjiohzJzTYgTFv8KKRivXC3rqEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
