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.

Topics - TomP

Pages: [1]
LPC9xx/LPC9xxx / 89LPC932A1 & Vista (or Win 7)???
« on: August 30, 2010, 12:21:34 pm »
We have an in-house designed programming board that uses RTS & DTR to ISP several of our products that use the 89LPC932A1. There's been no issues with it until recently. I just "upgraded" to a new PC that has Vista-64 versus the old PC that ran XP Pro. The problem is, now FM doesn't work with the on-board serial port, or the add-in serial card (Rosewill RC-301)! It gives the dreaded "autobaud" failure message.

I can take the programming board connected to the product board over to the old PC and check the Device Signature as a quick test, with no problem. I've scoped everything out on the new PC and it looks like there is some strange timing issues between RTS & DTR, irrespective of which port I try. I did download and install the latest driver for the Rosewill card, but to no avail. I have the latest FM: 5.69.2060.

So has ANYBODY programmed an LPC9xx part using the RTS/DTR method under Vista or Win 7? (We tried it on the IT guy's PC with Win 7 and if failed there too).

Note: I have programmed an LPC1114 with the same new PC and FM with no problems, but of course, this does not use the same interface as an LPC9xx.


ARM Cortex / "Erase All Flash+Code Rd Prot"?
« on: April 21, 2010, 08:13:09 am »
I've got FM connected to an LPC1114/301.

The Erase Flash menu gives the option to "Erase All Flash+Code Rd Prot".

I understand that "Code Rd" refers to the Code Red LPCXpresso stuff, but what exactly does "Prot" mean? Protected?


We've been having difficulty (for some time, I just found out. Thank you Manufacturing for keeping me in the dark!) programming a product that has a P89C51RB2H on it. We get the "Unable to connect at specified baud rate..." message. The crew doing the programming sometimes have to try programming it multiple times (5 is not uncommon) to have FM get a valid reply. At first I thought it was because P2.6 & P2.7 were unconnected, but tying them high doesn't help. So I drag out the scope and look at the serial data. Our RB2H has the standard 11.0592MHz crystal (scope confirms the crystal is good), and we're trying to communicate at 57.6K baud.

Here's the weird part: The baud coming from the RB2H is measured to be 52.9K?!?

Is this because FM sends the crystal freq as 11MHz? I can't find boot source code, so I don't really know what they use for the baud rate clock.

Sometimes it sends back 'u' in response to the 'U'. Is this some kind of error message? Another reason I'd like to see the boot source code.

Lower bauds work better, but still not consistently. Results can vary from board to board.

Ideas? Suggestions? Chocolate cookie recipes?



LPC9xx/LPC9xxx / Security bits in unused blocks?
« on: November 02, 2006, 07:43:41 am »
I've got code that fits in Blocks 0 to 2 of a 922. Somehow (don't know how), the security bits for Block 3 got set. When I reprogram the software, with the security bits cleared for all blocks, the Block 3 bits are still programmed.

Does this mean that FM programs only the security bits for the blocks that have code in them? Or am I missing something?



Pages: [1]