Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

JTAG flashing vs. Philips utility- code runs different

JTAG flashing vs. Philips utility- code runs different

2006-03-22 by stephan2148

Hi,
I use the LPC2148 with Jlink IAR.  I use debug flash in the IAR setup,
so that when I unplug the JLINK the code is already flashed in the
part.  I tried to create a hex file in IAR using extra output in
linker options, and Intel-extended format.  It seemed to work, but
when I use the Philips flash utility, the code seems to run a bit
differently (display glitches sometimes P1.16-P1.23).   
Might I be producing the hex file incorrectly, or might some other pin
functions be activating that the JTAG supressed?
Running with the JLINK flashed part runs fine, it's just a hasle.
Thanks for any ideas.
Steve

Re: JTAG flashing vs. Philips utility- code runs different

2006-03-22 by charlesgrenz

Hi Steve,

  You need to set the linker up for IAR as follows:

  Click on "Override default" and put in the filename.hex
  Make sure that debug is unclicked.
  Click on other:
   Output format: intel-extended
   Format variant: 32-bit linear variant
  Modual-local symbols: include all

best regards,
Charles


--- In lpc2000@yahoogroups.com, "stephan2148" <stephan2148@...> wrote:
Show quoted textHide quoted text
>
> Hi,
> I use the LPC2148 with Jlink IAR.  I use debug flash in the IAR setup,
> so that when I unplug the JLINK the code is already flashed in the
> part.  I tried to create a hex file in IAR using extra output in
> linker options, and Intel-extended format.  It seemed to work, but
> when I use the Philips flash utility, the code seems to run a bit
> differently (display glitches sometimes P1.16-P1.23).   
> Might I be producing the hex file incorrectly, or might some other pin
> functions be activating that the JTAG supressed?
> Running with the JLINK flashed part runs fine, it's just a hasle.
> Thanks for any ideas.
> Steve
>

Re: JTAG flashing vs. Philips utility- code runs different

2006-03-22 by stephan2148

Thankyou,  Charles.
I tried that, but when I do I get a compile error undefined external 
_write found in putchar if debug is not selected.  I have read that
this is due to debug mode and the terminal I/O I think, and it tries
to remove it if not in debug mode.  
My code however uses printf, and needs it, which I have also read ends
up resolving to _write which I need.  
So, it is probably due to debug mode being selected.
Having the parameters you have shown with debug selected to allow
compile, I get the hex file, but with the same problem.
Maybe I will try to download the hex from a JTAG'd part to flash
others if fixing the root cause is too painful.
Thanks,
Steve 


--- In lpc2000@yahoogroups.com, "charlesgrenz" <charles.grenz@...> wrote:
Show quoted textHide quoted text
>
> Hi Steve,
> 
>   You need to set the linker up for IAR as follows:
> 
>   Click on "Override default" and put in the filename.hex
>   Make sure that debug is unclicked.
>   Click on other:
>    Output format: intel-extended
>    Format variant: 32-bit linear variant
>   Modual-local symbols: include all
> 
> best regards,
> Charles
> 
> 
> --- In lpc2000@yahoogroups.com, "stephan2148" <stephan2148@> wrote:

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.