2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

What would a reason be that an LPC2366 will not run without my IAR EWARM 5.4 and the Segger JTAG being connected ??? I've seen this
before I think, but cannot remember why this might be.
It gets stuck in a Data Abort loop.

I can get the code to run by just "attaching" the debugger in the OPTIONS, rather than having to download the code. It will continue running if I remove the JTAG connector too. Seems that if I am
quick enough, I can even remove power for a split second.
After I have the target running, and then pull the JTAG connection,
I can do a hardware RESET and the processor will come up and
run also. If I power the target down for just a second or more,
I need to put the JTAG back on, put it into a debugging mode by attaching, and then sofware (JTAG) RESET and it will run again.

Any experience here ??

Thanks,
boB

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

--- In l...@yahoogroups.com, "bobtransformer" wrote:
> What would a reason be that an LPC2366 will not run without my IAR EWARM 5.4 and the Segger JTAG being connected ??? I've seen this
> before I think, but cannot remember why this might be.
> It gets stuck in a Data Abort loop.
>
> I can get the code to run by just "attaching" the debugger in the OPTIONS, rather than having to download the code. It will continue running if I remove the JTAG connector too. Seems that if I am
> quick enough, I can even remove power for a split second.
> After I have the target running, and then pull the JTAG connection,
> I can do a hardware RESET and the processor will come up and
> run also. If I power the target down for just a second or more,
> I need to put the JTAG back on, put it into a debugging mode by attaching, and then sofware (JTAG) RESET and it will run again.
>
> Any experience here ??
>
> Thanks,
> boB
>
In addition, I notice that when I DO pull the power for about 1 and 1/2 seconds, the 3.3V drops to around 0.75V, and letting it drop any further, it will not start again when power is applied without the help of the JTAG.

It's almost like the chip remembers that the JTAG was connected until the Vcc drops below that point.

boB

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

--- In l...@yahoogroups.com, "bobtransformer" wrote:
>
> >
> > What would a reason be that an LPC2366 will not run without my IAR EWARM 5.4 and the Segger JTAG being connected ??? I've seen this
> > before I think, but cannot remember why this might be.
> > It gets stuck in a Data Abort loop.
> >
> > I can get the code to run by just "attaching" the debugger in the OPTIONS, rather than having to download the code. It will continue running if I remove the JTAG connector too. Seems that if I am
> > quick enough, I can even remove power for a split second.
> > After I have the target running, and then pull the JTAG connection,
> > I can do a hardware RESET and the processor will come up and
> > run also. If I power the target down for just a second or more,
> > I need to put the JTAG back on, put it into a debugging mode by attaching, and then sofware (JTAG) RESET and it will run again.
> >
> > Any experience here ??
> >
> > Thanks,
> > boB
> >

> In addition, I notice that when I DO pull the power for about 1 and 1/2 seconds, the 3.3V drops to around 0.75V, and letting it drop any further, it will not start again when power is applied without the help of the JTAG.
>
> It's almost like the chip remembers that the JTAG was connected until the Vcc drops below that point.
>
> boB
>
I figured I better post the fix I found, just to make this complete for either me or whoever might benefit. I still do no understand why attaching the JTAG in IAR-EWARM stops this Data_Abort interrupt exception from happening.

So, this project has a Bootloader at low memory with LPCUSB resident.
The main application calls the LPCUSB functions in the bootloader and so they must be "Located" at fixed locations. This, I have done already. However, there was a variable structure, called rxfifo that I was calling in the main application with the line...

if(fifo_get(&rxfifo, &rbyte)) {
rbyteUSB = rbyte;
more code etc...

and the location of rxfifo changed and when I went from IAR EWARM version 4.x to version 5.x all those methods of locating code and variables changed. I relocated the functions but not this variable structure. I use this method instead of VCOM_getchar() so I don't have to sit in a loop if there is nothing from the PC Host USB side to receive.

I still would like to know how/why that the JTAG changes things so that the Data_Abort doesn't happen while it is attached and monitoring things.

Now I can take my wife to a nice steak dinner like I wanted to a week ago when I was banging my head against a wall with other problems, all related to changing IAR EW compiler/linker versions and LPC2xxxx processor types.

boB

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )