-
Notifications
You must be signed in to change notification settings - Fork 10
WiFiManager_NINA_Lite-->RP2040_WiFiNINA Example does not work #15
Comments
Hi, I'm so sorry to see you getting new problem. I currently have no idea of what's happening with your new board because I have no issue with my current I suggest you try these 2 basic examples in LittleFS_Mbed_RP2040 library, which this library is based on : Please modify the code to have better debugging as follows
then post the debug terminal so that I can spot anything abnormal. I'm afraid that this is the board manufacturing issue similar to this [FACTORY SOLDER BUG] Nano Connect RP2040 Bad Solder for USB Mini Connector - possibly more? Good Luck and be patient exploring, |
I've tested again and again my board here and be sure the issue is not caused by the ArduinoCore-mbed v2.4.1, the LittleFS_Mbed_RP2040 v1.0.1 or WiFiManager_NINA_Lite v1.4.0. Be sure to check if you're using the same core /library version LittleFS_Test on Nano RP2040 Connect
LittleFS_Counting on Nano RP2040 Connect
RP2040_WiFiNINA on MBED NANO_RP2040_CONNECTAfter reformat => start over
Run normally
|
Thank you for your effort. First of all, having installed the As the official Arduino Install instructions for the And I think that is the main problem here that you base your LittleFS (and potentially also your WiFiManager_NINA_Lite) library to another board-type. Can you please make your trial with the Thank you. Here three screenshots showing what libraries I exactly installed. They are incompatible ! You can see, the Example LittleFS is INCOMPATBIBLE ! I use the newest Arduino IDE (hourly build from yesterday) - but also the official release Arduino IDE 1.8.16 does not work. Please, for your tests, make sure you also update the IDE. Again, with a brand new (and I tried with 5 out-of-the-box new boards, they all show the same Error) And I get the following Error:
The selected Board is the Arduino Mbed OS Nano Boards-->Arduino Nano RP2040 Connect |
Moreover, I found out that a board that I purchased 2 month ago works fine. But I received 8 boards that all are completely faulty as they seem to have a different Flash-memory Chip on them. I am completely clueless what is going on. This is just so frustrating. The old board works - the same SW on the new boards does not.. Old board (works): New board (does not work): I mean, look at the ugly quality the official Arduino Store sells. One chip is even abrased not so see its origin possibly. I am trying to return the faulty 8 boards. This is so bad. |
Thank you for updating the LittleFS library - I saw that there is an update today. Now the LittleFS library is compatible with the In addition, I installed the newest Firmware on my newly purchased boards. I installed version But unfortunately, running the... ... default Example --> LittleFS_Mbed_RP2040 --> LittleFS_Counting still lead to the exact same Error on these new RP2040 Connect boards:
or respectively, again, lead to the exact same Error on these new RP2040 Connect boards:
So same behaviour ! I contacted support from Arduino to ask about a return of my newly purchased boards. Or do you see anything related to your libraries ? |
The new release is just a cosmetic change to remove the complaint as well the So we can narrow down the current issue only happens to the so-called new boards, but I'm sorry I currently have no such a board to test, verify and investigate to know what's going wrong. I also don't know now if I order another new board, I can get the same new boards or not. Hopefully this issue happens only to some batches of the boards, or the boards you got are counterfeit ones, just by the unprofessional looks of those boards (colour, parts, ugliness, non-gold-plated, what-else, etc.).
IMHO, this is the correct way to do, but it's also beneficial to post an issue on the ArduinoCore-mbed core issue, so that it can be solved finally after the root cause found. I'm afraid with my time, knowledge, equipments, info I have, I can't do anything to help. It's also good if you can keep 1 new board to test later.
I really don't know now as I don't have that kind of new board to test and investigate. Keep us posted, Good Luck, |
I'm using the exactly-the-same
I believe this issue is wide-spreading now as more people experiencing the same problem, such as just reported here |
Yep, I saw - the bug-report on the Arduino Forum is also from me ;) Arduino official store tells me that these two libraries are not official Arduino libraries but 3rd party. And that they cannot help me. And that I should go with the WiFiNINA official library. But I really appreciate your work and I need a library that does Access-Points (potentially captive portal). And I am sure there must be a solution to this problem. I am pretty sure the manufacturing process at Arduino did exchange a component (my suggestion is the Flash-memory) and this lead to the issue with your libraries. If more people have the same issue - maybe it is time that you connect with Arduino as well to ask about the changes in Hardware that lead to the faulty behaviour of your libraries. |
You can verify and try the WiFiNINA_Generic and see it's working the same way as orignal WiFiNINA library. The issue here is the Anyway, I'm closing the issue now as this is not proven that the bug of this library. I will continue investigating and reopen when the time comes.
I don't think I'll do this as it's the responsibility of the manufacturers to investigate when they're selling batches having incompatibility and different functionalities from other batches. Good Luck |
As @pennam found out, the problem can be solved by going back to the mbed-core version 2.3.1 (instead of 2.4.1). |
Good news. So something introduced in the latest core created the incompatibility of the new batches' flash. |
I bought another
Arduino Nano RP2040 Connect
board.I installed the
Arduino Mbed OS Nano Boards (v2.4.1)
and I installed the libraryWiFiManager_NINA_Lite (v1.4.0)
Then running the default Example WiFiManager_NINA_Lite-->RP2040_WiFiNINA
But at start, the following error occurs:
Any idea why an out-of-the-box Nano RP2040 Connect board would bring this error ?
What do I have to do to make the default Example work ?
The text was updated successfully, but these errors were encountered: