At the execution at the Enable command I have an invalid io exception.
Is there any limitation in using the PB6 that is assigned as the QSPI chip select? ( which however on this board I don’t use ).
I’m using the same example posted on the documentation site which works great for me with the Fez Feather.
NO,
using PD6 as RST for this device,
is on a prototype board and I have not wired any other interface. Only WINC is connected on the SPI3 at this time and no other GPIO is used and configured.
The CHIP_EN of the WINC is also driven with a delay circuit to keep it low at power up for 3 seconds … then bring it to 3V3 with a 10K is enough to bring the device active or need a drive current ?
…is very very strange.
Can you run this quick test please? On a new project, create a GPIO input pin on PB6 and enable interrupt. You do not have to physically try it, just see if you get an exception.
Of course I am assuming you did not extend flash and you are not using QSPI in your design.
var _interruptPort = GpioController.GetDefault().OpenPin(SC20100.GpioPin.PB6);
_interruptPort.SetDriveMode(GpioPinDriveMode.InputPullUp);
_interruptPort.ValueChangedEdge = GpioPinEdge.FallingEdge | GpioPinEdge.RisingEdge;
… with no exception.
However, I first tried the same board wiring SPI3 with an ENC28J60 and with a WIZ5500 using practically the same lines for the same functions.
Can it be a 100K pullup resistor on the INT line (the PB6) at VCC before its definition as an INT line of the module ?
Is there a check on its logical state before its use ?
If so, the exception is thrown correctly
NOTHING TO DO.
Model ATWINC1500-MR210PB1952 there is no way to make it work !!!.
I have come to the conclusion that the problem is the firmware on this model because I took apart the WINC of a Fez Feather and mounted it on my board and it works great as other two Click 7 from Mikroe.
As long as it’s just a firmware problem … the strange thing is that the error appears whether the module is connected or not and I have tried 3 modules of this serie.
I’ll try to flash one with the updated FW and I’ll be able to tell you.
Does anyone have my same problems with the latest WINC1500 modules on the market?
These are modules that I ordered in November 2021 and they arrived in March of this year.
CHIP_EN is on a GPIO as in your wifi example… the problem is that I have 10 WINC modules purchased in March which are not working.
The program (the WiFi example of your site) and the self-built card works with :
a WINC removed from your Fez Feather
a WINC removed from a Mikroe Click 7
… but not with 2 of the 10 ATWINC1500-MR210PB1952 just purchased.
The error is generated with or without the module as if the bus were disconnected.
Firmware version. Officially, support is 19.5.4.xxx. Tested 19.6.xxx (first releases), work no issue known. But I think latest now is 19.7 or higher that we never tested.
Well… then let’s start connecting the serial pins to the TTL adapter to see if it responds and tells me what version it is.
From the item number I think it could be a 19.52 … then the discussion of the firmware update opens that will involve Harmony or other devilry.
It’s not that you have any reference to a magical exe that does its due without having to install a full development system.