I am trying to boot linux on Beagle Board Rev. C3 with no success. Steps I took for booting is taken from this wiki https://eewiki.net/display/linuxonarm/BeagleBoard . It is created by Robert Nelson. I can see that U-Boot is started and trying to start Linux kernel, but as control is passed to kernel I stop getting output. It looked like low-level debug is not configured for OMAP3. I tried to recompile and configure kernel. In menuconfig I select Kernel hacking —> Kernel low-level debugging functions —> Kernel low-level debugging port and I select “Kernel low-level debugging messages via OMAP3 UART3”. I also select Early printk(I am not sure if I need this). After compiling I have no progress. I also connect monitor via hdmi and I see yellow screen only.
Could you please give me some idea?
This is my output:
U-Boot 2016.09-dirty (Nov 02 2016 - 12:23:39 +0100)
OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 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 C1/C2/C3
Timed out in wait_for_event: status=1000
Check if pads/pull-ups of bus are properly configured
No EEPROM on expansion board
Timed out in wait_for_bb: status=1000
No EEPROM on expansion board
OMAP die ID: 3d00000300000000040323090b01e00a
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 …
23 bytes read in 11 ms (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-4.7.8-armv7-x3 …
6089504 bytes read in 543 ms (10.7 MiB/s)
loading /boot/dtbs/4.7.8-armv7-x3/omap3-beagle.dtb …
109840 bytes read in 277 ms (386.7 KiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait musb_hdrc.fifo_mode=5] …
debug: [bootz 0x82000000 - 0x88000000] …
Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffe2000, end 8ffffd0f … OK
Starting kernel …