Re: State of LDP3430 platform

Paul Walmsley
2010-12-08T03:40:12Z

On Tue, 7 Dec 2010, Paul Walmsley wrote:

> I do have a LDP3430 here though. It doesn't boot past:
>
> [ 0.000000] Linux version 2.6.37-rc5 (paul@twilight) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #68 SMP Tue Dec 7 17:42:20
> [ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
> [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> [ 0.000000] Machine: OMAP Zoom2 board
> [ 0.000000] debug: ignoring loglevel setting.
> [ 0.000000] bootconsole [earlycon0] enabled
> [ 0.000000] Memory policy: ECC disabled, Data cache writeback
> [ 0.000000] OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp )
> [ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
>
> Looking into it now.

My Zoom2 dies in the memset() in omap2_map_sram(). Not sure why, since
yours seems to make it quite a bit further. It dies in the same place
with 2.6.36. The Zoom2 here may be broken; it does not receive regular
use.

Regarding the watchdog problem, unfortunately, I can't reproduce on the
BeagleBoard with v2.6.37-rc5 with either omap2plus_defconfig or
omap2plus_defconfig without CONFIG_WATCHDOG. If you send along your
.config, one of us can try to reproduce the problem with it. Do the
2.6.38 hwmod and wdt patchsets fix the problem for .38, at least?

- Paul