Hi Robert,

I have a similar issue - am I doing anything obviously wrong. Image is 
created with:

sudo ./setup_sdcard.sh --mmc /dev/sdf --dtb omap3-beagle --distro xenial

Serial output until board freeze:

40
U-Boot SPL 2016.03-00001-g54456ef (Mar 17 2016 - 16:31:02)
Trying to boot from MMC
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
bad magic
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2016.03-00001-g54456ef (Mar 17 2016 - 16:31:02 -0500), Build: 
jenkins-github_Bootloader-Builder-351

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

Beagle Rev C4
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
OMAP die ID: 1301901c040365fa000000005ac20004
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
reading /boot/uEnv.txt
184 bytes read in 5 ms (35.2 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-current ...
reading /boot/vmlinuz-current
5778160 bytes read in 429 ms (12.8 MiB/s)
loading /boot/dtbs/current/omap3-beagle.dtb ...
reading /boot/dtbs/current/omap3-beagle.dtb
107105 bytes read in 31 ms (3.3 MiB/s)
loading /boot/initrd.img-current ...
reading /boot/initrd.img-current
68120186 bytes read in 4971 ms (13.1 MiB/s)

Installer for [xenial-armhf] is using the Serial Interface

debug: [console=ttyO2,115200n8 root=/dev/ram rw musb_hdrc.fifo_mode=5] ...
debug: [bootz 0x82000000 0x88080000:40f6e7a 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x582af0 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Ramdisk to 8bf09000, end 8ffffe7a ...

Any clue would be precious - especially on how to debug from here...

Thanks,
David

On Monday, March 7, 2016 at 12:18:50 AM UTC+1, [email protected] wrote:
>
> Dear Robert, 
>
> Thanks a lot for your help!
> Unfortunately - no luck with both methods with same symptoms
>
> Netinstall.
>
> > git clone https://github.com/RobertCNelson/netinstall
> > cd netinstall
> > sudo ./mk_mmc.sh --mmc /dev/sdf --dtb omap3-beagle --distro xenial
>
> gives 
>
> ======================
> 40W
> U-Boot SPL 2016.01-00001-g3f205b0 (Mar 01 2016 - 14:23:49)
> Trying to boot from MMC
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2016.01-00001-g3f205b0 (Mar 01 2016 - 14:23:49 -0600), Build: 
> jenkins-github_Bootloader-Builder-337
>
> OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  256 MiB
> NAND:  256 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - bad CRC, using default environment
>
> Beagle Rev C4
> Timed out in wait_for_event: status=0000
> Check if pads/pull-ups of bus 1 are properly configured
> No EEPROM on expansion board
> Timed out in wait_for_event: status=0000
> Check if pads/pull-ups of bus 1 are properly configured
> No EEPROM on expansion board
> OMAP die ID: 1401d01c04037305000000002eaa0004Net:   usb_ether
> Error: usb_ether address not set.
>
> Hit any key to stop autoboot:  0 
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> Checking for: /uEnv.txt ...
> Checking for: /boot/uEnv.txt ...
> reading /boot/uEnv.txt
> 184 bytes read in 4 ms (44.9 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> Running uname_boot ...
> loading /boot/vmlinuz-current ...
> reading /boot/vmlinuz-current
> 5778816 bytes read in 426 ms (12.9 MiB/s)
> loading /boot/dtbs/current/omap3-beagle.dtb ...
> reading /boot/dtbs/current/omap3-beagle.dtb
> 107105 bytes read in 23 ms (4.4 MiB/s)
> loading /boot/initrd.img-current ...
> reading /boot/initrd.img-current
> 58777385 bytes read in 4280 ms (13.1 MiB/s)
>
> Installer for [xenial-armhf] is using the Serial Interface
>
> debug: [console=ttyO2,115200n8 root=/dev/ram rw musb_hdrc.fifo_mode=5] ...
> debug: [bootz 0x82000000 0x88080000:380df29 0x88000000] ...
> Kernel image @ 0x82000000 [ 0x000000 - 0x582d80 ]
> ## Flattened Device Tree blob at 88000000
>    Booting using the fdt blob at 0x88000000
>    Loading Ramdisk to 8c7f2000, end 8fffff29 ...
>
> ==============================================================================
>
> Precompiled image method
>
> > wget 
> https://rcn-ee.com/rootfs/2016-02-11/elinux/ubuntu-xenial-console-armhf-2016-02-11.tar.xz
> > tar xf ubuntu-xenial-console-armhf-2016-02-11.tar.xz
> > cd ubuntu-xenial-console-armhf-2016-02-11
> > sudo ./setup_sdcard.sh --mmc /dev/sdf --dtb omap3-beagle
>
>
> ==============================================================================
>
> 40W
> U-Boot SPL 2016.01-00001-g3f205b0 (Mar 01 2016 - 14:23:49)
> Trying to boot from MMC
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2016.01-00001-g3f205b0 (Mar 01 2016 - 14:23:49 -0600), Build: 
> jenkins-github_Bootloader-Builder-337
>
> OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  256 MiB
> NAND:  256 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - bad CRC, using default environment
>
> Beagle Rev C4
> Timed out in wait_for_event: status=0000
> Check if pads/pull-ups of bus 1 are properly configured
> No EEPROM on expansion board
> Timed out in wait_for_event: status=0000
> Check if pads/pull-ups of bus 1 are properly configured
> No EEPROM on expansion board
> OMAP die ID: 1401d01c04037305000000002eaa0004Net:   usb_ether
> Error: usb_ether address not set.
>
> Hit any key to stop autoboot:  0 
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> Checking for: /uEnv.txt ...
> Checking for: /boot/uEnv.txt ...
> 295 bytes read in 28 ms (9.8 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> Running uname_boot ...
> loading /boot/vmlinuz-4.4.1-armv7-x5 ...
> 5766104 bytes read in 458 ms (12 MiB/s)
> loading /boot/dtbs/4.4.1-armv7-x5/omap3-beagle.dtb ...
> 107105 bytes read in 91 ms (1.1 MiB/s)
> loading /boot/initrd.img-4.4.1-armv7-x5 ...
> 16301865 bytes read in 1236 ms (12.6 MiB/s)
> debug: [console=ttyO2,115200n8 
> root=UUID=d96b5f18-265e-49be-a8f0-d4be34d1d7f6 ro rootfstype=ext4 rootwait 
> musb_hdrc.fifo_mode=5 coherent_pool=1M quiet] ...
> debug: [bootz 0x82000000 0x88080000:f8bf29 0x88000000] ...
> Kernel image @ 0x82000000 [ 0x000000 - 0x57fbd8 ]
> ## Flattened Device Tree blob at 88000000
>    Booting using the fdt blob at 0x88000000
>    Loading Ramdisk to 8f074000, end 8fffff29 ...
>    
> ==============================================================================
>  
>
>
> On Sunday, March 6, 2016 at 11:35:21 PM UTC+3, RobertCNelson wrote:
>>
>> Or use the net install found here
>>
>> https://github.com/RobertCNelson/netinstall
>>
>> With the 4.1 LTS kernel option.
>>
>> See my last comment here..
>>
>>
>> https://github.com/RobertCNelson/armv7-multiplatform/issues/25#issuecomment-192494682
>> On Mar 6, 2016 2:30 PM, "Robert Nelson" <[email protected]> wrote:
>>
>>> It's the v4.4.x kernel with trusty..
>>>
>>> Use the xenial beta image.
>>>
>>> I'm dropping trusty..
>>>
>>> On Mar 6, 2016 2:24 PM, <[email protected]> wrote:
>>> >
>>> > Hello,
>>> >  I have issues trying to upgrade the Beagleboard C4 ubuntu.
>>> >  I followed the guide on http://elinux.org/BeagleBoardUbuntu , but 
>>> both Method 1 and Method failed.
>>> >
>>> >  It seems like it fails in uboot, just before the actual kernel start.
>>> >  Here is a full pastebin: http://pastebin.com/T6nnx1QP
>>> >
>>> >  And a small end of log:
>>> >
>>> >    Loaded environment from /boot/uEnv.txt
>>> > Checking if uname_r is set in /boot/uEnv.txt...
>>> > Running uname_boot ...
>>> > loading /boot/vmlinuz-4.4.1-armv7-x5 ...
>>> > 5699696 bytes read in 452 ms (12 MiB/s)
>>> > loading /boot/dtbs/4.4.1-armv7-x5/omap3-beagle.dtb ...
>>> > 107105 bytes read in 153 ms (683.6 KiB/s)
>>> > loading /boot/initrd.img-4.4.1-armv7-x5 ...
>>> > 12722954 bytes read in 969 ms (12.5 MiB/s)
>>> > debug: [console=ttyO2,115200n8 
>>> root=UUID=4817de6d-b3bb-4fb5-8157-492d5eedb08a ro rootfstype=ext4 rootwait 
>>> musb_hdrc.fifo_mode=5 coherent_pool=1M quiet] ...
>>> > debug: [bootz 0x82000000 0x88080000:c2230a 0x88000000] ...
>>> > Kernel image @ 0x82000000 [ 0x000000 - 0x56f870 ]
>>> > ## Flattened Device Tree blob at 88000000
>>> >    Booting using the fdt blob at 0x88000000
>>> >    Loading Ramdisk to 8f3dd000, end 8ffff30a ...
>>> >
>>> >
>>> >   After the Ramdisk line - device halts.
>>> >
>>> >  Additional info:
>>> >    1. MMC had passed badblocks test - so it should be fine. 
>>> >    2. I have two identical Beagleboards C4 - and both fail in the same 
>>> way. So it should not be hardware issue.
>>> >    3. Beagleboards are able to run old Ubuntu 9.10 - so again it seem 
>>> to prove they are fine.  
>>> >    4. I have tried "nand erase 260000 20000"
>>> >
>>> >  Questions - 
>>> >   1. Have anyone a a copy of ubuntu >14.04 that works with 
>>> Beagleboards Ax/Bx/Cx/Dx? Can you please share?
>>> >   2. Had anyone same issue as above? Google seem to be silent.
>>> >   3. Any other idea how to proceed? Can old NAND version of uboot 
>>> affect the MMC boot when MMC has a new version of u-boot?
>>> >
>>> > Best regards,
>>> > Alexander
>>> >
>>> > -- 
>>> > 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].
>>> > 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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to