Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - EdH

Pages: [1]
1
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: September 15, 2006, 03:25:01 pm »
I'm using Windows XP Professional, Version 2002, Service Pack 2, English(US) version.

I did try uninstalling FM, re-downloading, and re-installing FM but still get the same error.

It's odd that the only command that causes an error is:

ERASE(DEVICE, PROTECTISP)

I have tried moving this command after the ERASE(1, PROTECTISP) and after the ERASEUSED(blinky.hex, PROTECTISP).  Those commands always work, but ERASE(DEVICE,  PROTECTISP) still gives the error.

2
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: September 15, 2006, 09:35:32 am »
Andy,

The 2 files should be in your inbox...

Thanks, again.

Ed

3
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: September 15, 2006, 07:03:56 am »
I tried your text file and it still failed with the same error.  After experimenting a little using your text file, I found that the ERASEUSED and the ERASE(1, PROTECTISP) work OK.  I only get the error when the ERASE(DEVICE, PROTECTISP) command is included.

This text file works:

DEVICE(89LPC935,7.372)
READSIGNATURE
COM(1,7200) HARDWARE(KEILMCB900, 50, 100) ERASE(1, PROTECTISP)
ERASEUSED(blinky.hex, PROTECTISP) HEXFILE(blinky.hex, NOCHECKSUMS, NOFILL, PROTECTISP)

Here is the result:

>fm @fm.txt

Flash Magic Version 3.27.130
8051/XA Driver Version 2.14.130
ARM Driver Version 1.13.128
(C) Embedded Systems Academy 2000-2006 All rights reserved
Connected
Device selected
Manufacturer ID: 0x15
Device ID 1: 0xDD
Device ID 2: 0x1E
Erase complete (BLOCK 1)
Erase complete (USED)
Hex file programming complete (blinky.hex)


This text file gives the "Erase failed: invalid commend (DEVICE)" error:

DEVICE(89LPC935,7.372)
READSIGNATURE
COM(1,7200) HARDWARE(KEILMCB900, 50, 100) ERASE(DEVICE, PROTECTISP) ERASE(1, PROTECTISP)
ERASEUSED(blinky.hex, PROTECTISP) HEXFILE(blinky.hex, NOCHECKSUMS, NOFILL, PROTECTISP)

Here is the result:

>fm @fm.txt

Flash Magic Version 3.27.130
8051/XA Driver Version 2.14.130
ARM Driver Version 1.13.128
(C) Embedded Systems Academy 2000-2006 All rights reserved
Connected
Device selected
Manufacturer ID: 0x15
Device ID 1: 0xDD
Device ID 2: 0x1E
Erase failed: invalid command (DEVICE)


I tried this on another PC (both are running WinXP, SP2) with the same results.

I noticed that you are using:

8051/XA Driver Version 2.20.130
ARM Driver Version 1.14.128

These drivers (especially the 8051/XA) are newer than what I downloaded yesterday:

8051/XA Driver Version 2.14.130
ARM Driver Version 1.13.128

Could this make a difference?

Ed

4
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: September 14, 2006, 03:53:33 pm »
Thanks for the quick response , Andy.

I just tried using a text file with your changes, ran it from the command prompt, and got exactly the same error as before (I used fm.txt):

fm.exe @fm.txt

Flash Magic Version 3.27.130
8051/XA Driver Version 2.14.130
ARM Driver Version 1.13.128
(C) Embedded Systems Academy 2000-2006 All rights reserved
Connected
Device selected
Erase failed: invalid command (DEVICE)

Any other ideas?

Ed

5
LPC9xx/LPC9xxx / Command Line ERASE Problem
« on: September 14, 2006, 03:27:25 pm »
I'm using Flash Magic (V3.27.130) in conjuction with the External Programming feature of Keil uVision, and when I try to program my MCB900 board using Keil example MCB900 projects (HELLO, BLINKY or MEASURE) I get:

Flash Magic Version 3.27.130
8051/XA Driver Version 2.14.130
ARM Driver Version 1.13.128
(C) Embedded Systems Academy 2000-2006 All rights reserved
Connected
Device selected
Erase failed: invalid command (DEVICE)

The command line looks like this:

"FM.EXE" "DEVICE(P89LPC935,12.0) ERASE(DEVICE,PROTECTISP) HEXFILE("C:\Keil\C51\EXAMPLES\Philips LPC9xx\Measure\measure.HEX",NOCHECKSUMS,NOFILL,PROTECTISP) COM(1,9600) HARDWARE(KEILMCB900)"

I know this worked on earlier versions of Flash Magic, but I don't remember which version it was.

If I remove the "ERASE(DEVICE,PROTECTISP)" section, I no longer get the error, but, of course, flash is not erased.

I can erase and program the device successfully by running Flash Magic from the Windows dialog, but I would really like to get this working again  via command line from within uVision.  I tried moving the commands into a text file, but was unsuccessful there also.

Do you have any ideas on how to get this to work?

Pages: [1]