Lora-net / sx1302_hal

SX1302/SX1303 Hardware Abstraction Layer and Tools (packet forwarder...)
Other
219 stars 272 forks source link

Failed to set SX1250_0 in STANDBY_RC mode #61

Closed shawaj closed 1 year ago

shawaj commented 2 years ago

I am getting this error:

root@f986d0ed3f2c:/opt/iotloragateway/packet_forwarder# sx1302/util_chip_id/chip_id -d /dev/spidev1.2
CoreCell reset through GPIO22...
Opening SPI communication interface
Note: chip version is 0x12 (v1.2)
ERROR: Failed to set SX1250_0 in STANDBY_RC mode
ERROR: failed to setup radio 0
ERROR: failed to start the gateway

And the concentrator gets very hot, very quickly.

Any idea of the issue?

kmuster-semtech commented 2 years ago

I have seen that error when there is an issue with the hardware setup. For general troubleshooting, make sure the particular concentrator board supports SPI and not USB communication and that the SX1250 transceiver is receiving 3.3V supply power. Check that you are able to run "sx1302/bin/test_loragw_com -d /dev/spidev1.2" and "sx1302/bin/test_loragw_com_1250 -d /dev/spidev1.2" and receive a stream of outputs saying "no error." After checking that, can you also share the concentrator PCB number and any mounted power jumpers?

cstratton commented 2 years ago

And the concentrator gets very hot, very quickly

That would indicate a hardware issue. Either mistaken connection of the concentrator card to the host system (which card, in which system, connected how?) or else past permanent damage from miswiring, ESD, etc.

gswebspace commented 2 years ago

Noticed SX1250_0 in STANDBY_RC mod in my logs too, but not sure if it is due to the same reason. Opened #67 to track it.

wong-hao commented 2 years ago

I have seen that error when there is an issue with the hardware setup. For general troubleshooting, make sure the particular concentrator board supports SPI and not USB communication and that the SX1250 transceiver is receiving 3.3V supply power. Check that you are able to run "sx1302/bin/test_loragw_com -d /dev/spidev1.2" and "sx1302/bin/test_loragw_com_1250 -d /dev/spidev1.2" and receive a stream of outputs saying "no error." After checking that, can you also share the concentrator PCB number and any mounted power jumpers?

I'm sure it's not a personal problem because people who use different brands of hardware and different versions of library will all encounter this problem. Please refer to this issue

cstratton commented 2 years ago

I'm sure it's not a personal problem because people who use different brands of hardware and different versions of library will all encounter this problem.

No, while the error message is commonly seen, the cause is very much a "personal" one unique to a given setup or hardware problem.

Most commonly, that would be not having scripts configured to use the GPIO that is actually wired to the concentrator reset in your particular configuration. Other causes have included the one earlier in this thread where someone has a damaged concentrator chip, and one at your link where someone is trying to do an unsupported "hot change" of configuration without reset.

LittleFool1022 commented 2 years ago

I had the same problem, on Raspberry Pi 3B and SX1302 gateway module, the problem was failed to set sx1250_0 STANDBY_RC mode. However, I can get the chip version by pulling the CSN of the SX1302 and the SPI chip selection control pin by pulling it high and then pulling it low, but the above problems are still impossible.

ahmed560 commented 2 years ago

I had the same problem and I have tested the reset_lgw.sh and it works and i have changed the sx_1302_reset

ahmed560 commented 2 years ago

but the problem isn't resolved

smtc-bot commented 1 year ago

Thank you for your inquiry.

Customers are encouraged to submit technical questions via our dedicated support portal at https://semtech.force.com/ldp/ldp_support.

We invite all users to visit the LoRa Developer Portal Forum at https://forum.lora-developers.semtech.com and to join the thriving LoRa development community!

ABHITHLALC commented 11 months ago

Did anyone solved this problem? I am having the same problem. I am using raspberry pi 3b+ with sx1302 lorawan hat