Re: ATWINC1500 (Part #2 of Likely So Many)
Hi Dan. Thank you for that suggestion. It appears to have the same transmitter that I am playing around with. Main difference is it looks like it has an embedded controller and can function more standalone than the WINC1500 XPRO that I picked up. It helps to look at the circuitry, for verification, and I think I am probably at the same point. The built in MCC code generated as pertains to the nCS question (the version I am tinkering with) appears to come from the MCC WINC function block and pin configuration and I think the answer is that nCS in this context connects to SPI_SSN abstracting hardware. I am able to call some functions from the controller and it appears that the WINC is overwriting test variables with return values so at face value it appears to be functioning from a hardware perspective. Example code from MCC generation is minimal at best. Basically try to connect to SSID and handle background tasks, nothing else. I am not able to connect to SSID with this so I am trying to see if there are stock functions that return test values I can use to verify SPI is working properly rather than perceived return value updates being a fluke. I haven't worked with this software before so I have no idea what I am doing and can hopefully piece this together via MLA and your suggestion above.
In my mind, being totally new to this the odds are slim I am going to be able to do much with it on my own so I may have to turn to the dev board for a polished example and kind of break that down once I have a better understanding and apply to more piecewise stuff I am tinkering with.