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.

Reply via email to