Oddities with RS232 and EEPROM

[jharkins]

First, I'm new to the PIC. I've got the PCWH compiler, an ICD-S box, and an IOSoft ER21 platform (18F452 based). When running from the ICD, all reads from the EEPROM return 0xff. When I enter a number (like an IP of 10.2.2.20) it echos the ascii equivalent, coubling the periods (31302e2e322e2e32w3w33230 in this case). There is no code to do this echoing. Finally, when running the RS232 spits out a bunch of numbers and letters that seem meaningless. It's not complete garbage, it's all valid alphanumeric. But again, there is nothing in the code to print this stuff.

Now the odd part. If I download the code into the PIC and disconnect the ICD, then all works fine. My EEPROM has it's valid data, my RS232 does what I expect, etc.

So, ahhh, what do I look for?

jim

___________________________
This message was ported from CCS's old forum
Original Post ID: 10355

[PCM programmer]

:=First, I'm new to the PIC. I've got the PCWH compiler, an ICD-S box, and an IOSoft ER21 platform (18F452 based). When running from the ICD, all reads from the EEPROM return 0xff. When I enter a number (like an IP of 10.2.2.20) it echos the ascii equivalent, coubling the periods (31302e2e322e2e32w3w33230 in this case). There is no code to do this echoing. Finally, when running the RS232 spits out a bunch of numbers and letters that seem meaningless. It's not complete garbage, it's all valid alphanumeric. But again, there is nothing in the code to print this stuff.
:=
:=Now the odd part. If I download the code into the PIC and disconnect the ICD, then all works fine. My EEPROM has it's valid data, my RS232 does what I expect, etc.
:=
-------------------------------------------------------------
I don't have your development environment, so I can't help
too much. But I'd try to find out what line of code is
causing the problem. You could put a while(1); statement
near the start of your program, and re-compile. Then see
if you still get the garbage out. If not, then move it
down a few lines and try again. Eventually, you should be
able to find the exact line that's causing the problem.

This may or may not help. It might turn out to be some ICD
related problem. But it should get you some more information.
___________________________
This message was ported from CCS's old forum
Original Post ID: 10373

[jharkins]

I got this figured out. First, debugging with the ICD clears out the internal EEPROM. As for the RS232 issue, turned out the pins were shared with the 802.11b card. Taking out the card made RS232 work much better.
___________________________
This message was ported from CCS's old forum
Original Post ID: 10419