Maker Pro
Maker Pro

ATMEL 89C51RD2 ISP, HEX file programming problem

mcustudent

Jul 23, 2023
3
Joined
Jul 23, 2023
Messages
3
Hi, thank you for taking the time.

I am currently working on a project that uses the Atmel at89c51rd2 PLCC. I had a Lab Pro-51 board but the PLCC no longer connects to FLIP. So, I can't burn a hex file onto the mcu.

I took this opportunity to learn how to wire a minimal ISP programming circuit using Atmel at89c51rd2 PLCC with MAX232CPE+ so that I can make my own basic development board. I am trying out the connections on a breadboard first to make sure that I have it correct, and once I do, then I'll make a PCB. The circuit that I am using is based on the book The 8051 Microcontroller and Embedded Systems: Using Assembly and C. Chapter 8.

See attached image for the debug log of Flip.
Notice that the Flip tool sends a 'U' and the PLCC echos back a 'U'. This means that the bootloader is active and the initialization step is done. However, the Flip tool then sends Hex commands to read the signature byte but the PLCC does not echo back any of the commands. Look to the right panel of Atmel Flip and one thing to note is that the FLIP tool DOES NOT fill in the fields of "Signature Byte", "Device Boot Ids", and etc.
1. I have correctly chosen the device as Atmel AT89C51RD2 and my clock is 11.0592.

From the image, the "Erase" step checks but the "Blank Check" step generates the error "Time Out" and "Cannot write to port".

I've bought several PLCC from different manufacturers ( Digikey, Mouser, Ebay ) and have bought SLSUM and SLRUM versions. However, they all give me the same thing.


Any advice or guidance in getting the Atmel Flip and PLCC to burn a hex file is greatly appreciated.
 

Attachments

  • atmel_flip_debug_log.png
    atmel_flip_debug_log.png
    229.2 KB · Views: 6

kellys_eye

Jun 25, 2010
6,480
Joined
Jun 25, 2010
Messages
6,480
'Cannot write to port' infers a problem with the interface in your PC. Are you using a real serial port or a USB-simulation?

It's a common issue that not all USB-to-serial converters work to the full serial protocol standard and there are recommendations for 'approved' converters that get around this.

Also, check your port programming parameters and that the correct COM port is specified for the device you are using.
 

mcustudent

Jul 23, 2023
3
Joined
Jul 23, 2023
Messages
3
'Cannot write to port' infers a problem with the interface in your PC. Are you using a real serial port or a USB-simulation?

It's a common issue that not all USB-to-serial converters work to the full serial protocol standard and there are recommendations for 'approved' converters that get around this.

Also, check your port programming parameters and that the correct COM port is specified for the device you are using.
Hi,

I'm using a USB to Serial adapter. I've purchased several and some use Prolific while others us FTDI. The one that I have purchased are
0. SABRENT USB 2.0 to Serial (9 Pin) DB 9 RS 232 Converter Cable, Prolific Chipset
1. Tripp Lite 5ft USB to Serial Adapter Cable (USB-A to DB9 M/M)(U209-000-R)
2. BENFEI USB to Serial Adapter, USB to RS-232 Male (9-pin) DB9 Serial Cable, Prolific Chipset, Windows 11/10/8.1/8/7, Mac OS X 10.6 and Above, 1.8M
3. OIKWAN USB to RS232, USB Serial Adapter with FTDI Chipset,USB 2.0 to Male DB9 Serial Cable for Windows 11,10, 8, 7, Vista, XP, 2000, Linux and Mac OS(6ft)

When my Lab Pro-51 board was still working, I used the OIKWAN adapter and it worked fine. After several usages, FLIP no longer connects to the board. I then purchased BENFEI and Tripp Lite but they don't work either.

I purchased another Lab Pro-51 board and used all 3 cables but still won't work. I then uninstalled and reinstall FLIP but no luck. I also made sure to set the configuration parameters.

After all 3 cables didn't work, I purchased extra PLCC and created the ISP circuit on a breadboard. FLIP sends a 'U' and the bootloader echos back a 'U'. This means that the read operation is possible but "cannot write to port" implies write operation is not possible?

I'll check my wiring on the breadboard again but I'm not sure if there is anything else that I can do.
 
Top