Bug 58611
| Summary: | [pandaboard] device tree booting fails | ||
|---|---|---|---|
| Product: | Platform Specific/Hardware | Reporter: | Tobias Jakobi (liquid.acid) |
| Component: | ARM | Assignee: | linux-arm-kernel (linux-arm-kernel) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | high | CC: | nm, rogerq |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.9.3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
output from serial debug
serial debug with 3.10-rc2 serial debug with 3.10-rc3 + init-order patch |
||
|
Description
Tobias Jakobi
2013-05-21 19:40:28 UTC
For my current kernel config, see #58551 -- it's attached there. I have been booting pandaboard-ES with the following uEnv.txt
--- start of uEnv.txt
fdtbaddr=0x80F80000
loadaddr=0x80200000
fatloaduimage=fatload mmc 0:1 ${loadaddr} uImage
bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait earlyprintk
loaddtb=fatload mmc 0:1 ${fdtbaddr} omap4-panda-es.dtb; fdt addr ${fdtbaddr}; fdt resize
bootwdtb=bootm ${loadaddr} - ${fdtbaddr}
bootcmd=mw.w 0x4A31E05A 0x1f;printenv;echo "NOTE: booting from MMC filesystem";sleep 1;run fatloaduimage; sleep 1; run loaddtb; echo "starting.."; sleep 1; run bootwdtb
uenvcmd=boot
--- end of uEnv.txt --
This was done with 3.10-rc2 + omap2plus_defconfig, u-boot revision last tested on: latest u-boot tag.
mw.w 0x4A31E05A 0x1f is meant to hack GPIO pinmux configuration needed to keep MPU voltage alive - else the voltage drops when omap_hwmod resets GPIO1 block - see discussion here: http://marc.info/?t=135610446600003&r=1&w=2
*sigh* And I wanted to avoid using an rc-kernel. Guess I have no choice then! Reporting back once I test this -- wish me luck and that I don't blow up anything :) Created attachment 102291 [details]
serial debug with 3.10-rc2
Checked out latest version of linus' tree tried booting with it. Doesn't work, see the log. Looks like i2c is still acting up.
Well, at least I'm now getting exactly the same output as in the patchwork thread mentioned before: https://patchwork.kernel.org/patch/2444501/ Might be worth to try the proposed patch again. Created attachment 102701 [details]
serial debug with 3.10-rc3 + init-order patch
I did a retry with 3.10-rc3 plus the init order (from above) patch applied. The boot process gets a bit farther, but systemd then fails at bringing up ethernet and mounting the external usb drive.
Looking at the log itself, all the main problems however seem to remain.
With device tree boot, USB host and Ethernet will not work on Panda on v3.10 as some patches didn't make it into the merge window. Till 3.11 comes out you will have to manually apply the following patches. https://lkml.org/lkml/2013/4/19/124 https://lkml.org/lkml/2013/4/12/407 USB host and Ethernet should work fine on non device tree boot on v3.10. Also please make sure you have the following options enabled in kernel config to for USB host to work on OMAP. CONFIG_USB_EHCI_HCD_OMAP CONFIG_USB_PHY CONFIG_NOP_USB_XCEIV I tried applying the patches to 3.10-rc3, and while the first one works, the second one doesn't apply (multiple hunks fails). I guess I'll just wait until 3.11 then. DT booting now works with 3.12-rc5 |