Quantcast

Gumstix Overo AM3703 does not boot with kernel 3.18

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Gumstix Overo AM3703 does not boot with kernel 3.18

Zipper Fish
Dear gumstix-users,

Recently Gumstix upgraded the processors on some Overo boards to the AM3703 Sitara, previously it was the OMAP3503.

On the older Overo Earth COM, I have a customized Linux 3.18.18 setup. It starts up reliably and no issues

The exact same load will not boot on the newer AM3703 based Earthstorm COMs.

Even the stock Gumstix kernel 3.18.18 recipe will not boot on the AM3703 processor.
Also built a stock 3.18.43 kernel (by setting the SRCREV to 3cab355c2ff3a781b6ebe9d1a25bd4ebc1207430) and the same problem exists.

The kernel starts up and immediately produces a flood of errors on the serial console.

Here is the point where things go bad:

[    3.599029] In-band Error seen by MPU  at address 0
[    3.606536] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa050444
[    3.614624] Internal error: : 1028 [#1] SMP ARM
[    3.619415] Modules linked in:
[    3.622650] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G        W      3.18.43-test #1
[    3.631103] Workqueue: deferwq deferred_probe_work_func
[    3.636627] task: de0760c0 ti: de07c000 task.ti: de07c000
[    3.642333] PC is at dispc_runtime_resume+0xc/0x1b08
[    3.647583] LR is at __rpm_callback+0x2c/0x60
[    3.652191] pc : [<c036818c>]    lr : [<c03ceb40>]    psr: a0000113
[    3.652191] sp : de07dcf0  ip : 00000004  fp : c00775b8
[    3.664306] r10: 00000000  r9 : de07c028  r8 : 00000004
[    3.669799] r7 : c08b8100  r6 : c0029fd4  r5 : de25b4a4  r4 : c1149eb0
[    3.676696] r3 : c0368180  r2 : fa050400  r1 : de076680  r0 : de25b410
[    3.683593] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    3.691284] Control: 10c5387d  Table: 80004019  DAC: 00000015
[    3.697357] Process kworker/u2:0 (pid: 6, stack limit = 0xde07c240)
[    3.703979] Stack: (0xde07dcf0 to 0xde07e000)
[    3.708557] dce0:                                     de25b410 de25b4a4 c0029fd4 c08b8100
[    3.717193] dd00: 00000004 c03ceb40 de25b410 de25b4a4 de23fc10 c03ceb94 de25b410 de25b4a4
[    3.725830] dd20: de23fc10 c03cfebc c05dd9b8 de25b4c8 de25b4a4 60000113 c03d0158 c03706d8


This is with kernel 3.18.43 but the exact same thing happens with 3.18.18.
This is the Gumstix Overo default kernel config, with some of the heavy multi-MB driver modules disabled (mainly video and IP filter stuff), no other changes to system level or board level stuff.

The previous 3.13.6 kernel starts up fine.

The same 3.18.18 / 3.18.43 kernel starts on fine on the older OMAP3503 based Overo.

This may or may not matter, but I'm starting Linux using U-Boot Falcon mode, where the main U-Boot executable is bypassed and the SPL starts the kernel directly. I don't see why it would -- the same kernel works fine on other Overo boards with the identical U-Boot binaries.

Has anybody experienced this?
It can't be that the stock Gumstix kernels just don't work on the AM3703 based COMs.... or can it?

Attachments:
defconfig - My kernel config. Basically the stock config that comes with the Gumstix Yocto, except I disabled a few modules that make the rootfs huge (mainly video and IP filter / routing stuff).
bootlog.txt - Boot log from the first several seconds of the AM3703 board starting up. Something is completely not right as you can see.

Any help would be appreciated :-)

Thank you


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users

bootlog.txt (29K) Download Attachment
defconfig.txt (117K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Gumstix Overo AM3703 does not boot with kernel 3.18

arun
Hi there,

I think the kernel version might be the reason why you are seeing boot failures on AM3703. We have several patches on top of Linux 3.18.21 in our Gumstix linux tree which is needed to boot on AM3703.

I would recommend either of the following:
  1. Build just the linux kernel using the Gumstix linux branch yocto-v3.18.y from [1] using the config from [2] or
  2. Rebuild the entire yocto image using -dev instead of master. We are currently in the process of updating our -master branch to incorporate changes from -dev but the changes are not yet live. So just build yocto using -dev to get full support for AM3703.
Let me know if this helps.


- Arun

On Sat, Oct 15, 2016 at 9:04 AM, Zipper Fish [via Gumstix] <[hidden email]> wrote:
Dear gumstix-users,

Recently Gumstix upgraded the processors on some Overo boards to the AM3703 Sitara, previously it was the OMAP3503.

On the older Overo Earth COM, I have a customized Linux 3.18.18 setup. It starts up reliably and no issues

The exact same load will not boot on the newer AM3703 based Earthstorm COMs.

Even the stock Gumstix kernel 3.18.18 recipe will not boot on the AM3703 processor.
Also built a stock 3.18.43 kernel (by setting the SRCREV to 3cab355c2ff3a781b6ebe9d1a25bd4ebc1207430) and the same problem exists.

The kernel starts up and immediately produces a flood of errors on the serial console.

Here is the point where things go bad:

[    3.599029] In-band Error seen by MPU  at address 0
[    3.606536] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa050444
[    3.614624] Internal error: : 1028 [#1] SMP ARM
[    3.619415] Modules linked in:
[    3.622650] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G        W      3.18.43-test #1
[    3.631103] Workqueue: deferwq deferred_probe_work_func
[    3.636627] task: de0760c0 ti: de07c000 task.ti: de07c000
[    3.642333] PC is at dispc_runtime_resume+0xc/0x1b08
[    3.647583] LR is at __rpm_callback+0x2c/0x60
[    3.652191] pc : [<c036818c>]    lr : [<c03ceb40>]    psr: a0000113
[    3.652191] sp : de07dcf0  ip : 00000004  fp : c00775b8
[    3.664306] r10: 00000000  r9 : de07c028  r8 : 00000004
[    3.669799] r7 : c08b8100  r6 : c0029fd4  r5 : de25b4a4  r4 : c1149eb0
[    3.676696] r3 : c0368180  r2 : fa050400  r1 : de076680  r0 : de25b410
[    3.683593] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    3.691284] Control: 10c5387d  Table: 80004019  DAC: 00000015
[    3.697357] Process kworker/u2:0 (pid: 6, stack limit = 0xde07c240)
[    3.703979] Stack: (0xde07dcf0 to 0xde07e000)
[    3.708557] dce0:                                     de25b410 de25b4a4 c0029fd4 c08b8100
[    3.717193] dd00: 00000004 c03ceb40 de25b410 de25b4a4 de23fc10 c03ceb94 de25b410 de25b4a4
[    3.725830] dd20: de23fc10 c03cfebc c05dd9b8 de25b4c8 de25b4a4 60000113 c03d0158 c03706d8


This is with kernel 3.18.43 but the exact same thing happens with 3.18.18.
This is the Gumstix Overo default kernel config, with some of the heavy multi-MB driver modules disabled (mainly video and IP filter stuff), no other changes to system level or board level stuff.

The previous 3.13.6 kernel starts up fine.

The same 3.18.18 / 3.18.43 kernel starts on fine on the older OMAP3503 based Overo.

This may or may not matter, but I'm starting Linux using U-Boot Falcon mode, where the main U-Boot executable is bypassed and the SPL starts the kernel directly. I don't see why it would -- the same kernel works fine on other Overo boards with the identical U-Boot binaries.

Has anybody experienced this?
It can't be that the stock Gumstix kernels just don't work on the AM3703 based COMs.... or can it?

Attachments:
defconfig - My kernel config. Basically the stock config that comes with the Gumstix Yocto, except I disabled a few modules that make the rootfs huge (mainly video and IP filter / routing stuff).
bootlog.txt - Boot log from the first several seconds of the AM3703 board starting up. Something is completely not right as you can see.

Any help would be appreciated :-)

Thank you


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users

bootlog.txt (29K) Download Attachment
defconfig.txt (117K) Download Attachment



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.x6.nabble.com/Gumstix-Overo-AM3703-does-not-boot-with-kernel-3-18-tp4971121.html
To start a new topic under Gumstix, email [hidden email]
To unsubscribe from Gumstix, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Gumstix Overo AM3703 does not boot with kernel 3.18

Zipper Fish
Hi Arun,
Thanks for your response.
After several more hours of head scratching, I found the reason for the failure.

I hadn't realized that the Overo *STORM boards have their own device trees. It turns out that they do. Now that I changed to the appropriate device tree, everything starts up fine.

Back when this started happening, I knew it had to be something simple... and it was. Lesson learned. Sorry about the false alarm.

Thank you and have a great day!



On Mon, Oct 17, 2016 at 1:36 PM, arun <[hidden email]> wrote:
Hi there,

I think the kernel version might be the reason why you are seeing boot failures on AM3703. We have several patches on top of Linux 3.18.21 in our Gumstix linux tree which is needed to boot on AM3703.

I would recommend either of the following:
  1. Build just the linux kernel using the Gumstix linux branch yocto-v3.18.y from [1] using the config from [2] or
  2. Rebuild the entire yocto image using -dev instead of master. We are currently in the process of updating our -master branch to incorporate changes from -dev but the changes are not yet live. So just build yocto using -dev to get full support for AM3703.
Let me know if this helps.


- Arun

On Sat, Oct 15, 2016 at 9:04 AM, Zipper Fish [via Gumstix] <[hidden email]> wrote:
Dear gumstix-users,

Recently Gumstix upgraded the processors on some Overo boards to the AM3703 Sitara, previously it was the OMAP3503.

On the older Overo Earth COM, I have a customized Linux 3.18.18 setup. It starts up reliably and no issues

The exact same load will not boot on the newer AM3703 based Earthstorm COMs.

Even the stock Gumstix kernel 3.18.18 recipe will not boot on the AM3703 processor.
Also built a stock 3.18.43 kernel (by setting the SRCREV to 3cab355c2ff3a781b6ebe9d1a25bd4ebc1207430) and the same problem exists.

The kernel starts up and immediately produces a flood of errors on the serial console.

Here is the point where things go bad:

[    3.599029] In-band Error seen by MPU  at address 0
[    3.606536] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa050444
[    3.614624] Internal error: : 1028 [#1] SMP ARM
[    3.619415] Modules linked in:
[    3.622650] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G        W      3.18.43-test #1
[    3.631103] Workqueue: deferwq deferred_probe_work_func
[    3.636627] task: de0760c0 ti: de07c000 task.ti: de07c000
[    3.642333] PC is at dispc_runtime_resume+0xc/0x1b08
[    3.647583] LR is at __rpm_callback+0x2c/0x60
[    3.652191] pc : [<c036818c>]    lr : [<c03ceb40>]    psr: a0000113
[    3.652191] sp : de07dcf0  ip : 00000004  fp : c00775b8
[    3.664306] r10: 00000000  r9 : de07c028  r8 : 00000004
[    3.669799] r7 : c08b8100  r6 : c0029fd4  r5 : de25b4a4  r4 : c1149eb0
[    3.676696] r3 : c0368180  r2 : fa050400  r1 : de076680  r0 : de25b410
[    3.683593] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    3.691284] Control: 10c5387d  Table: 80004019  DAC: 00000015
[    3.697357] Process kworker/u2:0 (pid: 6, stack limit = 0xde07c240)
[    3.703979] Stack: (0xde07dcf0 to 0xde07e000)
[    3.708557] dce0:                                     de25b410 de25b4a4 c0029fd4 c08b8100
[    3.717193] dd00: 00000004 c03ceb40 de25b410 de25b4a4 de23fc10 c03ceb94 de25b410 de25b4a4
[    3.725830] dd20: de23fc10 c03cfebc c05dd9b8 de25b4c8 de25b4a4 60000113 c03d0158 c03706d8


This is with kernel 3.18.43 but the exact same thing happens with 3.18.18.
This is the Gumstix Overo default kernel config, with some of the heavy multi-MB driver modules disabled (mainly video and IP filter stuff), no other changes to system level or board level stuff.

The previous 3.13.6 kernel starts up fine.

The same 3.18.18 / 3.18.43 kernel starts on fine on the older OMAP3503 based Overo.

This may or may not matter, but I'm starting Linux using U-Boot Falcon mode, where the main U-Boot executable is bypassed and the SPL starts the kernel directly. I don't see why it would -- the same kernel works fine on other Overo boards with the identical U-Boot binaries.

Has anybody experienced this?
It can't be that the stock Gumstix kernels just don't work on the AM3703 based COMs.... or can it?

Attachments:
defconfig - My kernel config. Basically the stock config that comes with the Gumstix Yocto, except I disabled a few modules that make the rootfs huge (mainly video and IP filter / routing stuff).
bootlog.txt - Boot log from the first several seconds of the AM3703 board starting up. Something is completely not right as you can see.

Any help would be appreciated :-)

Thank you


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users

bootlog.txt (29K) Download Attachment
defconfig.txt (117K) Download Attachment



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.x6.nabble.com/Gumstix-Overo-AM3703-does-not-boot-with-kernel-3-18-tp4971121.html
To start a new topic under Gumstix, email [hidden email]
To unsubscribe from Gumstix, click here.
NAML



View this message in context: Re: Gumstix Overo AM3703 does not boot with kernel 3.18
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Gumstix Overo AM3703 does not boot with kernel 3.18

arun
Yeah, that should do it. 

u-boot has an env variable called boardname which is set to "overo-storm" for storm COMs which then results in the right device tree being used. But since you are skipping the u-boot altogether, I am guessing the right device tree is not being used for booting the kernel.

Glad that things are working now.

- Arun

On Mon, Oct 17, 2016 at 12:57 PM, Zipper Fish [via Gumstix] <[hidden email]> wrote:
Hi Arun,
Thanks for your response.
After several more hours of head scratching, I found the reason for the failure.

I hadn't realized that the Overo *STORM boards have their own device trees. It turns out that they do. Now that I changed to the appropriate device tree, everything starts up fine.

Back when this started happening, I knew it had to be something simple... and it was. Lesson learned. Sorry about the false alarm.

Thank you and have a great day!



On Mon, Oct 17, 2016 at 1:36 PM, arun <[hidden email]> wrote:
Hi there,

I think the kernel version might be the reason why you are seeing boot failures on AM3703. We have several patches on top of Linux 3.18.21 in our Gumstix linux tree which is needed to boot on AM3703.

I would recommend either of the following:
  1. Build just the linux kernel using the Gumstix linux branch yocto-v3.18.y from [1] using the config from [2] or
  2. Rebuild the entire yocto image using -dev instead of master. We are currently in the process of updating our -master branch to incorporate changes from -dev but the changes are not yet live. So just build yocto using -dev to get full support for AM3703.
Let me know if this helps.


- Arun

On Sat, Oct 15, 2016 at 9:04 AM, Zipper Fish [via Gumstix] <[hidden email]> wrote:
Dear gumstix-users,

Recently Gumstix upgraded the processors on some Overo boards to the AM3703 Sitara, previously it was the OMAP3503.

On the older Overo Earth COM, I have a customized Linux 3.18.18 setup. It starts up reliably and no issues

The exact same load will not boot on the newer AM3703 based Earthstorm COMs.

Even the stock Gumstix kernel 3.18.18 recipe will not boot on the AM3703 processor.
Also built a stock 3.18.43 kernel (by setting the SRCREV to 3cab355c2ff3a781b6ebe9d1a25bd4ebc1207430) and the same problem exists.

The kernel starts up and immediately produces a flood of errors on the serial console.

Here is the point where things go bad:

[    3.599029] In-band Error seen by MPU  at address 0
[    3.606536] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa050444
[    3.614624] Internal error: : 1028 [#1] SMP ARM
[    3.619415] Modules linked in:
[    3.622650] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G        W      3.18.43-test #1
[    3.631103] Workqueue: deferwq deferred_probe_work_func
[    3.636627] task: de0760c0 ti: de07c000 task.ti: de07c000
[    3.642333] PC is at dispc_runtime_resume+0xc/0x1b08
[    3.647583] LR is at __rpm_callback+0x2c/0x60
[    3.652191] pc : [<c036818c>]    lr : [<c03ceb40>]    psr: a0000113
[    3.652191] sp : de07dcf0  ip : 00000004  fp : c00775b8
[    3.664306] r10: 00000000  r9 : de07c028  r8 : 00000004
[    3.669799] r7 : c08b8100  r6 : c0029fd4  r5 : de25b4a4  r4 : c1149eb0
[    3.676696] r3 : c0368180  r2 : fa050400  r1 : de076680  r0 : de25b410
[    3.683593] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    3.691284] Control: 10c5387d  Table: 80004019  DAC: 00000015
[    3.697357] Process kworker/u2:0 (pid: 6, stack limit = 0xde07c240)
[    3.703979] Stack: (0xde07dcf0 to 0xde07e000)
[    3.708557] dce0:                                     de25b410 de25b4a4 c0029fd4 c08b8100
[    3.717193] dd00: 00000004 c03ceb40 de25b410 de25b4a4 de23fc10 c03ceb94 de25b410 de25b4a4
[    3.725830] dd20: de23fc10 c03cfebc c05dd9b8 de25b4c8 de25b4a4 60000113 c03d0158 c03706d8


This is with kernel 3.18.43 but the exact same thing happens with 3.18.18.
This is the Gumstix Overo default kernel config, with some of the heavy multi-MB driver modules disabled (mainly video and IP filter stuff), no other changes to system level or board level stuff.

The previous 3.13.6 kernel starts up fine.

The same 3.18.18 / 3.18.43 kernel starts on fine on the older OMAP3503 based Overo.

This may or may not matter, but I'm starting Linux using U-Boot Falcon mode, where the main U-Boot executable is bypassed and the SPL starts the kernel directly. I don't see why it would -- the same kernel works fine on other Overo boards with the identical U-Boot binaries.

Has anybody experienced this?
It can't be that the stock Gumstix kernels just don't work on the AM3703 based COMs.... or can it?

Attachments:
defconfig - My kernel config. Basically the stock config that comes with the Gumstix Yocto, except I disabled a few modules that make the rootfs huge (mainly video and IP filter / routing stuff).
bootlog.txt - Boot log from the first several seconds of the AM3703 board starting up. Something is completely not right as you can see.

Any help would be appreciated :-)

Thank you


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users

bootlog.txt (29K) Download Attachment
defconfig.txt (117K) Download Attachment



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.x6.nabble.com/Gumstix-Overo-AM3703-does-not-boot-with-kernel-3-18-tp4971121.html
To start a new topic under Gumstix, email [hidden email]
To unsubscribe from Gumstix, click here.
NAML



View this message in context: Re: Gumstix Overo AM3703 does not boot with kernel 3.18
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.x6.nabble.com/Gumstix-Overo-AM3703-does-not-boot-with-kernel-3-18-tp4971121p4971124.html
To start a new topic under Gumstix, email [hidden email]
To unsubscribe from Gumstix, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Gumstix Overo AM3703 does not boot with kernel 3.18

Zipper Fish
Exactly. 
Now my U-Boot NAND install script uses the boardname environment variable to decide with device tree to write into NAND memory.
Once I knew what the problem was, this was a relatively painless fix. :-)


On Mon, Oct 17, 2016 at 4:01 PM, arun <[hidden email]> wrote:
Yeah, that should do it. 

u-boot has an env variable called boardname which is set to "overo-storm" for storm COMs which then results in the right device tree being used. But since you are skipping the u-boot altogether, I am guessing the right device tree is not being used for booting the kernel.

Glad that things are working now.

- Arun

On Mon, Oct 17, 2016 at 12:57 PM, Zipper Fish [via Gumstix] <[hidden email]> wrote:
Hi Arun,
Thanks for your response.
After several more hours of head scratching, I found the reason for the failure.

I hadn't realized that the Overo *STORM boards have their own device trees. It turns out that they do. Now that I changed to the appropriate device tree, everything starts up fine.

Back when this started happening, I knew it had to be something simple... and it was. Lesson learned. Sorry about the false alarm.

Thank you and have a great day!



On Mon, Oct 17, 2016 at 1:36 PM, arun <[hidden email]> wrote:
Hi there,

I think the kernel version might be the reason why you are seeing boot failures on AM3703. We have several patches on top of Linux 3.18.21 in our Gumstix linux tree which is needed to boot on AM3703.

I would recommend either of the following:
  1. Build just the linux kernel using the Gumstix linux branch yocto-v3.18.y from [1] using the config from [2] or
  2. Rebuild the entire yocto image using -dev instead of master. We are currently in the process of updating our -master branch to incorporate changes from -dev but the changes are not yet live. So just build yocto using -dev to get full support for AM3703.
Let me know if this helps.


- Arun

On Sat, Oct 15, 2016 at 9:04 AM, Zipper Fish [via Gumstix] <[hidden email]> wrote:
Dear gumstix-users,

Recently Gumstix upgraded the processors on some Overo boards to the AM3703 Sitara, previously it was the OMAP3503.

On the older Overo Earth COM, I have a customized Linux 3.18.18 setup. It starts up reliably and no issues

The exact same load will not boot on the newer AM3703 based Earthstorm COMs.

Even the stock Gumstix kernel 3.18.18 recipe will not boot on the AM3703 processor.
Also built a stock 3.18.43 kernel (by setting the SRCREV to 3cab355c2ff3a781b6ebe9d1a25bd4ebc1207430) and the same problem exists.

The kernel starts up and immediately produces a flood of errors on the serial console.

Here is the point where things go bad:

[    3.599029] In-band Error seen by MPU  at address 0
[    3.606536] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa050444
[    3.614624] Internal error: : 1028 [#1] SMP ARM
[    3.619415] Modules linked in:
[    3.622650] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G        W      3.18.43-test #1
[    3.631103] Workqueue: deferwq deferred_probe_work_func
[    3.636627] task: de0760c0 ti: de07c000 task.ti: de07c000
[    3.642333] PC is at dispc_runtime_resume+0xc/0x1b08
[    3.647583] LR is at __rpm_callback+0x2c/0x60
[    3.652191] pc : [<c036818c>]    lr : [<c03ceb40>]    psr: a0000113
[    3.652191] sp : de07dcf0  ip : 00000004  fp : c00775b8
[    3.664306] r10: 00000000  r9 : de07c028  r8 : 00000004
[    3.669799] r7 : c08b8100  r6 : c0029fd4  r5 : de25b4a4  r4 : c1149eb0
[    3.676696] r3 : c0368180  r2 : fa050400  r1 : de076680  r0 : de25b410
[    3.683593] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    3.691284] Control: 10c5387d  Table: 80004019  DAC: 00000015
[    3.697357] Process kworker/u2:0 (pid: 6, stack limit = 0xde07c240)
[    3.703979] Stack: (0xde07dcf0 to 0xde07e000)
[    3.708557] dce0:                                     de25b410 de25b4a4 c0029fd4 c08b8100
[    3.717193] dd00: 00000004 c03ceb40 de25b410 de25b4a4 de23fc10 c03ceb94 de25b410 de25b4a4
[    3.725830] dd20: de23fc10 c03cfebc c05dd9b8 de25b4c8 de25b4a4 60000113 c03d0158 c03706d8


This is with kernel 3.18.43 but the exact same thing happens with 3.18.18.
This is the Gumstix Overo default kernel config, with some of the heavy multi-MB driver modules disabled (mainly video and IP filter stuff), no other changes to system level or board level stuff.

The previous 3.13.6 kernel starts up fine.

The same 3.18.18 / 3.18.43 kernel starts on fine on the older OMAP3503 based Overo.

This may or may not matter, but I'm starting Linux using U-Boot Falcon mode, where the main U-Boot executable is bypassed and the SPL starts the kernel directly. I don't see why it would -- the same kernel works fine on other Overo boards with the identical U-Boot binaries.

Has anybody experienced this?
It can't be that the stock Gumstix kernels just don't work on the AM3703 based COMs.... or can it?

Attachments:
defconfig - My kernel config. Basically the stock config that comes with the Gumstix Yocto, except I disabled a few modules that make the rootfs huge (mainly video and IP filter / routing stuff).
bootlog.txt - Boot log from the first several seconds of the AM3703 board starting up. Something is completely not right as you can see.

Any help would be appreciated :-)

Thank you


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users

bootlog.txt (29K) Download Attachment
defconfig.txt (117K) Download Attachment



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.x6.nabble.com/Gumstix-Overo-AM3703-does-not-boot-with-kernel-3-18-tp4971121.html
To start a new topic under Gumstix, email [hidden email]
To unsubscribe from Gumstix, click here.
NAML



View this message in context: Re: Gumstix Overo AM3703 does not boot with kernel 3.18
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



If you reply to this email, your message will be added to the discussion below:
http://gumstix.8.x6.nabble.com/Gumstix-Overo-AM3703-does-not-boot-with-kernel-3-18-tp4971121p4971124.html
To start a new topic under Gumstix, email [hidden email]
To unsubscribe from Gumstix, click here.
NAML



View this message in context: Re: Gumstix Overo AM3703 does not boot with kernel 3.18
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Loading...