WiFiClass::status() doesn't return WL_NO_SHIELD when shield is missing about wifi101 HOT 9 CLOSED

I experience the same issue on an arduino mega R3 2560
I am waiting for the wifi101 shield to arrive and have been coding in anticipation.
With a bare board, status() fails.

No return from m2m_wifi_init(&param) in m2m_wifi.c
Last point of failure tracked to nm_read_reg(M2M_WAIT_FOR_HOST_REG) in nmasic.c (No return)
Naturally it should never have got this far into the initialise sequence.
As andreimatei above I expect that the nm_drv_init routine should return with an error much earlier!
David

from wifi101.

@drp0 I've submitted a patch in #23 to resolve this. Would you be able to try it out?

from wifi101.

Yes,
I tried clicking on #23 , then (541b5be#diff-57b01d2f3e2fef366d5fd9f83065c011L53).
This link opens part way into src/driver/source/nmasic.c
I opened the view source, and replaced a copy of nmasic.c with the linked code-
No return from WiFi.status()

Let me know if I have dived down the wrong rabbit hole,
David

from wifi101.

Test 2-
I replaced
#define TIMEOUT (0xfffffffful)
with
#define TIMEOUT (0x2000ul)
Using the CheckWifi101FirmwareVersion sketch, the WIFI.status() routine returned in 15.22 seconds with NOT PRESENT (WL_NO_SHIELD)

David

from wifi101.

@drp0 great, thanks for trying. We'll have to wait for someone to review and merge #23.

from wifi101.

No problem,
I also tried #define TIMEOUT (2000)
as it seemed probable that the timeout was a milli-second value
The routine returned in just over 3 seconds.

from wifi101.

I regret to report that this problem is back in library versions 0.14 and up (2017.03.22). I tried with bare Mega 2560 and Pro Mini boards and reproduced same result as original post.
(Confirmed fixed in 0.9 thru 0.13 though.)

from wifi101.

@z-l-p I've made pull request #205 to resolve this, it would be great to get your feedback on it.

from wifi101.

Thanks! sandeepmistry's change works fine with my ATWINC1500 board (quickly returns correct values for present / !present). I can't do more in-depth testing because my board is now installed in an inaccessible place! Sorry.

from wifi101.