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.

Hi All,

Any ideas to run https://gitee.com/openeuler/rockchip openEuler 22.03 LTS SP3 Firefly-RK3399 on RockPro64.

It seams to be easy, but actually not know how. The boards FireFly and RockPro64 are 99% similar hardware.

https://hackerboards.com/compare/t-chip-...rockpro64/

Br,
Yuriy Gavrilov

I followed the command provided by the website[https://wiki.pine64.org/wiki/PinePhone_P..._Debugging] and ran.

Quote:Opening media device /dev/media0
Enumerating entities
looking up device: 81:8
looking up device: 81:9
looking up device: 81:10
looking up device: 81:2
looking up device: 81:3
looking up device: 81:6
looking up device: 81:7
looking up device: 81:11
looking up device: 81:12
Found 9 entities
Enumerating pads and links
no such entity "imx258 1-001a"
media_parse_setup_link: Unable to parse link

'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]
  ^
Unable to parse link: Invalid argument (22)

Quote:VIDIOC_QUERYCAP: ok

VIDIOC_REQBUFS returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_G_FMT returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned -1 (Broken pipe)

Will Rust Apps run on a 64-bit RISC-V SBC? Like Ox64 BL808 SBC? Let’s find out!

(1) We take a Barebones Rust App (“Hello World!”)

(2) Compile it for QEMU RISC-V Emulator (64-bit)

(3) Run it on QEMU Emulator with Apache NuttX RTOS

(4) Do the same on Ox64 BL808 SBC (via MicroSD)

(5) We’ll discuss the Quirky Workarounds (because NuttX Apps work differently in Kernel Mode vs Flat Mode)

Here's how: Rust Apps on Ox64 BL808 RISC-V SBC and Apache NuttX RTOS

Lup

   

Hello

This time I have basic question:

I use Spacebar program to send and receive messages on my pinephone

but where are these messages stored ?? every single message to separate file
or all messages into one file and can I read it in text editor ??

This presentation explains how we created the Software Emulator for Ox64 BL808 RISC-V SBC, by customising the TinyEMU RISC-V Emulator. Today we run it for Daily Automated Testing of Apache NuttX RTOS for Ox64.

Presentation Slides

I have summarized the simplest privacy office solution for the Pinephone I know. I did not manage to get every detail to work yet, but everything should work in principle. Since all information is available from the Pine64 forum. I invite everybody to take over this instruction, update it and add more features:

https://petergamma.org/a-simple-privacy-...l-sd-card/

Just found this in the news:

www.tomshardware.com/laptops/the-worlds-first-risc-v-laptop-gets-a-big-update-deepcomputing-doubled-the-core-count-increased-clocks-to-2-ghz-and-added-ai-capabilities

Wondering whether Pine64 has already plans for a Pinebook Pro successor based on RISC-V (and without that AI hype)?

A long running concern I've had about the PP is that at some point phone carriers can drop service at any time as has happened previously.

Is the following a solution for not just messaging, but audio calls to others who've loaded the same software?

--------------------------

There is a non-TCP internet project called Reticulum that has some similarities to the low signal messenger Meshtastic, but Reticulum is much more versatile.

One of the newest features includes allowing for VOIP phone calls through Reticulum Meshchat:

https://github.com/liamcottle/reticulum-webchat

Meshchat can make use of standard internet, wifi, and also the LORA Radio Nodes commonly used for Meshtastic.

PinePhone has a back plate accessory that comes with a built in LORA Radio Node:

https://pine64.com/product/pinephone-pin...d-on-case/

Can this provide another use case for the back plate accessory?

It theoretically solves for the cumbersome LilyGo T-Beam Radio Node that needs to be connected via USB chord to droid phones for similar mesh networks.

How difficult is it to code Reticulum-Meshchat for PinePhone (preferably Arch Phosh for personal testing)?

Note: I don't know Python and lack the free time to learn to attempt this on my own.

We ported Apache NuttX RTOS to PINE64’s Ox64 BL808 64-bit Single-Board Computer. And we created an Emulator for Ox64 SBC that runs in the Web Browser, thanks to TinyEMU RISC-V Emulator. Today we run Daily Automated Testing of NuttX on the Ox64 Emulator.

In this presentation we explain how we used the Ox64 Emulator in our experiments with WebAssembly and NuttX: (1) Testing the TCC RISC-V Compiler in WebAssembly (2) Porting the QuickJS JavaScript Engine to NuttX (3) Creating a Drag-n-Drop App Builder for NuttX.

Presentation Slides