Gingerbread-rowboat kernel stuck on "beagleboard rev C3"
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
What steps will reproduce the problem?
1. Compiled filesystem
2. Compiled Kernel
3. Copied uImage.bin to bootload from mmc
4. The Beagleboard stuck on loading the kernel
U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31)
I2C: ready
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 256 MB
NAND: 256 MiB
MUSB: using high speed
In: serial usbtty
Out: serial usbtty
Err: serial usbtty
Board revision C
Serial #6d220003000000000403230911012018
Hit any key to stop autoboot: 0
reading uImage.bin
2770344 bytes read
## Booting kernel from Legacy Image at 80000000 ...
Image Name: Linux-2.6.37-g3b51b95-dirty
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2770280 Bytes = 2.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
```
Original issue reported on code.google.com by `gsi...@nvtl.com` on 2 Nov 2011 at 9:08
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported filesystem and kernel build steps, then reproduce the U-Boot sequence on a BeagleBoard revision C3 using the copied uImage.bin. Compare the boot output through “Uncompressing Linux... done, booting the kernel.” Done means determining why this kernel does not continue booting and documenting a working boot or a confirmed cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100