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 - Rick

Pages: [1]
1
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 10:51:13 am »
Aha!

Right. When I change to Erase All Flash in FM, I get a popup warning me that it will change the parameters to protect the device ISP, fine, good.

When I then try to program the device though, I get a popup error, stating that it can't erase that same page 112 as stated in uVision, because of the settings of the security bits.

So...

The way I see it, my options are...

1) Disable those security bits - but what are they protecting? Am I risking damaging the device? Why were they enabled in the first place?
2) Only program using "erase blocks used by hex file" - will this be sufficient?
3) Find an older version of the program like the 1.95 at the uni, that seems to ignore the error.

2
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 10:40:01 am »
Right, there are 3 blocks of code following. The reason being, that the new one uses a different erase command, which presumably "does the job"?


Original line from uni lab, works correctly

"FM.EXE" "DEVICE(P89LPC935,12.0) ERASE(DEVICE,PROTECTISP) HEXFILE("U:\Blinky\Blinky.HEX",NOCHECKSUMS,NOFILL,PROTECTISP) COM(1,9600) HARDWARE(KEILMCB900)"


Original line from my pc, does not work

"FM.EXE" "DEVICE(P89LPC935,12.0) ERASE(DEVICE,PROTECTISP) HEXFILE("C:\Blinky\Blinky.HEX",NOCHECKSUMS,NOFILL,PROTECTISP) COM(1,7200) HARDWARE(KEILMCB900)"


Save Command Line from FM, new, DOES work

COM(1, 7200)
DEVICE(89LPC935, 12.000000)
HARDWARE(KEILMCB900, 250, 120)
ERASEUSED(D:\Ex935_AD\AD.hex, PROTECTISP)
HEXFILE(D:\Ex935_AD\AD.hex, NOCHECKSUMS, NOFILL, PROTECTISP)


I should state that I've tried both 7200 and 9600 in uVision on my PC with no difference.
The differences I've spotted are the different ERASE commands used, and also the extra HARDWARE parameters passed in the new FM code.


3
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 10:32:26 am »
Andy, you're invaluable, not only can I read the security bits,I can now program using FM and selecting the FM file. I can't even begin to express my gratitude.

However, I am still unable to program it in uVision, which since FM now works, I can only attribute to not passing the correct parameters?

My thanks once again.

EDIT: Having read the security bits in FM, all the bits for Block 7 are set. Is there a reason for this? Are they protecting something important? Or can I just toggle the bit protecting it from erase? Presumably then I also have to toggle the read bit? I DO NOT want to risk damaging this board in any way, since as I said it is not mine, but being able to program directly from uVision would be a great help :)


4
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 09:25:38 am »
Emailed.

I also added an edit into my previous post, but you posted back first.

"EDIT: I should add, I'm a novice to this, I'm just trying to use it for my university project, and have no guru-level understanding of what's going on, and the settings. All the current directives etc are specified automatically since I installed uVision and FM from the LPC900 development kit disc."

5
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 09:16:28 am »
Regardless of the Baud rate I select in FM, it cannot read the security bits, it simply says that it cannot connect at the specified baud rate.

In uVision, even if I change the directive to 7200 instead of 9600, it gives the same error (I should mention that the lab at university, where it DOES work, DOES connect at 9600).
I don't know what the erase is meant to achieve, but at the working machine at university, I CAN load different programs to the board, so at the very least even if the erase fails it's still managing to overwrite the code.

EDIT: I should add, I'm a novice to this, I'm just trying to use it for my university project, and have no guru-level understanding of what's going on, and the settings. All the current directives etc are specified automatically since I installed uVision and FM from the LPC900 development kit disc.

6
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 08:27:26 am »
File sent now, please let me know if you don't receive it :).

Many thanks for your help.

7
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 08:16:15 am »
Sorry, I'm a novice to FM and uVision, where do I add the DEBUG directive?

Many thanks

8
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 07, 2007, 01:50:35 am »
I have now repeated with version 4.01, and I still have problems, but I have a more helpful error message for you :).

I would like to add, that it STILL works perfectly on the computers in the lab, so I am somewhat confused as to the potential hardware implications of this message?


"FM.EXE" "DEVICE(P89LPC935,12.0) ERASE(DEVICE,PROTECTISP) HEXFILE("C:\Blinky\Blinky.HEX",NOCHECKSUMS,NOFILL,PROTECTISP) COM(1,9600) HARDWARE(KEILMCB900)"
Flash Magic Version 4.01.259
8051/XA Driver Version 2.41.258
ARM Driver Version 1.31.258
(C) Embedded Systems Academy 2000-2007 All rights reserved
NON PRODUCTION USE ONLY
Connected
Device selected
Erase failed: invalid command - Operation Failed. (Unable to erase page 112 - erase disabled via security bits) (DEVICE)


EDIT: Oh, I meant to add, I try to Read the security bits in FM itself, but I cannot connect at any baud rate, it always says that it can't connect at the specified baud rate. I tried installing FM 1.71, and managed to read them (all unset), but I was still unable to program it.

9
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 04, 2007, 09:41:10 am »
I shall, many thanks. Due to other commitments I won't be able to try it until late Thursday or Friday, I shall post back on here regardless of the result.

Thanks for your reply.

10
General Discussion / Where can I get old versions of FM?
« on: December 04, 2007, 02:35:17 am »
I'm having some problems with being able to use FM to load my MCB900 board - works fine from one PC, not from the other. My first idea is that they are running 2 different versions - the one that works is on FM 1.95, and the one that doesn't is on FM 3.33. I was wondering if there was anywhere that I could get 1.95 from in order to rule out that possibility?

Many thanks

11
LPC9xx/LPC9xxx / Re: Command Line ERASE Problem
« on: December 03, 2007, 09:08:24 am »
I realise this is an old topic, but I'm having the EXACT same problems.

MCB900 board.

Loads fine on the computers at university, but not at home.

University PCs are running uVision 3.02c, FM 1.95

I'm on uVision 3.03c, FM 3.33

"FM.EXE" "DEVICE(P89LPC935,12.0) ERASE(DEVICE,PROTECTISP) HEXFILE("C:\Keil\C51\Examples\LPC9xx\Blinky\Blinky.HEX",NOCHECKSUMS,NOFILL,PROTECTISP) COM(1,9600) HARDWARE(KEILMCB900)"
Flash Magic Version 3.33.157
8051/XA Driver Version 2.22.156
ARM Driver Version 1.17.157
(C) Embedded Systems Academy 2000-2006 All rights reserved
Connected
Device selected
Erase failed: invalid command (DEVICE)

That's the output I get when I try to compile on the machine at home.

The board is connected via COM1, with the same cable as used at university, and no USB converters are being used.

I'm on XP SP2, UK (International) English.

I'd be grateful if anyone could offer some help, since this is a major obstacle to ease of working on my thesis project.

Many thanks in advance.


EDIT: Just to add to this post, I've checked my port by shorting the pins on the cable, and the PC COM port is working fine (no echo without short, input echoed with short). The board also appears to be fine (all Hyperterminal input echoed when connected, nothing echoed when cable disconnected)

EDIT AGAIN: If I try to program the file directly in FM, I get a popup saying

"Failed to read the device signature (Operation Failed. (reading signature)). Accessing a device using the wrong protocol could render the device unusable. Do you want to continue?"

I always click no, since this is a university board, and I'd rather not risk damaging it!

Pages: [1]