Hi everyone,
I am trying to run meshtasticd on my Pinephone.
Suddenly tough, the received bytes of the SX1262 are all zero, and I never managed to get the standard 0xA2 answer back.
I2C communication works still, which is why I am suspecting that the radio chip is at fault.
Does anybody know what I was doing wrong or how to debug this?
Onto the details, I simply implemented an SPI device driver which translates to I2C such that mestasticd can communicate with it as if the ATTiny bridge isn't there.
The code for the kernel driver and a dmesg trace with debug output can be found here: https://gist.github.com/pectec/ffddf32ae...041bc92bbe
Any help on this is appreciated
Thank you,
Nick
Edit: I managed to damage it, Pine64 says that there isn't going to be a production batch anytime soon.
My only option is DIY at this point (using a [url=https://www.amazon.de/dp/B0CSFG65MS?psc=1&ref=ppx_yo2ov_dt_b_product_details][/url]Waveshare RP2040), which I'll do when I come around to it, so I'll mark this issue as solved.
I am trying to run meshtasticd on my Pinephone.
Suddenly tough, the received bytes of the SX1262 are all zero, and I never managed to get the standard 0xA2 answer back.
I2C communication works still, which is why I am suspecting that the radio chip is at fault.
Does anybody know what I was doing wrong or how to debug this?
Onto the details, I simply implemented an SPI device driver which translates to I2C such that mestasticd can communicate with it as if the ATTiny bridge isn't there.
The code for the kernel driver and a dmesg trace with debug output can be found here: https://gist.github.com/pectec/ffddf32ae...041bc92bbe
Any help on this is appreciated
Thank you,
Nick
Edit: I managed to damage it, Pine64 says that there isn't going to be a production batch anytime soon.
My only option is DIY at this point (using a [url=https://www.amazon.de/dp/B0CSFG65MS?psc=1&ref=ppx_yo2ov_dt_b_product_details][/url]Waveshare RP2040), which I'll do when I come around to it, so I'll mark this issue as solved.