-
Notifications
You must be signed in to change notification settings - Fork 12
u-blox nina b #1
Comments
Hi,
Do you mean the board using nRF52x such as Nano 33 BLE / BLE Sense (using nRF52840) or just the uBlox NINA B1/2/3/4 modules (using nRF52832, etc.)?
Great and appreciated, thanks for your offer to help. |
Hi, NINA B302 uses a NRF52840. Just now i got success to add WIFI to NINA B302, but using the PYTHON. But, i am looking for ARDUINO If you make work with 33 BLE SENSE, it will work with NINA B302 ! Thanks! |
That's great. Could you pass the link or any additional info so that I can have a look and save some time researching.
Will try. Thanks, |
Yes But will you try NRF52840 talks with WIFININA, right ? (using Arduino) ? |
Thanks for the links. I'll try to make WiFi running on Nano 33 BLE (nRF52840). Will let you know if it's OK soon. |
This is the best news of today!!!!! And you will be famous :) too I am will write many blogs with ble and wifinina with your credits! |
I really don't like that as being obscure will help have time to do better work. PS:
|
And you will be famous :) too YES, YOU ARE RIGHT! PS: The B302 in Nano 33 BLE, I think, can only run either BLE or WiFi, not both at the same time with the current firmware as there is only 1 radio channel. The better U-Blox NINA W15 can do this simulltaneously BUT DO YOU HAVE ONE WITH W102 ? LOOKS THAT B302 HAS 4MB FLASH! It's great if you, as one of UBlox reps, can ask UBlox to upgra.de the firmware to let both WiFi and BLE running at the same time as in Nano 33 IoT. If this is possible, the work will be much simpler then. BUT THAT FIRMWARE OF MODULE IS NOT OF UBLOX TEAM! Another question is why you don't use Nano 33 Iot which offer both WiFi and BLE (slave) at the same time? UBLOX REPRESENTATIVE ONLY HAVE W102,B302 and B112 and B312 |
I have Nano 33 IoT using U-blox W102. All the libraries relating to WiFiNINA are written for and tested specially on that Nano board.
So strange, at least they have some engineers supporting / developing these firmwares with Espressif (ESP-32 based chip). Otherwise, it'll take much more time for outsiders to do that. It'll take some more research before knowing the time, if and when the work can be done. Hopefully someone will be there much earlier. |
Nano 33 iot uses atmel SAM The challenger is replace the SAM by a NRF52 :) About u-blox, they have proprietary firmware to W1 (for the chips that are not opencpu) |
Hi, After some research, I have these following observations:
IMHO, the suggestion and plan is:
Hope they are correct after so short research time . |
late i will try to make the NRF52 try to talk with W102 (WIFININA) too! But i still testing it with CIRCUIT PYTHON and need to make some blogs |
Pls inform when done. I can port the WiFiNINA libraries to nRF52 boards, but still don't have any board (to be ordered) to test. Hopefully you can help test when the enhancement finished. |
Hi, Thanks!!!! Helps the community! After some research, I have these following observations: The WiFi Tutorial for nRF52840 is not about using B302 to run WiFi, but using external ESP32 as co-processor to run WiFi. Yes, the W102! It's better to use W102, W1x if you'd like to run WiFi as in Nano 33 IoT, instead of using B302, B3x (as in Nano 33 BLE/Sense). yes, i want the W102 The Arduino mbed-based development (for Nano 33 BLE/Sense) is still pre-matured (without the Network, WiFi, etc. support). It'll take some much more time to wait or develop yourself. I never more used the Mbed, but they are making changes on Web page and OS Don't go further with the WiFiNINA port to B302, etc. Yes!!!! Make NRF528XX (Arduino) talks with W102 (WIFININA) Enable the above-mentioned AdaFruit boards to run Ethernet W5x00, ENC28J60, LAN8742A, etc. Will buy some boards to test. that is a good idea!!! It will make NRF52 for example, a NRF52 MESH reach WAN :) Enhance Arduino mbed-based development (for Nano 33 BLE/Sense) to add WiFi/Ethernet Network support. Some long-term plan for fun if not available then. Correct! |
Try now make a NRF52 works with W102 :) |
@khoih-prog |
Pls wait for v1.5.1 in an hour. Don't use v1.5.0 for this purrpose. |
You can see your contribution has been noted and appreciated in README Waiting for the test result to continue to update the following libs to support nRF52 boards:
|
i got 3 minutes now (i am in classroom, and compiles)! Tomorrow i will test after change MAP pins! Help me to understand the #defines #define NINA_GPIO0 (26u) //26 #define SPIWIFI_SS 24 //PIN_SPI1_SS //24 in Circuit Python i choose those pins (left side), P0.X, in the NRF52 side, not clear to me wich are the simular in your Arduino #defines I guess that should be #define NINA_RESETN (15u) #define SPIWIFI_SS 13 //PIN_SPI1_SS //13 What is the function of PS: You can see your contribution has been noted and appreciated in README! PS: and where in the source code i define that i am using of these ( defined(NRF52840_FEATHER) || defined(NRF52832_FEATHER) || defined(NRF52_SERIES) || defined(ARDUINO_NRF52_ADAFRUIT) ) |
I have to check more to see how the pin is used. You can see how the pins are used in Nano 33 IoT as follows: and the corresponding #defines //NINA pin to control // SPI1 pins for SPI bus communications ??? <==== NiNA W102 GIPIO0 <--> pin 26 of SAMD21 // SPI1 pins for SPI bus communications
You don't need to do anything unless you'd like to print board information depending on the board you're using. The compiler will take care of that. Just select the correct board in Arduino Board Manager. Have a look at the example WiFiWebServer If you like to print board type, use
|
For B302 <--> nRF52840, I think you can connect as follows: ??? <==== NiNA B302 GIPIO0 <--> pin ?? of nRF52840 // SPI1 pins for SPI bus communications |
I did all the Setup, still nothing running! No DEBUG message showing what is going on! Maybe the problem is that GIPIO0 on W102, strange that i didnt use this GPIO on CIRCUIT PYTHON... |
Which boards are you testing now? Can you send the actual pin-to-pin connections as well as any terminal debugging msg. And how did you change in WiFiNINA_Pinout_Generic.h to match new boards? Adafruit Feather nRF52840 Express? W102 or B302? BTW, can you swap the MOSI and MISO pins. By the times, I'll have a look at GPIO0 to see what its actual function. |
Hi
Left side, NINA B302 (NRF52840), right side, NINA W102 (ESP32)
Tomorrow i send you their connection used on CIRCUIT PYTHON SOFTWARE!
Please, put messages debug!
I created a FEATHER variant, the NINA_B302_Ublox, works nice with gpio access to arduino!
I had already swap the miso mosi
Debug messages is a good begin!
I am in the bed :)
Enviado do meu iPhone
Em 23 de abr de 2020, às 00:07, Khoi Hoang <notifications@github.com<mailto:notifications@github.com>> escreveu:
Which boards are you testing now? Can you send the actual pin-to-pin connections as well as any terminal debugging msg.
Adafruit Feather nRF52840 Express? W102 or B302?
I can put more debugging msgs to see what's happening and put on master and let you know when.
BTW, can you swap the MOSI and MISO pins.
By the times, I'll have a look at GPIO0 to see what its actual function.
|
The Nano 33 IoT schematics shows how W102 is connected Pls discard the previous pin-to-pin connections and use the following: Note: NiNA W102 GIPIO0 pulled low during startup for download Pin 27 of W102 <==== NiNA W102 GIPIO0 <--> pin PA27 of SAMD21 // SPI1 pins for SPI bus communications The GPIO0 function in W102
Another question is if you updated the firmware of W102 to latest v1.3.0 ? |
Already post in Master the debugging version. I'm afraid that the B302 firmware you have with the board is not suitable for running the normal program as normal nRF52840. Do you have an Adafruit Feather nRF52840 Express (instead of B302) to test to eliminate? I'm not sure the SPI bus on B302 board is working OK as expected (you can check MISO and MOSI signals to see). The Adafruit assignments for MOSI, MISO and CS/SS are also different (in variants/xxx/variant.cpp) for every board, depending which we choose when compile :
The problem is I don't have any nRF52 board here to test, as I just ordered some from Adafruit today and it'll take longer time to arrive in this nCovid condition. Just try out best now. The actual pin assignment will be:
Change the pin in WiFiNINA_Pinout_Generic.h according to actual connection between W102 and nRF52 to:
|
Hi, |
HI @khoih-prog just wake up! I will do the changes and tests in 2,5 hours! Going to the VIRTUAL classroom! Thanks!!!! |
Hi @tcpipchip I'm temporarily closing this issue now. Pls post on private repository |
#### New in v1.5.1 1. Add support to nRF52 boards, such as AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, Clue nRF52840, Nordic nRF52840DK, Particle Xenon, etc. Raytac MDBT50Q-RX Dongle is not supported. 2. Add support to ***NINA_B302_ublox running as nRF52840***. Thanks to great work of [Miguel Alexandre Wisintainer](https://github.com/tcpipchip) for initiating, inspriring, working with, developing, debugging and testing. See [u-blox nina b](#1)
#### New in v1.5.1 1. Add support to nRF52 boards, such as AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, Clue nRF52840, Nordic nRF52840DK, Particle Xenon, etc. Raytac MDBT50Q-RX Dongle is not supported. 2. Add support to ***NINA_B302_ublox running as nRF52840***. Thanks to great work of [Miguel Alexandre Wisintainer](https://github.com/tcpipchip) for initiating, inspriring, working with, developing, debugging and testing. See [u-blox nina b](#1)
#### New in v1.5.1 1. Add support to nRF52 boards, such as AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, Clue nRF52840, Nordic nRF52840DK, Particle Xenon, etc. Raytac MDBT50Q-RX Dongle is not supported. 2. Add support to ***NINA_B302_ublox running as nRF52840***. Thanks to great work of [Miguel Alexandre Wisintainer](https://github.com/tcpipchip) for initiating, inspriring, working with, developing, debugging and testing. See [u-blox nina b](#1)
#### New in v1.5.1 1. Add support to nRF52 boards, such as AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, Clue nRF52840, Nordic nRF52840DK, Particle Xenon, etc. Raytac MDBT50Q-RX Dongle is not supported. 2. Add support to ***NINA_B302_ublox running as nRF52840***. Thanks to great work of [Miguel Alexandre Wisintainer](https://github.com/tcpipchip) for initiating, inspriring, working with, developing, debugging and testing. See [u-blox nina b](#1)
#### New in v1.5.1 1. Add support to nRF52 boards, such as AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, Clue nRF52840, Nordic nRF52840DK, Particle Xenon, etc. Raytac MDBT50Q-RX Dongle is not supported. 2. Add support to ***NINA_B302_ublox running as nRF52840***. Thanks to great work of [Miguel Alexandre Wisintainer](https://github.com/tcpipchip) for initiating, inspriring, working with, developing, debugging and testing. See [u-blox nina b](#1)
Finally, thanks to the collaboration of @tcpipchip, the nRF52 (even B302's nRF52840) boards can run WiFiNINA W102 from version v1.5.1-final |
A success story how to use ESP32-based WiFiNINA with Teensy 4.0 WiFiNINA_Generic-Library-for-WiFiNINA-modules-to-support-Teensy-and-more-boards
SPISClass SPIS(VSPI_HOST, 1, 23, 19, 18, 5, 33);
|
@khoih-prog
Hi
Is it possible to port to NRF52 chips ? I can test here!
Are the routines HIGH level ? (hardware gpios access)
Thanks!
The text was updated successfully, but these errors were encountered: