ICD and USB UART device

[tumbleweed]

At least I incorporated the pull-up resistor

What "pull-up resistor" is that? Is there something missing from the X1 board?

[Demon]

The instructions seem a little vague, saying it can be configured for both ICSP and ICD. But it only mentions the pull-up in the ICD section.

"The debugger system can be configured to use standard ICSP communication for both
programming and debugging functions."

So I hid one in the hotglue and the ICSP seems to run fine. The hotglue is not elegant, but it keeps all the fine wires separated and adds A LOT of strength to the connector.

[Demon]

What "pull-up resistor" is that? Is there something missing from the X1 board?

The pull-up on the Lab X1 is only 1K, the PK4 wants 10-50K. So I slapped in something in the 20K range; whichever one I had the most.

The 1K probably might have been enough, but I'm getting enough pesky problems without creating more of my own.




Example of pesky problem: trying to get example code taken from the MSFS SDK docs to work. Except, the example code is missing a parameter.
Took me a while to track down the problem. The DEVs were really helpful though. Had a few of these pesky problems since I started this project.

[tumbleweed]

The instructions seem a little vague, saying it can be configured for both ICSP and ICD. But it only mentions the pull-up in the ICD section.

The PIC ICSP and debug connections are the same. In Table B-5, ignore the "debug" column (that's not for a PIC device) and just use the ICSP column connections.

Whatever you add externally to the VPP/MCLR is just going to go in parallel with the 1K on the X1 board (lowering the R), so I'd remove it.

Do you have the JP1 jumper installed? If you tell the PK to use target power then it must be connected as it uses the target VDD connection to power the output drivers of the ICSP lines.

[Demon]

The PIC ICSP and debug connections are the same. In Table B-5, ignore the "debug" column (that's not for a PIC device) and just use the ICSP column connections.

Yeah, I realized that after I posted that pic and started googling those acronyms.

Whatever you add externally to the VPP/MCLR is just going to go in parallel with the 1K on the X1 board (lowering the R), so I'd remove it.

Having 1K in parallel with 20K shouldn<t have an impact when the allowable range is 10-50K, I would think.

Do you have the JP1 jumper installed? If you tell the PK to use target power then it must be connected as it uses the target VDD connection to power the output drivers of the ICSP lines.

Yup, JP1 is ON, I use an external power supply for the Lab X1. I have a fear of overloading USB ports on my PCs, practically a phobia.



I'm taking a mental break from trying to get ICD working on my PK4. I still haven't investigated that other "ICD" command line that I found (although part of me is afraid that only works from MPLABX).



I'm in the process of finishing up a tutorial on adding a COM port in Visual Studio to a basic GUI using C++. I have some MCP2221A-I/P coming in from Newark, so I'm going to investigate using UART. These USB ICs gets recognized as an ordinary serial port in Windows.

I got frustrated with the pains of MCS+5 generating obsolete USB code in C++ version6 (that's like 25 years old). Despite DT's efforts to simplify matters in PBP, I just find the whole USB connectivity thing cumbersome.

[tumbleweed]

Having 1K in parallel with 20K shouldn<t have an impact when the allowable range is 10-50K, I would think.

You might want to rethink that. What's 1K in parallel with 20K?

Although to be honest, I've used 1K before without too many issues.

[Ioannis]

Get rid off the 1K resistor. LABX1 was on a very safe side with this value and with 20K in parallel you are now less than 1K.

Are you trying to have ICD with Basic?

Ioannis

[tumbleweed]

Wouldn't it be better to just change the 1K to a 10K on the X1 and get rid of the extra resistor in the cable?
That way you still have the MCLR pullup on the board.