Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
LPC2xxx / Re: After Update to V10.66 Flash Magic's fm.exe does not work anymore
« Last post by Andy Ayre on October 12, 2017, 07:00:42 am »
Looks like you are still running an old version. The version number shown should be 10.67.4823. To double-check I just re-downloaded and installed it and it is correct for me.

Andy
22
LPC2xxx / Re: After Update to V10.66 Flash Magic's fm.exe does not work anymore
« Last post by crossing on October 12, 2017, 06:23:29 am »
Sorry, still answers with
Flash Magic Version 10.30.4694
8051/XA Driver Version 3.51.4763
ARM UART Driver Version 5.01.4766
ARM Cortex UART Driver Version 7.91.4816
ARM Ethernet Driver Version 2.22.4763
ARM Cortex Ethernet Driver Version 2.61.4763
ARM CAN Driver Version 3.30.4776
(C) Embedded Systems Academy 2000-2017 All rights reserved
NON PRODUCTION USE ONLY
Erase failed: not connected (DEVICE)
23
LPC2xxx / Re: After Update to V10.66 Flash Magic's fm.exe does not work anymore
« Last post by Andy Ayre on October 11, 2017, 06:41:58 am »
Please try version 10.67 and let us know if you still have a problem.

Andy
24
LPC2xxx / After Update to V10.66 Flash Magic's fm.exe does not work anymore
« Last post by crossing on October 10, 2017, 01:08:08 am »
After Update to V10.66 Flash Magic's fm.exe does not work anymore:
Error "device not connected" appears.
I double checked the Parameters and even tried the "fm.exe @commandfile.txt"- way. Same result.
(The "Windows Version" works fine, nevertheless)
(I tried with and without installing the USB Driver Option. It is not needed as I use a Serial port)
When uninstalling 10.66 and installing the old 7.66 everything works fine again. (7.71 works fine, too)
Is this a known problem or can anyone confirm it works in 10.66 without issues?
25
Thanks for your reply Andy.

I can confirm that the status byte is 0x00 by reading it back but it still takes another go at programming for it to change the boot location.

This is the last of our stock so I have to switch to an Atmel device next time anyway.

Nick
26
Yes, FM sets the status byte to zero after successful programming. Perhaps age has affected the parts in some way and it takes two attempts to program that location to make it stick?

Probably the best thing to do for the future is to use the command line version so you always explicitly set the status byte after programming.

Andy
27
We have recently programmed 100 pieces of a product that uses the P89C51RD2HBBD MCU.  This is old Philips stock with date code D0047 G (I think - can't find any doco on this!).
 
On 12 of the boards it was noticed that after programming, verifying successfully then being reset the MCU did not run the application code.  Later investigation showed that the MCU would continue to start in boot loader mode (i.e. boot from 0xFC00).  When power was applied I could communicate with FlashMagic without needing to force entry to the boot loader mode by holding PSEN low at turn on.  With FlashMagic I checked that the device was not blank and verified the code successfully with the hex file.

Using FlashMagic I was able to program the status byte and boot vector separately to the memory space.  I set the status byte to 0x00 and left the boot vector at 0xFC.  After this operation the MCU restarted running the application code.

It is my understanding that FlashMagic would set the status byte to 0x00 after successful programming.

Has anyone seen this behaviour before?  Is there some timing relationship between finishing the verify and programming the status/boot vector bytes that is marginal on these MCUs?

There is a momentary switch attached to PSEN to pull low if ISP mode is needed after programming but I think it unlikely that that this pin was getting a repeatable low glitch at boot up on only these 12 units.

We used FlashMagic 6.77.2724 (this is the free version - we also own a production version license but this was not installed).

Thanks in advance,
Nick
28
LPC2xxx / Re: Failed to read device signature (operation failed, reading signature)
« Last post by Andy Ayre on September 12, 2017, 12:39:40 am »
Please generate a debug file then post back with it attached. Instructions are here:

  http://www.flashmagictool.com/debugfile.html

Andy
29
LPC2xxx / Failed to read device signature (operation failed, reading signature)
« Last post by evoluer on September 12, 2017, 12:19:22 am »
Hello all,
I am having a problem for the last 3 weeks and i am not able to find a solution for it. Let me explain the problem in detail.

When i try to download the program, i get the following error Failed to read device signature ( operation failed .(reading signature)). Accessing a device using the wrong protocol could render the device unusable. Do you want to continue?

controller: lpc2148
oscillator: 12MHz crystal
serial connection through max3232
reset and program switch connection
Software used : Flashmagic version9.73.4146 arm7 UART driver version: 5.00.3965

Hope someone can point me in the right direction
30
ARM Cortex / Re: LPC54608 returns invalid device ID
« Last post by Andy Ayre on September 11, 2017, 01:19:05 am »
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
Pages: 1 2 [3] 4 5 ... 10