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 - Andy Ayre

Pages: 1 ... 3 4 [5]
61
LPC2xxx / Read First Before Posting
« on: October 05, 2007, 11:44:59 am »
Before posting make sure you have read through and tried the suggestions in this post:

  http://forum.flashmagictool.com/index.php?topic=3273.0

Posting the results of your tests will increase the chances that someone reading the forum will be able to help you, and help you quickly.

Andy

62
LPC9xx/LPC9xxx / Read First Before Posting
« on: October 05, 2007, 11:44:23 am »
Before posting make sure you have read through and tried the suggestions in this post:

  http://forum.flashmagictool.com/index.php?topic=3273.0

Posting the results of your tests will increase the chances that someone reading the forum will be able to help you, and help you quickly.

Andy

63
P89C51Rx+/P89C51Rx2/P89C66x/P89C6xX2/P89V66x / Read First Before Posting
« on: October 05, 2007, 11:43:08 am »
Before posting make sure you have read through and tried the suggestions in this post:

  http://forum.flashmagictool.com/index.php?topic=3273.0

Posting the results of your tests will increase the chances that someone reading the forum will be able to help you, and help you quickly.

Andy

64
General Discussion / MOVED: Reset Device Box
« on: July 17, 2007, 09:49:28 am »

65
LPC9xx/LPC9xxx / MOVED: help using DAC in LPC925
« on: March 20, 2007, 11:26:01 am »

66
General / RS232 to USB Cables That Work (Or Don't)
« on: January 24, 2007, 11:17:38 am »
This thread will be used to compile a list of RS232 to USB cables that work with Flash Magic and NXP microcontroller bootloaders. If you have one please post the details.

67
General / Debugging ISP Problems
« on: January 24, 2007, 09:58:36 am »
These are the steps to go through when ISP does not work. Some are device specific and are indicated with [<devicename>] before the item. For example, [LPC9xx]. This list will be added to over time based on discussions in the forums.

By completing these steps and posting the results that you get and the checks that you have performed in the forums when posting your problem, it will be quicker and easier for others to provide suggestions or even answers.

1. Ensure the crystal frequency entered is accurate. For example, if you are using 11.0592MHz, then enter 11.0592, not 11.0000 or 11.

2. If you are using high-speed communications mode with the correct frequency entered, then try connecting with the feature turned off. Make sure the device is reset again into ISP mode if needed before attempting to connect.

3. If you have the half-duplex communications feature turned on and you do not need it, then turn it off. It only slows down the serial communications.

4. If you are using a baud rate higher than 9600, lower it to 9600, reset the device into ISP mode (if applicable) and try again. The baud rate at which you are able to successfully connect to the device depends on which device you are using, the crystal frequency you are using and how many clocks per cycle the device is configured for.

5. If you are already using 9600 baud, or lowering to 9600 baud does not work, then try 4800 baud. If your crystal frequency is 6MHz or below, try the baud rates below 4800 baud.

6. Ensure you have the correct device selected in Flash Magic. Some of the devices have very similar names. If you change the device then ensure you reset the device into ISP mode if applicable before trying again.

7. Ensure the COM Port selected in Flash Magic is the correct one you are using.

8. Check the datasheet and Philips Application Note AN461 for details of the requirements to place the device into ISP mode using hardware methods. Ensure the voltages on the necessary pins are at the expected levels.

9. Ensure the power supply to the device is stable, within the allowed range, and free from glitches.

10. Ensure your ground is stable and it is not floating. A floating ground will cause devices to behave erratically or incorrectly.

11. [89C51Rx2Hxx, 89C66x] Ensure P2.6 and P2.7 are pulled high during reset into ISP mode.

12. [LPC9xx] If the Keil MCB900 board is being used, then ensure the power is removed and reapplied after changing the jumpers. Failure to do this could cause the device to enter an unknown state.

13. Try connecting to the device using Hyperterminal or any other terminal program, such as Tera Term Pro. Hyperterminal comes with most versions of Windows and is usually available from the Start Menu, under Start | Programs | Accessories | Communications. If it does not appear on the Start Menu, then you may need to install it. The method to do this varies between different versions of Windows, but in general:

Click on Start | Settings | Control Panel
Choose Add/Remove Programs
Click on Windows Components or similar
Search for the checkbox for Hyerterminal and check it. You may need to keep selecting categories and clicking on the Details button to view more choices.

Once you have a terminal program running, select the COM Port you are using and create a connection with the following configuration:

8 bits
No parity
One stop bit
No handshaking or flow control
9600 baud or 4800 baud
No local echo (if available)

If you are using the Start BootROM feature, then send the Start BootROM command your device expects. If the command and/or the full stop response are not echoed back, then the problem potentially lies in your application code.

Next:

Reset the device into ISP mode if applicable.
Send a single uppercase U ('?' for LPC2xxx devices)

If the device fails to echo the uppercase U (or '?') back to the terminal program then there is a COM Port, serial cable or device problem.

14. check using an oscilloscope:

For LPC2xxx devices a '?' is used instead of a 'U'.

If the U is not arriving at the RxD pin of the device then it is a COM Port or serial cable problem.
If the U is arriving, but no U is leaving the TxD pin in response, then the device is not executing the bootloader for some reason. Check how you are placing the device into ISP mode.
If the U is leaving the TxD pin of the device but not arriving at the terminal program, then it is a COM port or serial cable problem.
If the baud rate of the U is not the baud rate selected in the terminal program, then either the PC COM port is faulty, or there is something like opto-isolators affecting the baud rate.

If the device echoes back the U to the terminal program then try sending some ISP commands to the device and seeing if they are echoed back. If any response from the device takes longer than about 10 seconds, then perform the Last Resort steps below.

If the device echoes back the U and all ISP commands and responses then the problem likely lies in Flash Magic somewhere.

15. try using a different device, different COM Port or different PC, with a different version of Windows.

16. If you are using the COM Port control signals DTR and RTS to place the device into ISP mode, look at the signals on an oscilloscope and compare them with the waveforms shown in Flash Magic Application Note 1. If there are differences, check your circuit.

Ensure the timing for T1 is at least 50ms and T2 is at least 100ms. Try increasing both values to 200ms and 300ms respectively.

Try temporarily using switches or jumpers to place the device into ISP mode, rather than using DTR and RTS. Turn off the option in Flash Magic to use DTR and RTS.

17. Another cause of problems could be that your device is taking a little longer to respond than Flash Magic allows. This problem has been most frequently observed during device erasing or when using some types of USB to RS232 converters or cables.

To increase the timeouts in Flash Magic go to the Options menu, choose Advanced Options and click on the Timeouts tab. Check "Use my timeouts for ISP operations" and increase the values displayed in the boxes. Keep increasing the timeouts one or two seconds at a time and retesting.

Note that increasing the timeouts has the downside that if something should go wrong during an ISP operation, or if you start Flash Magic with no device connected, then you will have a longer wait before Flash Magic gives up trying.

68
General / Generating a Debug File (Updated)
« on: January 24, 2007, 09:46:47 am »
Generating a debug file allows us at ESAcademy to see what is going on between Flash Magic and a device. The instructions for generating a debug file are given below. However, before generating the file first try to diagnose the problem by completing some basic steps. The steps are given here:

  http://forum.flashmagictool.com/index.php?topic=3273.0

To generate a debug file:

1. Start Flash Magic
2. Click on the entry in the COM port field to give the Flash Magic window the focus
3. Press F1 to enter debug mode ("Debug" will appear at the top of the window)
4. Perform the specific operation or operations that you are having a problem with. For example, ISP -> Read Device Signature...
5. Wait for any error message and make a note of it.
6. Press F2 to exit debug mode

Versions 6.76 and later

The debug file is located in the "My Documents" folder and will have the name "flashmagic-date-time.fmd" where date and time are when the file was created.

Versions 6.75 and earlier

Start Flash Magic with Administrator permissions.
The debug file is located at C:\flashmagic.fmd.

69
General / MOVED: LPC925 ISP - Erasing Hangs FM
« on: January 01, 2007, 10:04:10 am »

Pages: 1 ... 3 4 [5]