Unable to access/talk to BBB after netinstalling Ubuntu

46 views
Skip to first unread message

SriRam Chadalavada

unread,
Apr 26, 2016, 6:11:42 PM4/26/16
to BeagleBoard
I am unable to access/talk to my Beaglebone Black after doing a fresh netinstall with the following command:
sudo ./mk_mmc.sh --mmc /dev/mmcblk0 --firmware --serial-mode --dtb am335x-boneblack --distro trusty

It neither shows up connected with ethernet on my network nor does the serial console connectivity display anything. And I had tried this precise method earlier and both ways to access the device were working just fine.

Please find a screenshot of the files on the programmed microSD card attached. Any help to resolve will be much appreciated!
bbb_microsd_image.jpg

William Hermans

unread,
Apr 26, 2016, 7:10:05 PM4/26/16
to beagl...@googlegroups.com
Maybe you aught to buy a serial debug cable, and see why it doesn't work. There are probably 100's of reason why this could have failed, for which a single person could probably make a different guess a day, for the next 6 months, and still guess wrong.

Passed that, only one person on this group could really start guessing, as he wrote that script, and knows how it works.

--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6de0c41a-eda8-4813-b978-43e4a3f6a2e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Robert Nelson

unread,
Apr 26, 2016, 7:51:12 PM4/26/16
to Beagle Board
On Tue, Apr 26, 2016 at 5:11 PM, SriRam Chadalavada <chsr...@gmail.com> wrote:
I am unable to access/talk to my Beaglebone Black after doing a fresh netinstall with the following command:
sudo ./mk_mmc.sh --mmc /dev/mmcblk0 --firmware --serial-mode --dtb am335x-boneblack --distro trusty

"--serial-mode" implies connecting a physical serial port to the debug header on the black. ;)

Regards,

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

Sriram Chadalavada

unread,
Apr 27, 2016, 2:49:50 PM4/27/16
to beagl...@googlegroups.com
I did have a serial debug cable connected :). Turned out the right angle serial connector between the cable and the J1  went bad.

But the BBB seems to be booting into the default debian in the eMMC rather than the Ubuntu programmed into the microSD card using netinstall.

Here's the output: 

U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_B5

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw


Is the SD card being recognized correctly by uboot?


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/GyKN6K8esa0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYioShijrz4bkYkF%2BZOGXcsZ8oxjbfZzn8%3D1yFxwEHxM2g%40mail.gmail.com.

Robert Nelson

unread,
Apr 27, 2016, 2:56:07 PM4/27/16
to Beagle Board
On Wed, Apr 27, 2016 at 1:49 PM, Sriram Chadalavada <chsr...@gmail.com> wrote:
I did have a serial debug cable connected :). Turned out the right angle serial connector between the cable and the J1  went bad.

But the BBB seems to be booting into the default debian in the eMMC rather than the Ubuntu programmed into the microSD card using netinstall.

Here's the output: 

U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_B5

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw


Is the SD card being recognized correctly by uboot?

boot into the eMMC and:

sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=10

u-boot gone from the eMMC ;)

Regards,

Sriram Chadalavada

unread,
Apr 27, 2016, 3:04:35 PM4/27/16
to beagl...@googlegroups.com
u-boot gone from the eMMC ;)

I could do that but if it truly isn't recognizing the microSD, wouldn't formatting eMMC render it non-usable? I'm not that familiar with BBB, have not played around with U-boot off late nor have JTAG etc , so would rather not take a chance. Did the output indicate that the microSD is NOT being recognized? Thanks!
Regards,
--
Robert Nelson
https://rcn-ee.com/

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/GyKN6K8esa0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Robert Nelson

unread,
Apr 27, 2016, 3:08:09 PM4/27/16
to Beagle Board
On Wed, Apr 27, 2016 at 2:04 PM, Sriram Chadalavada <chsr...@gmail.com> wrote:


On Wed, Apr 27, 2016 at 1:55 PM, Robert Nelson <robert...@gmail.com> wrote:


On Wed, Apr 27, 2016 at 1:49 PM, Sriram Chadalavada <chsr...@gmail.com> wrote:
I did have a serial debug cable connected :). Turned out the right angle serial connector between the cable and the J1  went bad.

But the BBB seems to be booting into the default debian in the eMMC rather than the Ubuntu programmed into the microSD card using netinstall.

Here's the output: 

U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_B5

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw


Is the SD card being recognized correctly by uboot?

boot into the eMMC and:

sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=1

u-boot gone from the eMMC ;)

I could do that but if it truly isn't recognizing the microSD, wouldn't formatting eMMC render it non-usable? I'm not that familiar with BBB, have not played around with U-boot off late nor have JTAG etc , so would rather not take a chance. Did the output indicate that the microSD is NOT being recognized? Thanks!

Nope, you cut it off too early..

Regards,

Sriram Chadalavada

unread,
Apr 27, 2016, 3:15:19 PM4/27/16
to beagl...@googlegroups.com
Here's more output. Thanks!

U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)


U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_B5

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0                                                
gpio: pin 53 (gpio 53) value is 1                                               
Card did not respond to voltage select!                                         
Card did not respond to voltage select!                                         
gpio: pin 56 (gpio 56) value is 0                                               
gpio: pin 55 (gpio 55) value is 0                                               
gpio: pin 54 (gpio 54) value is 0                                               
switch to partitions #0, OK                                                     
mmc1(part 0) is current device                                                  
gpio: pin 54 (gpio 54) value is 1                                               
Failed to mount ext2 filesystem...                                              
** Unrecognized filesystem type **                                              
Checking for: /uEnv.txt ...                                                     
Failed to mount ext2 filesystem...                                              
** Unrecognized filesystem type **                                              
Checking for: /boot.scr ...                                                     
Failed to mount ext2 filesystem...                                              
** Unrecognized filesystem type **                                              
Checking for: /boot/boot.scr ...                                                
Failed to mount ext2 filesystem...                                              
** Unrecognized filesystem type **                                              
Checking for: /boot/uEnv.txt ...                                                
Failed to mount ext2 filesystem...                                              
** Unrecognized filesystem type **                                              
gpio: pin 55 (gpio 55) value is 1                                               
818 bytes read in 28 ms (28.3 KiB/s)                                            
Loaded environment from /boot/uEnv.txt                                          
Checking if uname_r is set in /boot/uEnv.txt...                                 
gpio: pin 56 (gpio 56) value is 1                                               
Running uname_boot ...                                                          
loading /boot/vmlinuz-3.8.13-bone70 ...                                         
5617184 bytes read in 344 ms (15.6 MiB/s)                                       
loading /boot/dtbs/3.8.13-bone70/am335x-boneblack.dtb ...                       
26098 bytes read in 38 ms (669.9 KiB/s)                                         
loading /boot/initrd.img-3.8.13-bone70 ...                                      
2867606 bytes read in 190 ms (14.4 MiB/s)                                       
debug: [console=ttyO0,115200n8 root=UUID=8b8367b0-c090-4d28-8d50-309dd3f2d4b1 r.
debug: [bootz 0x82000000 0x88080000:2bc196 0x88000000] ...                      
Kernel image @ 0x82000000 [ 0x000000 - 0x55b620 ]                               
## Flattened Device Tree blob at 88000000                                       
   Booting using the fdt blob at 0x88000000                                     
   Loading Ramdisk to 8fd43000, end 8ffff196 ... OK                             
   Loading Device Tree to 8fd39000, end 8fd425f1 ... OK                         
                                                                                
Starting kernel ...                                                             
                                                                                
Uncompressing Linux... done, booting the kernel.                                
[    0.372801] omap2_mbox_probe: platform not supported                         
[    0.527720] tps65217-bl tps65217-bl: no platform data provided               
[    0.591106] bone-capemgr bone_capemgr.9: slot #0: No cape found              
[    0.628213] bone-capemgr bone_capemgr.9: slot #1: No cape found              
[    0.665321] bone-capemgr bone_capemgr.9: slot #2: No cape found              
[    0.702431] bone-capemgr bone_capemgr.9: slot #3: No cape found              
[    0.718221] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P)
[    0.727781] bone-capemgr bone_capemgr.9: slot #6: Failed verification        
[    0.734516] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BO)
[    0.750892] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed   
[    0.814032] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested b8
[    0.825720] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22  
[    0.832993] pinctrl-single 44e10800.pinmux: could not request pin 21 on devie
Loading, please wait...                                                         
systemd-fsck[207]: rootfs: clean, 84709/233856 files, 485265/933632 blocks      
                                                                                
Debian GNU/Linux 7 beaglebone ttyO0                                             
                                                                                
BeagleBoard.org Debian Image 2015-03-01                                         
                                                                                
Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian               
                                                                                
default username:password is [debian:temppwd]                                   
                                                                                
The IP Address for usb0 is: 192.168.7.2                                         
beaglebone login: [   28.197242] libphy: PHY 4a101000.mdio:01 not found         
[   28.202308] net eth0: phy 4a101000.mdio:01 not found on slave 1              
[   34.002771] libphy: PHY 4a101000.mdio:01 not found                           
[   34.007883] net eth0: phy 4a101000.mdio:01 not found on slave 1              
[   34.787891] libphy: PHY 4a101000.mdio:01 not found                           
[   34.792990] net eth0: phy 4a101000.mdio:01 not found on slave 1              


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/GyKN6K8esa0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Robert Nelson

unread,
Apr 27, 2016, 3:18:20 PM4/27/16
to Beagle Board
On Wed, Apr 27, 2016 at 2:14 PM, Sriram Chadalavada <chsr...@gmail.com> wrote:
Here's more output. Thanks!

U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)


U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_B5

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0                                                
gpio: pin 53 (gpio 53) value is 1                                               
Card did not respond to voltage select!                                         
Card did not respond to voltage select!  

Here you, yeah it's not reading the microSD...

try a different card..

Regards,
Reply all
Reply to author
Forward
0 new messages