Messages

I had the same Error Message, but the Reason was another.

I started programming with the "GettingStarted" Demo from IAR Compiler.
The Configuration for the Project is set by default to "RAM Debug". So the generated hex-File seems to want to programm the RAM what appears to be the Reason for the Error.
With the "Flash Debug" Setting, it works fine

I see, my remembrance was somewhat wrong.
The Compiler (IAR EWARM 5.4 Kickstart) outputs a warning that the hex-File could not be deleted, but the Compiler is able to write the File. Very strange...
So the Problem is not as big as i thought

As previously reported, the warning disapears if FM is closed.

Compiler Output:
"Failed to delete C:\....\Debug\GettingStarted.hex "

I'am using FM 5.32 and WinXP SP2.

If i have programmed my Device with FM and want to compile a new Version, the Compiler outputs a Error, because the hex File is unable to access. If i close FlashMagic the File is released an can be accessed by the Compiler.

So it would be nice if FlashMagic would close the hex-File always after programming. Then i could compile and programm without always closing FlashMagic

Sir actually i am a student and I don't have enough budget for that...

Can I connect TX and RX pins of MAX232 to UART0 of the ARM.And What about pins like rest(or other connections)...

Thank u sir...

Look into the AN10302 from NXP (Page 5) or the "LPC-1766STK-SCH.PDF" (RS232_0) Schematic. Both Files can be found easily with google

To solve the "Problem":
The NXP Support said it is a Engineering Sample and the Signature is not the same like the "real" one...

Since there is no Section for the LPC17xx Series, i choose the LPC2xxx Area

I want to programm a LPC1766 and FlashMagic (5.32) tells me that the Signature ist wrong 
It reads the Signature as 0x26013733. But that would be the right Signature for the LPC1765 according to the Flash Magic List.
My Chip is clearly labeled with LPC1766.

Bug in FlashMagic?