Closed Tipetofficial closed 1 month ago
This is interesting, since the excepted and read-out values match, the only way for the radio presence check to fail is if the method LR11x0::getVersion
fails itself. There's probably some subtle difference between LR1110 (which I used to write the LR11x0 driver) and the LR1121 in that regard that is causing this method to fail. Unfortunately I'm away from most of my hardware at the moment, so this will take a couple of days for me to look into.
@Tipetofficial I went through the log once more and noticed that a command to read WiFi scanning formware version is being called. For LR1121 that will always fail, since it does not have that functionality. A check to fix this was added in 87fac1797e8e8ef2a8c6cffb722e4212c3050a19, but was not released yet. Could you please try this again with the latest master?
@jgromes Thank you for the fast answer, the master fixed this problem but now I get the -707 error. I am using a TCXO and added
radio.setTCXO(2.4);
because the TCXO I use need at least 1.7V rather that the default 1.6V but the error stays the same.
You have to pass the TCXO voltage as an argument to the begin method, otherwise it will fail before it has a chance to initialize.
Thank you. With your help I was able to fix the issue.
I am using the LR1121 on an own PCB with an ESP32-S3-WROOM-1U and I keep getting the code -2 for a bad SPI-Interface when using the LR11x0_Firmware_Update. I checked my wiring (see schematic) and followed the Non-standard SPI setup as u can see in the code below.
As displayed in the basic debug output the red value and the expected value are the same, but it still fails.
I would highly appreciate any hints to how I could resolve this issue.
Schematic
Schematic_black.pdf
Code that fails
SPI Debug Output
Basic Debug Output
Output Logic Analyser