Added support for the nibble zero connect#1194
Conversation
ViezeVingertjes
force-pushed
the
nibble_zero_connect
branch
from
bcee346 to
20cfab6
Compare
ViezeVingertjes
force-pushed
the
nibble_zero_connect
branch
from
20cfab6 to
a2388a1
Compare
ViezeVingertjes
force-pushed
the
nibble_zero_connect
branch
from
a2388a1 to
35d45e4
Compare
|
Confirmed working! 🙏 |
Great! If you are actually using it with the flipper zero, then it might be cool to look into the SecureChat firmware. It needs a small modification to run over the TX/RX pins instead of USB Serial, but then you could also send messages etc from the Flipper. ^^ |
| -D HAS_NEOPIXEL | ||
| -D NEOPIXEL_COUNT=1 | ||
| -D NEOPIXEL_DATA=17 | ||
| -D NEOPIXEL_TYPE=(NEO_GRB+NEO_KHZ800) |
There was a problem hiding this comment.
I had to comment this out - it didnt like the ( / ) syntax
There was a problem hiding this comment.
What / are you refering to exactly? Maybe im overlooking it, but i dont see it haha...
Builds and flashes fine as-is for me (on Windows though)
There was a problem hiding this comment.
Sorry haha the backtick formatting may have been confusing. The problematic chracters for me are the open parens and close parens
There was a problem hiding this comment.
Check; i did see the same on Ubuntu. On Windows it did not care about it. Will fix.
|
I'm not using it with a flipper zero though. Just wanted to separately compile the latest MeshCore fw for the nibble zero in the wifi variant, which nugget.dev seems to not offer. |
|
Although everything seems to work, and I can see client and router adverts in the rx logs, I seemingly cannot discover any other contacts. Don't know if its an issue with these changes though as these are just the hardware definition stuffs, but figured I'd mention it in case anyone else has seen this on the nibble zero and knows a fix 😊 |
I will test it once more when i get home, pretty sure i have seen that working, but wont hurt to confirm. [Edit] |
ViezeVingertjes
force-pushed
the
nibble_zero_connect
branch
2 times, most recently
from
1ee030d to
c200c2c
Compare
|
Hey, thanks for the PR :) I know it's been a good 4 months since this was opened, but is this board purchasable anywhere? I'm thinking it should be left as a custom board that isn't automatically built, as our build/release flow already takes over an hour now, and if the board is only used by several people it would be best for us to avoid the increased build time. If you still want this added in, I'd probably suggest putting an underscore |
| radio.setCodingRate(cr); | ||
| } | ||
|
|
||
| void radio_set_tx_power(uint8_t dbm) { |
There was a problem hiding this comment.
I believe this now needs to be int8_t instead of uint8_t.
| bool radio_init(); | ||
| uint32_t radio_get_rng_seed(); | ||
| void radio_set_params(float freq, float bw, uint8_t sf, uint8_t cr); | ||
| void radio_set_tx_power(uint8_t dbm); |
There was a problem hiding this comment.
I believe this now needs to be int8_t instead of uint8_t.
I'm the board dev! Currently can be bought from retia.io, so far there are 250+ of them, plus another 100 in production. It would be nice to be able to flash from the main site, but I understand. Making it easy to compile via our own github action would probably be my workaround. |
|
I'm trying to flash my nibble to meshcore. Is anyone still working on this? |
ViezeVingertjes
force-pushed
the
nibble_zero_connect
branch
from
c200c2c to
3b88783
Compare
5 participants
Uh oh!
There was an error while loading. Please reload this page.