The in-circuit programmer that I was using for the 8051 (AT89S51) seems to have some problems with programming the chips correctly. The data is sent and verified, but then a memory map pulled from another method does not show the same results. To be more specific, I wrote a serial programmer in LabView that I used to verify the operation of the parallel-port ISP and found that the parallel-port ISP did not program all of the bytes correctly. Although the LabView programmer can program the whole chip without problems, it is very, very slow (doesn’t take advantage of page-write or DIO buffering.) I did manage to put PAULMON2 on one of the AT89S51 chips some time ago, so the current plan is to use that chip and external nv-ram to test code on or just move to a DS80C400, which has a built-in serial monitor. It seems that using a boot monitor is the easiest path to testing code on the 8051. For kicks, the poorly done LabView code is attached at the end.

LV.JPG

( nchernyy-serial-programmer-slowio.zip )

 
del.icio.us | digg