Messages

I can see the same behavior. At 6 clocks/cycle, 19200 works fine. At 12 clocks/cycle, 19200 works some of the time, 14400 seems ok, 9600 seems ok. If I enable high speed comms, select 12 clocks/cycle and switch to 9600 baud, I can erase, program, etc. fine at 19200 baud.

What I see at 19200 baud is that the autobauding appears to be successful, but then the device echoes junk back in response to commands. This tells me that 19200 baud almost works.

It seems that 19200 is just a little too high for this device to autobaud at when running at 12 clocks/cycle.

I'm not quite sure why autobauding at 19200 works ok on Win95/98. The only thing that I can think of is that either WinXP or Win95/98 is less accurate at generating exactly 19200 baud.

When using high speed comms, make sure the number of clocks/cycle you select matches your device. In this case you need to select 12 clocks/cycle.

I checked into this and found that I broke the reset/execution function in version 1.82. This will be fixed in version 1.83 which will be available early next week. Sorry for the inconvenience.

I checked into this and found that I broke the reset/execution function in version 1.82. This will be fixed in version 1.83 which will be available early next week. Sorry for the inconvenience.

There has been an increase lately in people asking their questions by adding on to an existing but unrelated topic. If you wish to ask a question that is not currently discussed by another topic, then please start a new topic. You can do this by clicking on the "New Topic" link at the top left of the forum index and on pages displaying topics. Thank you.

WinISP and Flash Magic cannot program the LPC7xx devices. Philips has written Application Note AN466 which gives details on programming these devices using a commercial programmer.

http://www.semiconductors.philips.com/acrobat/applicationnotes/AN466_2.pdf

It appears that the uninstaller does not remove the registry entries like it is supposed to. This will be fixed in the next release, which should appear early next week.

You have two options. Manually remove the registry key, which you do at your own risk, or wait for the new version.

1. Remove registry key

Uninstall Flash Magic
Go to Start -> Run and enter "regedit"
Browse to "HKEY_CURRENT_USER\Software\Embedded Systems Academy"
Delete the "FlashMagic" entry
Reinstall Flash Magic

2. New Flash Magic version

When it comes out uninstall what you currently have
Install the new version
Uninstall the new version (removes registry entries)
Install the new version

It could be that the settings stored in the registry have become corrupted. Uninstalling and reinstalling is the best way to solve that. Please give it a try and let me know if it helps or not. Install the latest version too if you are not already running it.

If you are talking about In-System Programming (ISP) then you can write a windows program to call the command line version of Flash Magic and perform any operations you want.

If you are talking about In-Application Programming (IAP) then we have a library on our web site that makes the IAP calls look like C functions. You might have to modify it slightly from the Rx2 version (check the SFR locations). Also if you are not using the Keil or Raisonance compilers then you will need to rewrite the C - Assembler interface. The actual assembler code will probably remain the same however.

http://www.esacademy.com/faq/progs/flash.htm

It sounds like Flash Magic might be retrying everything and most of the time succeeding on a retry, but not always.

Try increasing the timeouts in Options -> Advanced Options -> Timeouts. This was added for people using those USB to COM port converters. They don't always behave exactly like a real COM Port.

Note also, that if you are using a low crystal frequency such as 6MHz, then you will likely need to use a very low baud rate, such as 4800 or 2400.

First check using your parallel programmer that you haven't changed the boot vector from the default, as Erik suggested.

Second, to test entering ISP mode simply connect to the device using Hyperterminal as described in the app note and send a single uppercase 'U'. It should be echoed back. If not then you need to investigate why it wasn't echoed back. The app note leads you through this. For example, did the 'U' reach the device? Was the baudrate at the RxD pin what you expected? Sometimes optocouplers can affect the baud rate for example.

If you can get the 'U' to echo back, then Flash Magic should work at the same baud rate you used in Hyperterminal. Make sure you enter an accurate crystal frequency and turn off high speed communications (and half-duplex communications if possible) to simplify the situation.

It could be many things. What crystal frequency are you using? If it is 10MHz or higher then 9600 baud should definately work.

You said you are followed application note 4. What are the results of performing the tests in section 4.1 - "Terminal Test"? That will tell me a lot.

If you didn't send any ISP commands then the status bit should still be set, so when you power the device up it should enter ISP mode again.

What way? I really an cunfused as to what you are asking? It's very simple:

Parts with 'H' in the name require a parallel programmer.

Parts without 'H' in the name can be changed with Flash Magic or a parallel programmer.

Thats all there is to it.

The CKCON SFR is only implemented on the newer 89C51Rx2xx devices, which can be changed between 12 clocks/cycle and 6 clocks/cycle in software.

The CKCON SFR does NOT exist on the older 89C51Rx2Hxx device. Note the 'H' in the part name. This discussion is about the older devices, not the newer ones. Although the parts have similar names, they are NOT THE SAME.