NXP LPC3250 broken?

NXP LPC3250 broken?

[Roland Stigge]

Hi,

have you tried to compare with an NXP dev kit?

I also have an EA board but not currently connected. Will need to test
when I have access to it again.

Thanks for reporting,

Roland


On 04/12/2015 04:20 PM, Joachim Eastwood wrote:
> Hi,
> 
> I recently got a Embedded Artist LPC3250 (ea3250.dts) board that I
> wanted to test mainline Linux on.
> 
> But with lpc32xx_defconfig, ea3250.dts and the latest rc (v4.0-rc7) I am
> not getting very far.
> 
> First I got a "kernel NULL pointer dereference". See
> http://slexy.org/raw/s211rzbZL1
> I got around this one by disabling the leds-gpio driver.
> 
> Then, without leds-gpio, I get an endless stream of "unexpected IRQ trap
> at vector 00" messages.
> See: http://slexy.org/raw/s2S5Z9TtoV
> 
> I also tried an older kernel (3.18). This one seemed at first to hang
> but after a short while I got lots of backtraces which seem to involve
> rcu, tick and timer interrupt.
> See: http://slexy.org/raw/s2024RXCkX
> 
> Does anyone got any ideas on what may be going on?
> 
> 
> When I get a bit more time to play around with the kit I will try even
> older kernels to see if I can get it working at all.
> 
> best regards,
> Joachim Eastwood

NXP LPC3250 broken?

[Joachim Eastwood]

On 13 April 2015 at 10:01, Roland Stigge <stigge@antcom.de> wrote:
> Hi,
>
> have you tried to compare with an NXP dev kit?

No, the EA board is the only one I got.

> I also have an EA board but not currently connected. Will need to test
> when I have access to it again.

Okey, sounds good.

Which EA board do you have, btw?
The old one with the display or the v2?

regards,
Joachim Eastwood

> Thanks for reporting,
>
> Roland
>
>
> On 04/12/2015 04:20 PM, Joachim Eastwood wrote:
>> Hi,
>>
>> I recently got a Embedded Artist LPC3250 (ea3250.dts) board that I
>> wanted to test mainline Linux on.
>>
>> But with lpc32xx_defconfig, ea3250.dts and the latest rc (v4.0-rc7) I am
>> not getting very far.
>>
>> First I got a "kernel NULL pointer dereference". See
>> http://slexy.org/raw/s211rzbZL1
>> I got around this one by disabling the leds-gpio driver.
>>
>> Then, without leds-gpio, I get an endless stream of "unexpected IRQ trap
>> at vector 00" messages.
>> See: http://slexy.org/raw/s2S5Z9TtoV
>>
>> I also tried an older kernel (3.18). This one seemed at first to hang
>> but after a short while I got lots of backtraces which seem to involve
>> rcu, tick and timer interrupt.
>> See: http://slexy.org/raw/s2024RXCkX
>>
>> Does anyone got any ideas on what may be going on?
>>
>>
>> When I get a bit more time to play around with the kit I will try even
>> older kernels to see if I can get it working at all.
>>
>> best regards,
>> Joachim Eastwood
>

NXP LPC3250 broken?

[Roland Stigge]

On 04/13/2015 01:59 PM, Joachim Eastwood wrote:
>> I also have an EA board but not currently connected. Will need to test
>> when I have access to it again.
> 
> Okey, sounds good.
> 
> Which EA board do you have, btw?
> The old one with the display or the v2?

The one w/ the display. Would be interesting to support the v2 also, though!

NXP LPC3250 broken?

[Arnd Bergmann]

On Monday 13 April 2015 15:01:35 Roland Stigge wrote:
> On 04/13/2015 01:59 PM, Joachim Eastwood wrote:
> >> I also have an EA board but not currently connected. Will need to test
> >> when I have access to it again.
> > 
> > Okey, sounds good.
> > 
> > Which EA board do you have, btw?
> > The old one with the display or the v2?
> 
> The one w/ the display. Would be interesting to support the v2 also, though!

Sorry for highjacking the thread, but if one of you is still actively working
on lpc32xx stuff, would you be able to convert arch/arm/mach-lpc32xx/clock.c
to a proper driver for drivers/clk?

I'd like to see the platform get converted to use ARCH_MULTIPLATFORM
eventually, and this is the main showstopper.

	Arnd

NXP LPC3250 broken?

[Joachim Eastwood]

On 13 April 2015 at 15:01, Roland Stigge <stigge@antcom.de> wrote:
> On 04/13/2015 01:59 PM, Joachim Eastwood wrote:
>>> I also have an EA board but not currently connected. Will need to test
>>> when I have access to it again.
>>
>> Okey, sounds good.
>>
>> Which EA board do you have, btw?
>> The old one with the display or the v2?
>
> The one w/ the display. Would be interesting to support the v2 also, though!

I see. The one I have is the v2 one.

regards,
Joachim Eastwood

NXP LPC3250 broken?

[Joachim Eastwood]

On 13 April 2015 at 15:26, Arnd Bergmann <arnd@arndb.de> wrote:
> On Monday 13 April 2015 15:01:35 Roland Stigge wrote:
>> On 04/13/2015 01:59 PM, Joachim Eastwood wrote:
>> >> I also have an EA board but not currently connected. Will need to test
>> >> when I have access to it again.
>> >
>> > Okey, sounds good.
>> >
>> > Which EA board do you have, btw?
>> > The old one with the display or the v2?
>>
>> The one w/ the display. Would be interesting to support the v2 also, though!
>
> Sorry for highjacking the thread, but if one of you is still actively working
> on lpc32xx stuff, would you be able to convert arch/arm/mach-lpc32xx/clock.c
> to a proper driver for drivers/clk?

I am currently looking at it, but I won't promise anything.

regards,
Joachim Eastwood

> I'd like to see the platform get converted to use ARCH_MULTIPLATFORM
> eventually, and this is the main showstopper.
>
>         Arnd

NXP LPC3250 broken?

[Arnd Bergmann]

On Monday 13 April 2015 17:19:17 Joachim Eastwood wrote:
> On 13 April 2015 at 15:26, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Monday 13 April 2015 15:01:35 Roland Stigge wrote:
> >> On 04/13/2015 01:59 PM, Joachim Eastwood wrote:
> >> >> I also have an EA board but not currently connected. Will need to test
> >> >> when I have access to it again.
> >> >
> >> > Okey, sounds good.
> >> >
> >> > Which EA board do you have, btw?
> >> > The old one with the display or the v2?
> >>
> >> The one w/ the display. Would be interesting to support the v2 also, though!
> >
> > Sorry for highjacking the thread, but if one of you is still actively working
> > on lpc32xx stuff, would you be able to convert arch/arm/mach-lpc32xx/clock.c
> > to a proper driver for drivers/clk?
> 
> I am currently looking at it, but I won't promise anything.
> 

Ok, thanks!

	Arnd