Problem downloading to Propeller
bb369
Posts: 9
Hi:
I am having problems downloading code to the Propeller ram or eeprom when installed. I also get an error when using the Identify Hardware option under the Run toolbar of the Propeller Tool. I get the error message that says:
I am having problems downloading code to the Propeller ram or eeprom when installed. I also get an error when using the Identify Hardware option under the Run toolbar of the Propeller Tool. I get the error message that says:
No Propeller Chip found on any serial port
Unable to open com4
I get this same error message trying to download to ram or eeprom. Comm4 is the port assigned by the USB-RS232 installed device driver.
I am using the following setup:
1) Windows 7
2) HyperTerminal or the Parallax Serial Terminal GUI application for RS232 communication - 9600 baud, 1 stop, no parity, hardware protocol
3) USB to RS232 converter driver for a Comm4 connection.
4) The board is a customer designed board which has a functioning eeprom. I am re-writing the code because the previous programmer left and took all source code. So, I am working with known good hardware and rewriting the code. But I have no Parallax product experience.
In the second situation, I have an existing eeprom installed in the board and I use the supplied Parallax serial terminal GUI application. Using this app I can communicate to the board. However, when I substitute the TerraTerm application there is no communication. But hyperterminal works. So I know the comm 4 port works, the cable works and hyperterminal or the parallax serial terminal gui program works.
So there are several confusing points:
1) How does the Propeller Development Tool communicate over the serial link to the Propeller on my board? Does it use my comm port application (such as the Parallax Serial Terminal GUI) or does it have its own rs232 comm program?
2) When I install a functioning eeprom in the board, why does the Propeller serial terminal GUI app talk to the Propeller on my board but terraterm will not? Is there a timing problem due to the fact that the Propeller using software for the rs232 protocol and not hardware or something else? Also, hyperterminal will communicate to the board.
3) Is there some piece of code I am missing in my application? My application consists of my code plus the supplied Parallax Serial Terminal.spin code for handling the rs232 work. But my application code should be independent of downloading code to the Propeller ram correct?
Thank you.
Unable to open com4
I get this same error message trying to download to ram or eeprom. Comm4 is the port assigned by the USB-RS232 installed device driver.
I am using the following setup:
1) Windows 7
2) HyperTerminal or the Parallax Serial Terminal GUI application for RS232 communication - 9600 baud, 1 stop, no parity, hardware protocol
3) USB to RS232 converter driver for a Comm4 connection.
4) The board is a customer designed board which has a functioning eeprom. I am re-writing the code because the previous programmer left and took all source code. So, I am working with known good hardware and rewriting the code. But I have no Parallax product experience.
In the second situation, I have an existing eeprom installed in the board and I use the supplied Parallax serial terminal GUI application. Using this app I can communicate to the board. However, when I substitute the TerraTerm application there is no communication. But hyperterminal works. So I know the comm 4 port works, the cable works and hyperterminal or the parallax serial terminal gui program works.
So there are several confusing points:
1) How does the Propeller Development Tool communicate over the serial link to the Propeller on my board? Does it use my comm port application (such as the Parallax Serial Terminal GUI) or does it have its own rs232 comm program?
2) When I install a functioning eeprom in the board, why does the Propeller serial terminal GUI app talk to the Propeller on my board but terraterm will not? Is there a timing problem due to the fact that the Propeller using software for the rs232 protocol and not hardware or something else? Also, hyperterminal will communicate to the board.
3) Is there some piece of code I am missing in my application? My application consists of my code plus the supplied Parallax Serial Terminal.spin code for handling the rs232 work. But my application code should be independent of downloading code to the Propeller ram correct?
Thank you.