Sure would be nice if the simulator would support the extra ports of the 40 pin parts. Or did I miss some configuration setting?
Also, when set to 28X1 mode, I can't edit variables. It will let me enter a value, but it does not register the change. I don't know if that's an unimplemented feature or if it's just the 28x1 mode that's having problems.
Please also note that there seems to be a serious firmware bug in the 40x1 such that during power on firmware intialization the port c pins (especially pin 0,1) are driven high until the basic code sets them otherwise (as input or low output). This makes using port C a tricky business- as input circuits could get fried, and output circuits get a free power on randomization. I apologize if this is the wrong place for this note- I didn't see a spot for firmware bug reports elsewhere. A test program consisting of nothing or a pause, with LEDs hooked to c0, c1, c2, c3 will confirm this. All 4 of my current 40x1 parts on hand do this.
Bruce M
Snowflake, AZ
Also, when set to 28X1 mode, I can't edit variables. It will let me enter a value, but it does not register the change. I don't know if that's an unimplemented feature or if it's just the 28x1 mode that's having problems.
Please also note that there seems to be a serious firmware bug in the 40x1 such that during power on firmware intialization the port c pins (especially pin 0,1) are driven high until the basic code sets them otherwise (as input or low output). This makes using port C a tricky business- as input circuits could get fried, and output circuits get a free power on randomization. I apologize if this is the wrong place for this note- I didn't see a spot for firmware bug reports elsewhere. A test program consisting of nothing or a pause, with LEDs hooked to c0, c1, c2, c3 will confirm this. All 4 of my current 40x1 parts on hand do this.
Bruce M
Snowflake, AZ
