RE: Booting recent mainline on omap5-uevm
From: Suman Anna [mailto:s-a...@ti.com]
Sent: Wednesday, September 25, 2013 11:37 AM
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-a...@ti.com]
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-armm=137717811815777
and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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.
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.
Hi Suman,
Thanks for trying to help. Unfortunately, updating to v2013.07 u-boot, and
enabling the kernel config items you mentioned, didn't make a difference.
Could you share your boot.scr? I'm still using the one from the TI GLSDK,
but maybe something has changed since the 3.8 kernel? Also, how do you
build your kernel? I'm doing make LOADADDR=0x80008000 uImage because
newer kernels won't build without the LOADADDR= bit.
I guess you TI guys know how all this works, but for an outsider like me
it's not so clear ;)
--
Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
Hi Paul,
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-armm=137717811815777
and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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.
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.
Hi Suman,
Thanks for trying to help. Unfortunately, updating to v2013.07 u-boot, and
enabling the kernel config items you mentioned, didn't make a difference.
Could you share your boot.scr? I'm still using the one from the TI GLSDK,
but maybe something has changed since the 3.8 kernel? Also, how do you
build your kernel? I'm doing make LOADADDR=0x80008000 uImage because
newer kernels won't build without the LOADADDR= bit.
I build the kernel same way as you, and copy the zImage to boot
partition. I am not using any boot.scr, a simple uEnv.txt to override
the boot partition variables, and the default environment otherwise.
My boot log is here, including my uEnv.txt at the end.
http://hastebin.com/yinuxirexu.xml
Hopefully, this should clear out any setup differences..
regards
Suman
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
On Tuesday 24 September 2013 07:59 PM, Paul Zimmerman wrote:
From: Suman Anna [mailto:s-a...@ti.com]
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-armm=137717811815777 and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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.
Regards,
Santosh
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
Santosh,
On 09/24/2013 06:55 PM, Santosh Shilimkar wrote:
On Tuesday 24 September 2013 07:48 PM, Suman Anna wrote:
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-armm=137717811815777 and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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].
Would be good if you can get the mailbox dt node in rc cycles. But since
CCF is still missing if if that doesn't happen in rc's thats ok.
Would mostly be 3.13, we do not want to add just the OMAP5 DT node patch
separately in a 3.12 rc, since there are other patches that add the DT
binding documentation and driver support. Will definitely need to be
queued up alongside the CCF patches when OMAP5 boot is being enabled.
regards
Suman
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
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-a...@ti.com]
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-armm=137717811815777 and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Booting recent mainline on omap5-uevm
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-armm=137717811815777 and Wrong link, should have been http://marc.info/?l=linux-omapm=137515583214350. tried using git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git and merging in for_3.11/out_of_tree/omap5_clk_data from ssantosh's tree as described, but with no luck. In all cases the boot hangs after the Starting kernel ... message. I enabled the low-level debugging options in the kernel but got no further messages. I'm using u-boot_2013.01.1.1 from the GLSDK, is that OK or do I need a more recent version? Is there a FAQ or wiki or something that describes what I need to do? Thanks, -- Paul -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
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-armm=137717811815777 and
Wrong link, should have been http://marc.info/?l=linux-omapm=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.
The booting branch is pushed here [1] just in case you need it.
regards,
Santosh
[1]
https://git.kernel.org/cgit/linux/kernel/git/ssantosh/linux.git/log/?h=3.12/omap5
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
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-armm=137717811815777 and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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.
regards
Suman
The booting branch is pushed here [1] just in case you need it.
regards,
Santosh
[1]
https://git.kernel.org/cgit/linux/kernel/git/ssantosh/linux.git/log/?h=3.12/omap5
[2] http://marc.info/?l=linux-omapm=137582564017990w=2
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Booting recent mainline on omap5-uevm
On Tuesday 24 September 2013 07:48 PM, Suman Anna wrote:
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-armm=137717811815777 and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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].
Would be good if you can get the mailbox dt node in rc cycles. But since
CCF is still missing if if that doesn't happen in rc's thats ok.
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.
Thanks
Regards,
Santosh
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: Booting recent mainline on omap5-uevm
From: Suman Anna [mailto:s-a...@ti.com]
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-armm=137717811815777 and
Wrong link, should have been
http://marc.info/?l=linux-omapm=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?
--
Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
