Messages

Seems like it might be an engineering sample rather than a production part.

What error do you get when erasing? Have you tried lowering the baudrate?

Andy

As mentioned via email, the SWD communications are not reliable. Sometimes you are getting a parity error, other times a malformed packet. I would suspect an electrical issue between the LPC4300 on the LPC-Link2 and the target part.

Thanks for posting the solution - it helps users that come after you.

flashmagictool.com, look on the right.

I have no idea why it can't autobaud at higher speeds. Perhaps put a scope on the Tx and Rx pins, send the '?' and see if anything looks strange. Or you could try using the high speed comms mode in Flash Magic.

With a 12MHz crystal you should be able to connect at 38,400 if not 57,600. Something is wrong. If you are using a USB to RS232 cable then try swapping it for a different one. We recommend genuine FTDI cables. Also try a different PC - could be a Windows driver issue.

Some parts require the crystal frequency to know how long erase and programming will take internally. Some parts don't need this. For the LPC2000 you should enter an accurate value.

Take the blinky example and start modifying it a bit at a time into what you want. When it stops working you have found the cause.

This post contains steps to help debug problems with using the "SWD over Link2" and "SWD over LPC11U35" interfaces.

1. I don't have entries in the Interfaces list

For LPCxpresso boards make sure to install the DFU Link jumper and for LPC-Link2 boards make sure to remove jumper JP1. Connect the boards to your PC and make sure they are recognized by Windows in the Device Manager as "LPC device". Then start Flash Magic. At this point an LED on the boards should start flashing.

2. The LED doesn't start flashing

Check the board has been recognized by the PC. In Device Manager look for "HID-compliant vendor-defined device". Right-click and choose properties. Then click on the Events tab and scroll down in the information box. You should see something like "Parent Device: USB\VID_1FC9&PID_F059\xxxxxxxxxx" where xxxxxxxx is the interface serial number.

For ST parts you will need to use an ST programming utility. Flash Magic is for NXP only.

This topic has been moved to General.

http://forum.flashmagictool.com/index.php?topic=4519.0

I see this in the output from the device:

rx> \0ahave to say for yourself now?\0a\0d

This is not the bootloader running but some firmware instead.

You need to meet all the conditions given in the Flash memory section of the user manual from NXP to start the bootloader. You can check that the bootloader is running by connecting using a terminal program and sending a single '?'. You should get 'Synchronized' back.

Andy

You will need to configure LPXxpresso to output a hex file - it's somewhere in the settings.

Please generate and send a debug file. Instructions are here: http://www.flashmagictool.com/debugfile.html

Andy

Hi, I responded to your email yesterday afternoon with some questions and I didn't see a response back.

Programming external flash isn't supported on the command line. If you are using LabView you should use the included VI which uses the C# DLLs and modify it to program external flash that way.

Andy

You bought a new chip that has been out of production for years? I am skeptical that you bought a genuine part. If it is genuine then I think it has been reclaimed from some old product - that is why it is locked. New parts are not locked. I would return it for a refund.

My advice is to not start a new project on an obsolete chip - switch to ARM-Cortex or something else that is still in production and supported.

Yes you can do parallel programming with the PLCC package. We don't have any information on doing that - you would need to remove it from it's socket and put it into the programmer. I would expect there are many available.

P89C51RD2 and P89V51RD2 are completely different. Only the part names are similar. Instructions for one do not apply to the other.

Andy

Are you able to read the device signature (ISP -> Read Signature...)?

Andy