Paul, On 09/25/2013 10:02 AM, Santosh Shilimkar wrote: > On Tuesday 24 September 2013 07:59 PM, Paul Zimmerman wrote: >>> From: Suman Anna [mailto:s-anna@xxxxxx] >>> Sent: Tuesday, September 24, 2013 4:48 PM >>> >>> On 09/24/2013 05:24 PM, Santosh Shilimkar wrote: >>>> On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote: >>>>>> From: Paul Zimmerman >>>>>> Sent: Tuesday, September 24, 2013 1:21 PM >>>>>> >>>>>> Hi, >>>>>> >>>>>> I have an OMAP5432 uEVM which I cannot get to boot with recent mainline >>>>>> (tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board (v6.0.0.7), >>>>>> which comes with 3.8.4 which works fine. >>>>>> >>>>>> I found this thread: http://marc.info/?l=fedora-arm&m=137717811815777 and >>>>> >>>>> Wrong link, should have been http://marc.info/?l=linux-omap&m=137515583214350. >>>>> >>>> Its because of commit 03ab349ec{ARM: OMAP5: hwmod data: Add mailbox data} which >>>> added hwmod data but DT data for mailbox is missing. Reverting that makes >>>> things work. Looks like mailbox dt patches missed the last merge window. >>> >>> Yeah, the boot sequence tries to enable and idle all the hwmods, and >>> this results in an error while initializing the mailbox hwmod during the >>> sysc configuration. This is because the OMAP5 hwmod data file no longer >>> has the omap_hwmod_addr_space defined in the hwmod_ocp_if data. Two ways >>> for now to get past is either revert the mailbox hwmod commit as above >>> or add the DT node [2]. >>> >>> I will be respinning the mailbox DT series very soon targeting 3.13, so >>> should not be an issue when OMAP5 boot is supported directly on mainline. >> >> That's good info, but unfortunately it didn't work for me. I must have a >> different problem, maybe I need a newer version of u-boot. >> >> So there is no README or wiki that explains how to get Linux to boot on >> this board? Is there perhaps a prebuilt SD card image somewhere with a >> recent kernel that I can grab? >> > You don't need anything special as such. Just pull the latest mainline > denx u-boot build it for 'omap5_uevm' and update your boot-loaders. FYI, I was able to boot using the branch posted by Santosh just fine. I used v2013.07 u-boot. The boot traces show up about 30~45 seconds after you see the trace "Starting kernel...". For using a rootfs from MMC, enable the following in menuconfig: Device Drivers -> Multifunction device drivers -> TI Palmas series chips Device Drivers -> Voltage and Current Regulator Support -> TI Palmas PMIC regulators. Depending on your u-boot settings, make sure the mmcroot is also set to /dev/mmcblk1p2. regards Suman -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
