I just recently noticed that after the Raspberry Pi has attracted a lot of attention in the programming circle, smart compatriots have already secretly made a bunch of xx pie. Originally, they were not interested in orange pie, apple pie, potato pie and banana pie. However, due to the recent exaggerated secondary market prices and supply cuts of the Raspberry Pi, I finally chose the Potato Pi, which is relatively affordable and claims to have almost perfect peripherals that rival the Raspberry Pi 3B. Compared with Xianyu 3B second-hand boards that dare to ask for 500 in batches, it is better to choose a normal Alternative.
Today I removed the Jumbospot from the rusty Raspberry Pi 3B and put it on the potato pie. After a survey, I chose the raspbian debian 10 system with the self-compiled MMDVM. Let’s record the know-how.
My jumboSpot was bought from AliExpress in the early years. Its full name is YAOGREENHAM jumbospot V1.3. Its initial pins are to match the Raspberry Pi 3B. Therefore, observing the pins used by JumboSpot on 3B, it is inferred that uart/i2c/pwm-e needs to be opened from Le Potato.
#Potatopie peripherals related articles: https://hub.libre.computer/t/libre-computer-wiring-tool/40
How to find existing pin overlay: sudo ldto list
serial port enable: sudo ldto enable uart-a #Then you can see ttyAML6 appear. If that doesn't work, uarta can also be used.
Open pwm-e: sudo ldto enable pwm-e
i2c enable: sudo ldto enable i2c-b
sudo ldto enable i2c-ao
It is recommended to have a temporary continuous coverage (it can be reset, it doesn't matter, it's just that you don't need to do it again when you start it next time)
Note that the path of the uart-a serial port in Le Potato is /dev/ttyAML6.
If you are confused, you can search for the specific datasheet description of the headers of this board.
Make sure that after opening it, go directly to the 4 MMDVM backend key repos and 1 Dashboard (not that important).
sudo git clone https://github.com/g4klx/MMDVMHost.git
sudo git clone https://github.com/g4klx/MMDVMCal.git
#DMR related, like I use YSF, it doesn’t need to be compiled for the time being. But I suspect D-Star may also have something to do with it.
sudo git clone https://github.com/g4klx/DMRGateway.git
#YSF is just what I need, use DMR D-Star or the like, no need to compile, it is irrelevant.
sudo git clone https://github.com/g4klx/YSFClients.git
The terrible g4klx boss...
#Dashboard, it is said that this latest and low-level data interaction is the most efficient. It is a good thing not to make the board too hot.
sudo git https://github.com/dg9vh/MMDVMHost-Websocketboard
The overall compilation order can be like this, top to bottom.
It should be noted that the development boards of other brands use MMDVMHost to compile and select Makefile. Do not choose those with Pi suffix, otherwise at this point, the error of no Hareware info in /proc/cpuinfo due to the dependent library wiringPi should be insurmountable.
When sudo /usr/local/bin/MMDVMCal 115200 /dev/ttyAML6 succeeds, it is actually 50%+ successful
After everything is done, the usual startup sequence is to start with the Gateways first, then MMDVMHost, and then start the Dashboard-related programs.
=============
There are still some specific compilation details. The following is a master's operation for reference in getting this done.
Feasibility of the complete process on a Le Potato: MMDVMHost on a Le Potato – N2VDY: Amateur Radio
自编译MMDVM: Compilation of an MMDVMHost from G4KLX, independent of Pi-Star. – G4NAB
YSF: Manually compile and install MMDVM - Zhihu
For the sake of data transmission speed, in fact, this mainly refers to the logfile, specifically setting up a ram drive: https://linuxhint.com/setting-up-ram-disk-raspberry-pi/ . I was lazy and skipped this, maybe it was People have good habits.
Okay, buyer show time:
