rns.recipes

I asked this to the helpful people of Reticulum in practice Matrix channel but even with a lot of back and forward I still couldn't manage to make them work. You can flash them eventually if you just spam the command 15 times, but trying to pair it with bluetooth or use it through a serial connection then causes the Rnode basically bricks itself and no long responds to serial commands through rnodeconf

The only major discovery we managed to find was that flashing it once half breaks it (it'll show up a debug name as the serial name after you first attempt to flash it and attempting to flash afterwards doesn't really do much) and only after reflashing with meshtastic do you actually reset back to how the chip was originally.

This chips are experimental for Rnodes and are otherwise considered very buggy so this may just be a firmware issue that will eventually fix itself

If you have at all gotten this chip to work, please say how you successfully flashed them

I use them, if i remember correctly i had to reset them manually at the last step where it would fail to reset and potentially have to initialize them again afterwards but other than that ive been using them as my main RNodes without issue, i may try reflashing one if i have the chance but they are currently in use

itsme wrote:

I use them, if i remember correctly i had to reset them manually at the last step where it would fail to reset and potentially have to initialize them again afterwards but other than that ive been using them as my main RNodes without issue, i may try reflashing one if i have the chance but they are currently in use

Manually pressing the reset button does get me further all the way through the flashing process instead of getting stuck on the first reset, unfortunately though it seems to have not fixed much, I suspect that my seeed nodes are of a slightly different revision because I also tried with micropython reticulum, which acts completely normally until I try running the example reticulum node, where it then just corrupts and you have to reflash to for anything to happen, but notably in that case that the last thing I see is that python erros trying to configure itself with wifi, so it makes me suspect that whatever I have has a slightly different spec when it comes to lora or wifi which then is causing undefined behavior. That's my best guess after testing for the better part of several hours

I think I did have it working for someone else with pretty much no issues. Not really sure what your specific issue is though

Here's the exact two chips in case it is at all relevant. Looking at other Seeed node's people have gotten they seem to be slightly different but I can't tell if that's a relevant factor

This comes up regularly in channels, and I believe this is because there are two forms of the Wio-SX1262, v1.0 and v1.1 (check the reverse side of the Wio chip, it's printed on the board which version it is). It's likely that you have the v1.0 for XIAO which uses different pins than what is mapped out upstream IIRC, which only considers v1.1.

For v1.0:

CS = 5
RESET = 3
DIO1 = 2
BUSY = 4
RXEN = 6
SCK = 7
MISO = 8
MOSI = 9

If you don't have v1.0, then I'm not sure, sorry!

Okay actually ignore that, I just checked my v1.0 and yours is definitely different, so I don't think it's v1.0.

I can't upload the pictures but on mine it doesn't say V1.0 or V1.1 at all (just says the chip name), so I think I have an entirely different version

Though given what you said, it just sounds like I have to find which pins correspond to what and then edit to the corresponding pins in the build configs. I'll also have to try using the esp without the xiao, since if that has incorrect pin then those incorrect signals may be causing the thing entire thing to brick, would let me isolate the problem to specifically that device. Unfortunately I have assignments due so I'll have to look in to that later next week, thanks anyways.

Update: I feel fucking stupid cause I just realised that I have attaching the lora xiao module wrong this entire time. It's meant to go ontop of the esp32 on the stickout bus thing, not through the pins which I initally assumed and there's no mention of you having to do that (Maybe it's implicit thing I'm not a hardware guy so I didn't realise). Setting it up is still really finicky, but flashing the whole thing with meshtactic and then use rnodeconf one or twice (and having to manually press the reset button half way through as @itsme stated) actually gets it to a functional state where it works as an RNode. (also for some reason it didn't work for me till I turned on interference mode with rnodeconf, not sure what that's about)

I'll send pictures at some point for reference later (so people don't repeat what I did) because I've kept myself awake till 2am after realising I've been setting up the chips wrong the entire time.

Sidenote does anyone know the max txpower for this, I know for the heltic v4 it's 28dbm with the same module but I'm not sure if it's the same here.