Forums

Weird LPC2366 JTAG happenings...

Started by bobtransformer November 4, 2009
I am working on transitioning to the LPC2366 (have one successful transition already) and have a very strange happening here...
So far, my software works fine if I run from the J-Link JTAG and just
let it go, but does not work if I try to just let the LPC2366 hardware run all by itself. IAR EWARM 5.4 and J-Link JTAG.

If a start the hardware running without the JTAG, and then "attach" to it, I find it in a loop of 1 to 3 lines shown below (included some lines around this point too) at 0x7fffe152 0x7fffe154 and 0x7fffe156.

Sometimes 0x7fffe156 is not always the same stuff, but
the real weird thing is that there is NO MEMORY MAPPED to this area !

Any ideas here ? It is weird that it would be stuck somewhere where there is no memory mapped. The weird code appears to show up starting at 0x7fffe054 and does not seem to be just repeating, so far as I can tell. Maybe it's double decoded and appears at lower memory maybe ? What is at this spot in an LPC2366 ??

I cannot see what is happening before this loop with the JTAG because it has to start from power up or hardware reset. Any ideas
on that would be nice too so I can see what is going on here.
If I just set the JTAG to run from 0x000000000, it works fine.

Thanks,
boB

0x7fffe134: 0xff69f000 DC32 -9834496 ; '.'
0x7fffe138: 0xf000e7b0 DC32 -268376144 ; '
0x7fffe13c: 0xe7adfce8 DC32 -408027928 ; '
0x7fffe140: 0x4ea3b5f8 DC32 1319351800 ; ''
0x7fffe144: 0x4ca64da5 DC32 1285967269 ; 'ML'
0x7fffe148: 0x4aa62700 DC32 1252402944 ; '.'J'
0x7fffe14c: 0x60502002 DC32 1615863810 ; '. P`'
0x7fffe150: 0x694849a5 DC32 1766345125 ; 'IHi'
0x7fffe152: 0x6948 DC16 26952 ; 'Hi'
0x7fffe154: 0xd4fc0700 DC32 -721680640 ; '..'
0x7fffe156: 0xd4fc DC16 54524 ; ''
0x7fffe158: 0x07006948 DC32 117467464 ; 'Hi..'
0x7fffe15c: 0x2001d5fc DC32 536991228 ; '. '
0x7fffe160: 0x69486050 DC32 1766350928 ; 'P`Hi'
0x7fffe164: 0xd4fc0700 DC32 -721680640 ; '..'
0x7fffe168: 0x07006948 DC32 117467464 ; 'Hi..'
0x7fffe16c: 0x6057d5fc DC32 1616369148 ; 'W`'
0x7fffe170: 0x21806890 DC32 562063504 ; '.h.!'
0x7fffe174: 0xfef6f000 DC32 -17371136 ; '.'

An Engineer's Guide to the LPC2100 Series

I had the same problem. P0.14 was low at power-up. LPC2292 was mine.

bobtransformer wrote:
>
> I am working on transitioning to the LPC2366 (have one successful
> transition already) and have a very strange happening here...
> So far, my software works fine if I run from the J-Link JTAG and just
> let it go, but does not work if I try to just let the LPC2366 hardware
> run all by itself. IAR EWARM 5.4 and J-Link JTAG.
>
> If a start the hardware running without the JTAG, and then "attach" to
> it, I find it in a loop of 1 to 3 lines shown below (included some
> lines around this point too) at 0x7fffe152 0x7fffe154 and 0x7fffe156.
>
> Sometimes 0x7fffe156 is not always the same stuff, but
> the real weird thing is that there is NO MEMORY MAPPED to this area !
>
> Any ideas here ? It is weird that it would be stuck somewhere where
> there is no memory mapped. The weird code appears to show up starting
> at 0x7fffe054 and does not seem to be just repeating, so far as I can
> tell. Maybe it's double decoded and appears at lower memory maybe ?
> What is at this spot in an LPC2366 ??
>
> I cannot see what is happening before this loop with the JTAG because
> it has to start from power up or hardware reset. Any ideas
> on that would be nice too so I can see what is going on here.
> If I just set the JTAG to run from 0x000000000, it works fine.
>
> Thanks,
> boB
>
> 0x7fffe134: 0xff69f000 DC32 -9834496 ; '.'
> 0x7fffe138: 0xf000e7b0 DC32 -268376144 ; '
> 0x7fffe13c: 0xe7adfce8 DC32 -408027928 ; '
> 0x7fffe140: 0x4ea3b5f8 DC32 1319351800 ; ''
> 0x7fffe144: 0x4ca64da5 DC32 1285967269 ; 'ML'
> 0x7fffe148: 0x4aa62700 DC32 1252402944 ; '.'J'
> 0x7fffe14c: 0x60502002 DC32 1615863810 ; '. P`'
> 0x7fffe150: 0x694849a5 DC32 1766345125 ; 'IHi'
> 0x7fffe152: 0x6948 DC16 26952 ; 'Hi'
> 0x7fffe154: 0xd4fc0700 DC32 -721680640 ; '..'
> 0x7fffe156: 0xd4fc DC16 54524 ; ''
> 0x7fffe158: 0x07006948 DC32 117467464 ; 'Hi..'
> 0x7fffe15c: 0x2001d5fc DC32 536991228 ; '. '
> 0x7fffe160: 0x69486050 DC32 1766350928 ; 'P`Hi'
> 0x7fffe164: 0xd4fc0700 DC32 -721680640 ; '..'
> 0x7fffe168: 0x07006948 DC32 117467464 ; 'Hi..'
> 0x7fffe16c: 0x6057d5fc DC32 1616369148 ; 'W`'
> 0x7fffe170: 0x21806890 DC32 562063504 ; '.h.!'
> 0x7fffe174: 0xfef6f000 DC32 -17371136 ; '.'
>
>


bobt
> Any ideas here ? It is weird that it would be stuck somewhere where
> there is no memory mapped. The weird code appears to show up
> starting at 0x7fffe054 and does not seem to be just repeating, so far
> as I can tell. Maybe it's double decoded and appears at lower memory
> maybe ? What is at this spot in an LPC2366 ??

The NXP bootloader ?!

--
42Bastian
------------------
Parts of this email are written with invisible ink.

Note: SPAM-only account, direct mail to bs42@...
--- In l..., Dave Such wrote:
>
> I had the same problem. P0.14 was low at power-up. LPC2292 was mine.

Thank you Dave and 42Bastion !

Yep. That was it. I had the jumper in place. I knew the bootloader was "up there", but I didn't remember it being in the RAM area specified in the spec sheet (of course none of the parts actually have RAM up in that range.

What can is say but "DUHhhh" !

boB

>
> bobtransformer wrote:
> >
> >
> >
> > I am working on transitioning to the LPC2366 (have one successful
> > transition already) and have a very strange happening here...
> > So far, my software works fine if I run from the J-Link JTAG and just
> > let it go, but does not work if I try to just let the LPC2366 hardware
> > run all by itself. IAR EWARM 5.4 and J-Link JTAG.
> >
> > If a start the hardware running without the JTAG, and then "attach" to
> > it, I find it in a loop of 1 to 3 lines shown below (included some
> > lines around this point too) at 0x7fffe152 0x7fffe154 and 0x7fffe156.
> >
> > Sometimes 0x7fffe156 is not always the same stuff, but
> > the real weird thing is that there is NO MEMORY MAPPED to this area !
> >
> > Any ideas here ? It is weird that it would be stuck somewhere where
> > there is no memory mapped. The weird code appears to show up starting
> > at 0x7fffe054 and does not seem to be just repeating, so far as I can
> > tell. Maybe it's double decoded and appears at lower memory maybe ?
> > What is at this spot in an LPC2366 ??
> >
> > I cannot see what is happening before this loop with the JTAG because
> > it has to start from power up or hardware reset. Any ideas
> > on that would be nice too so I can see what is going on here.
> > If I just set the JTAG to run from 0x000000000, it works fine.
> >
> > Thanks,
> > boB
> >
> > 0x7fffe134: 0xff69f000 DC32 -9834496 ; '.'
> > 0x7fffe138: 0xf000e7b0 DC32 -268376144 ; '
> > 0x7fffe13c: 0xe7adfce8 DC32 -408027928 ; '
> > 0x7fffe140: 0x4ea3b5f8 DC32 1319351800 ; ''
> > 0x7fffe144: 0x4ca64da5 DC32 1285967269 ; 'ML'
> > 0x7fffe148: 0x4aa62700 DC32 1252402944 ; '.'J'
> > 0x7fffe14c: 0x60502002 DC32 1615863810 ; '. P`'
> > 0x7fffe150: 0x694849a5 DC32 1766345125 ; 'IHi'
> > 0x7fffe152: 0x6948 DC16 26952 ; 'Hi'
> > 0x7fffe154: 0xd4fc0700 DC32 -721680640 ; '..'
> > 0x7fffe156: 0xd4fc DC16 54524 ; ''
> > 0x7fffe158: 0x07006948 DC32 117467464 ; 'Hi..'
> > 0x7fffe15c: 0x2001d5fc DC32 536991228 ; '. '
> > 0x7fffe160: 0x69486050 DC32 1766350928 ; 'P`Hi'
> > 0x7fffe164: 0xd4fc0700 DC32 -721680640 ; '..'
> > 0x7fffe168: 0x07006948 DC32 117467464 ; 'Hi..'
> > 0x7fffe16c: 0x6057d5fc DC32 1616369148 ; 'W`'
> > 0x7fffe170: 0x21806890 DC32 562063504 ; '.h.!'
> > 0x7fffe174: 0xfef6f000 DC32 -17371136 ; '.'
> >
> >
>
>
>
>

My question is...

Why did NXP (Philips) chose a pin that is commonly used?

There are several pins (144 pin package) that are not used.

In my field of work, EINT (s) are valuable. This one sticks in my crawl.

My opinion.

Dave
> --- In l..., Dave Such wrote:
>>
>> I had the same problem. P0.14 was low at power-up. LPC2292 was mine.
>
> Thank you Dave and 42Bastion !
>
> Yep. That was it. I had the jumper in place. I knew the bootloader was
> "up there", but I didn't remember it being in the RAM area specified in
> the spec sheet (of course none of the parts actually have RAM up in that
> range.
>
> What can is say but "DUHhhh" !
>
> boB
>
>>
>> bobtransformer wrote:
>> >
>> >
>> >
>> > I am working on transitioning to the LPC2366 (have one successful
>> > transition already) and have a very strange happening here...
>> > So far, my software works fine if I run from the J-Link JTAG and just
>> > let it go, but does not work if I try to just let the LPC2366 hardware
>> > run all by itself. IAR EWARM 5.4 and J-Link JTAG.
>> >
>> > If a start the hardware running without the JTAG, and then "attach" to
>> > it, I find it in a loop of 1 to 3 lines shown below (included some
>> > lines around this point too) at 0x7fffe152 0x7fffe154 and 0x7fffe156.
>> >
>> > Sometimes 0x7fffe156 is not always the same stuff, but
>> > the real weird thing is that there is NO MEMORY MAPPED to this area !
>> >
>> > Any ideas here ? It is weird that it would be stuck somewhere where
>> > there is no memory mapped. The weird code appears to show up starting
>> > at 0x7fffe054 and does not seem to be just repeating, so far as I can
>> > tell. Maybe it's double decoded and appears at lower memory maybe ?
>> > What is at this spot in an LPC2366 ??
>> >
>> > I cannot see what is happening before this loop with the JTAG because
>> > it has to start from power up or hardware reset. Any ideas
>> > on that would be nice too so I can see what is going on here.
>> > If I just set the JTAG to run from 0x000000000, it works fine.
>> >
>> > Thanks,
>> > boB
>> >
>> > 0x7fffe134: 0xff69f000 DC32 -9834496 ; '.'
>> > 0x7fffe138: 0xf000e7b0 DC32 -268376144 ; '
>> > 0x7fffe13c: 0xe7adfce8 DC32 -408027928 ; '
>> > 0x7fffe140: 0x4ea3b5f8 DC32 1319351800 ; ''
>> > 0x7fffe144: 0x4ca64da5 DC32 1285967269 ; 'ML'
>> > 0x7fffe148: 0x4aa62700 DC32 1252402944 ; '.'J'
>> > 0x7fffe14c: 0x60502002 DC32 1615863810 ; '. P`'
>> > 0x7fffe150: 0x694849a5 DC32 1766345125 ; 'IHi'
>> > 0x7fffe152: 0x6948 DC16 26952 ; 'Hi'
>> > 0x7fffe154: 0xd4fc0700 DC32 -721680640 ; '..'
>> > 0x7fffe156: 0xd4fc DC16 54524 ; ''
>> > 0x7fffe158: 0x07006948 DC32 117467464 ; 'Hi..'
>> > 0x7fffe15c: 0x2001d5fc DC32 536991228 ; '. '
>> > 0x7fffe160: 0x69486050 DC32 1766350928 ; 'P`Hi'
>> > 0x7fffe164: 0xd4fc0700 DC32 -721680640 ; '..'
>> > 0x7fffe168: 0x07006948 DC32 117467464 ; 'Hi..'
>> > 0x7fffe16c: 0x6057d5fc DC32 1616369148 ; 'W`'
>> > 0x7fffe170: 0x21806890 DC32 562063504 ; '.h.!'
>> > 0x7fffe174: 0xfef6f000 DC32 -17371136 ; '.'
>> >
>> >
>>
>

Dave

> Why did NXP (Philips) chose a pin that is commonly used?
>
> There are several pins (144 pin package) that are not used.

Are there really pins which are not used ? I doubt this.

--
42Bastian
------------------
Parts of this email are written with invisible ink.

Note: SPAM-only account, direct mail to bs42@...