SPI Loop Back
I just spent a few hours (and probably days before this) over an issue that should not happen. I'd love to hear it is operator error so i can stop running into it...
SPI Loop Back example, PIC32MZ-EF starter kit.
Using it on an EFG100, so changed the processor, checked the config bits, went through the pin settings, made everything an input available except SDI2 (RG7), SCK2 (RG6), and SDO2 (RC4).
The program built as soon as I conditionally compiled out the BSP specific app code.
Ran, but rxdata was all zeros.
I had a scope on SCK and one on a joined SDO/SDI pair.
I assumed there must be a short on my board at SDI, so I soldered a 1K between the wires, and monitored both sides of the 1K... no short, stall all zeros.
Long and frustrating story short, ANSELG<7> was set. I modified SYS_PORT_G_ANSEL and the demo works...
Of course I was using the demo because WINC1500 demo did not for several days...
I gut the traces to the module to back up to this test, so now I get to white wire those back.
Bottom line is that the Harmony 2.04 system port object pretty much ignores changes made in pin settings or pin diagram windows. It also still likes to reset my clock and ICD settings...
post edited by MikeinAZ - 2017/10/16 09:45:13