<![CDATA[PINE64 - P64-LTS / SOPINE Projects, Ideas and Tutorials]]> https://forum.pine64.org/ Thu, 16 Apr 2026 03:20:14 +0000 MyBB <![CDATA[Hello from Ukraine]]> https://forum.pine64.org/showthread.php?tid=19945 Fri, 08 Aug 2025 23:55:48 +0000 SolderJackDIY]]> https://forum.pine64.org/showthread.php?tid=19945 <![CDATA[which emulator is it possible to install on Pine64 Lts]]> https://forum.pine64.org/showthread.php?tid=17338 Sun, 11 Sep 2022 18:28:27 +0000 Paulo Capel]]> https://forum.pine64.org/showthread.php?tid=17338

É possível instalar algo semelhante ao "Retropie"? Instalei o Armbian e executei o . mas o que fazer com este pinho 64lts ?]]>

É possível instalar algo semelhante ao "Retropie"? Instalei o Armbian e executei o . mas o que fazer com este pinho 64lts ?]]> <![CDATA[really want to use lvds flat screen displays on Pine64/Sopine]]> https://forum.pine64.org/showthread.php?tid=17245 Mon, 29 Aug 2022 19:02:26 +0000 jjello-53]]> https://forum.pine64.org/showthread.php?tid=17245
I bought one of the Pine 7 inch mipi-dsi displays just to get an idea of how a flat screen would be enabled in Armbian. It works fine, but I can't glean much information from the configuration that gives me any hints about how to make changes to switch to lvds display output. They have a device tree overlay for the dsi screen, but it mostly deals with power/backlight/etc. There's nothing in the .dtob file about dsi pre-se. I also can't find anything about how the display resolution of communicated to the software. It looks to me like the things I want to change are baked in to the driver and not supplied by device tree information, which was my previous experience with using Raspberry Pi hardware. Any help would be greatly appreciated.]]>
I bought one of the Pine 7 inch mipi-dsi displays just to get an idea of how a flat screen would be enabled in Armbian. It works fine, but I can't glean much information from the configuration that gives me any hints about how to make changes to switch to lvds display output. They have a device tree overlay for the dsi screen, but it mostly deals with power/backlight/etc. There's nothing in the .dtob file about dsi pre-se. I also can't find anything about how the display resolution of communicated to the software. It looks to me like the things I want to change are baked in to the driver and not supplied by device tree information, which was my previous experience with using Raspberry Pi hardware. Any help would be greatly appreciated.]]> <![CDATA[Pinedio Project: Notes Sharing/Log]]> https://forum.pine64.org/showthread.php?tid=13682 Thu, 22 Apr 2021 21:15:01 +0000 RTP]]> https://forum.pine64.org/showthread.php?tid=13682 https://github.com/righttoprivacy/rak_co...or_gateway sets the Pinedio gateway devices (concentrator/gps) listed below. (Leaving notes for context/reference).
See lower page for example image with fork installed.

Hello! Smile

Post to share things that are found helpful/work, progress/Notes along Pinedio Gateway/modules/Kit.

(Pinedio uses Rak Wireless "LoRa"/Mesh related/compatible hardware).

Pinedio's Wiki has been started and can be found here: https://wiki.pine64.org/wiki/Pinedio

Thread for sharing some found to be working notes that can be edited out/posted to WiKi as wanted.

The Pine64 Gateway's underlying hardware runs on the A64-LTS (this looked the best place to post this - feel free to move).

Working SOPINE/Patched Armbian image can be found at:

*** Removed one of the images as users reported ethernet was not working- my working image is below this:

https://mega.nz/file/Wd5CGRhB#spBqSQrhLm...HopFs4Ho9o (576MB) (Uploaded this copy after patching it)

sx1302_hal compiles/installs on Armbian without issue.

EXPERIMENT: SET UP RAK_COMMON_FOR_GATEWAY (ORIGINALLY FOR RPI: SOME MOD REQUIRED - NOT QUITE FINISHED):

Run sudo armbian-config. Enter System to enable SPI/UART for sx1302/rak/GPS.

Then Add The Following Line To /boot/armbianEnv.txt:

Code:
param_spidev_spi_bus=0

***After this reboot Gateway***

NEXT:

Code:
clone https://github.com/RAKWireless/rak_common_for_gateway.git

Then:

Code:
cd rak_common_for_gateway

In rak/install.sh comment out the line (add hash mark in front of)

Code:
# systemctl stop hciuart
(or you will receive errors aborting your install)

Run the install.sh script in the main directory.

Select: 7 : rak2287/GPS without LTE

We can use gateway-config command to make some device location changes (if needed).

Before entering gateway-config -> edit packet forwarder, we need to grab our mac address based Gateway ID for all LoRa networks. To grab this Gateway ID run:

Code:
gateway-version

It will print out your Gateway ID (based on your unique mac address).

Inside gateway-config make the following changes:

Code:
{
    "SX130x_conf": {
        "com_type": "SPI",
        "com_path": "/dev/spidev0.0",
        "lorawan_public": true,

Set GPS to /dev/ttyS2 and grep -i reset to find reset pin swapping 17 with 71.

GPS section of the packet forwarding should look as below

Code:
/* GPS configuration */
        "gps_tty_path": "/dev/ttyS2",
        /* GPS reference coordinates */

Above GPS, replace the default GatewayID with your gateway ID retrieved from gateway-version (from earlier). The line looks like:
Code:
"gateway_conf": {
        "gateway_ID": "03BD3EFFFF21D2F",

Restart packet forwarder. You may need a reboot.

GPS Related:

If experimenting with The Things Network I discovered Gateway does not appear on the map until the GPS signal is stable. I ran a line towards a window to give it a clear line of sight for GPS. Using a temporary antenna I was able to get a better GPS reception. Immediately after setting up this stable GPS link, the Gateway appears on the map and the PPS counter begins.

journalctl log example (still more to look at):

Code:
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: Opening SPI communication interface
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: Note: chip version is 0x10 (v1.0)
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: using legacy timestamp
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: LoRa Service modem: configuring preamble size to 8 symbols
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: ARB: dual demodulation disabled for all SF
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: found temperature sensor on port 0x39
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: [main] concentrator started, packet can now be received
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: concentrator EUI: 0x00xxxxxxxx (masked)
Apr 22 16:57:19 rak-gateway ttn-gateway[6400]: CoreCell reset through GPIO71...
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: *** Packet Forwarder ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: Version: 2.0.1
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: *** SX1302 HAL library version info ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: Version: 2.0.1;
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Little endian host
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: found configuration file global_conf.json, parsing
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: global_conf.json does contain a JSON object named SX130x_conf, parsing SX1302 parameters
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: antenna_gain 0 dBi
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Configuring legacy timestamp
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: no configuration for SX1261
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: radio 0 enabled (type SX1250), center frequency 904300000, RSSI offset -215.399994, tx enabled 1, single input mode 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: radio 1 enabled (type SX1250), center frequency 905000000, RSSI offset -215.399994, tx enabled 0, single input mode 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8, Explicit header
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: FSK channel 8 disabled
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: gateway MAC address is configured to AAxxxxxxxxxxxx (mac masked)
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: server hostname or IP address is configured to "router.us.thethings.network"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: upstream port is configured to "1700"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: downstream port is configured to "1700"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: downstream keep-alive interval is configured to 10 seconds
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: statistics display interval is configured to 30 seconds
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: upstream PUSH_DATA time-out is configured to 100 ms
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with a valid CRC will be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with a CRC error will NOT be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with no CRC will NOT be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: GPS serial port path is configured to "/dev/ttyS2"
....
Apr 23 03:17:37 rak-gateway ttn-gateway[17110]: # PUSH_DATA datagrams sent: 1 (124 bytes)
Apr 23 03:17:37 rak-gateway ttn-gateway[17110]: # PUSH_DATA acknowledged: 100.00%

[OP actively being edited and may change - will clean up as I go]

(Thanks JF for sharing some hardware/SPI related information especially on GPS as I have not worked with an LTS/A64 board until now)

My thought is to continue looking at what may not yet work, change things along the way until all is functional.

Having some odd things happen where I make a small edit to packet forwarder and it resets to original RPI, leading me to have to re-edit leading to starting of concentrator (as far as can see - will end up testing a node on it coming up and checking more details that might differ between RPI/Pine64- if you have anything helpful to share, thanks).

(For now mainly looking at Gateway and using rak_gateway as a starting point to test hardware and make changes).

If you have anything/thoughts/suggestions to add, related, or unrelated, please do! Smile]]> https://github.com/righttoprivacy/rak_co...or_gateway sets the Pinedio gateway devices (concentrator/gps) listed below. (Leaving notes for context/reference).
See lower page for example image with fork installed.

Hello! Smile

Post to share things that are found helpful/work, progress/Notes along Pinedio Gateway/modules/Kit.

(Pinedio uses Rak Wireless "LoRa"/Mesh related/compatible hardware).

Pinedio's Wiki has been started and can be found here: https://wiki.pine64.org/wiki/Pinedio

Thread for sharing some found to be working notes that can be edited out/posted to WiKi as wanted.

The Pine64 Gateway's underlying hardware runs on the A64-LTS (this looked the best place to post this - feel free to move).

Working SOPINE/Patched Armbian image can be found at:

*** Removed one of the images as users reported ethernet was not working- my working image is below this:

https://mega.nz/file/Wd5CGRhB#spBqSQrhLm...HopFs4Ho9o (576MB) (Uploaded this copy after patching it)

sx1302_hal compiles/installs on Armbian without issue.

EXPERIMENT: SET UP RAK_COMMON_FOR_GATEWAY (ORIGINALLY FOR RPI: SOME MOD REQUIRED - NOT QUITE FINISHED):

Run sudo armbian-config. Enter System to enable SPI/UART for sx1302/rak/GPS.

Then Add The Following Line To /boot/armbianEnv.txt:

Code:
param_spidev_spi_bus=0

***After this reboot Gateway***

NEXT:

Code:
clone https://github.com/RAKWireless/rak_common_for_gateway.git

Then:

Code:
cd rak_common_for_gateway

In rak/install.sh comment out the line (add hash mark in front of)

Code:
# systemctl stop hciuart
(or you will receive errors aborting your install)

Run the install.sh script in the main directory.

Select: 7 : rak2287/GPS without LTE

We can use gateway-config command to make some device location changes (if needed).

Before entering gateway-config -> edit packet forwarder, we need to grab our mac address based Gateway ID for all LoRa networks. To grab this Gateway ID run:

Code:
gateway-version

It will print out your Gateway ID (based on your unique mac address).

Inside gateway-config make the following changes:

Code:
{
    "SX130x_conf": {
        "com_type": "SPI",
        "com_path": "/dev/spidev0.0",
        "lorawan_public": true,

Set GPS to /dev/ttyS2 and grep -i reset to find reset pin swapping 17 with 71.

GPS section of the packet forwarding should look as below

Code:
/* GPS configuration */
        "gps_tty_path": "/dev/ttyS2",
        /* GPS reference coordinates */

Above GPS, replace the default GatewayID with your gateway ID retrieved from gateway-version (from earlier). The line looks like:
Code:
"gateway_conf": {
        "gateway_ID": "03BD3EFFFF21D2F",

Restart packet forwarder. You may need a reboot.

GPS Related:

If experimenting with The Things Network I discovered Gateway does not appear on the map until the GPS signal is stable. I ran a line towards a window to give it a clear line of sight for GPS. Using a temporary antenna I was able to get a better GPS reception. Immediately after setting up this stable GPS link, the Gateway appears on the map and the PPS counter begins.

journalctl log example (still more to look at):

Code:
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: Opening SPI communication interface
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: Note: chip version is 0x10 (v1.0)
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: using legacy timestamp
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: LoRa Service modem: configuring preamble size to 8 symbols
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: ARB: dual demodulation disabled for all SF
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: found temperature sensor on port 0x39
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: [main] concentrator started, packet can now be received
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: concentrator EUI: 0x00xxxxxxxx (masked)
Apr 22 16:57:19 rak-gateway ttn-gateway[6400]: CoreCell reset through GPIO71...
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: *** Packet Forwarder ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: Version: 2.0.1
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: *** SX1302 HAL library version info ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: Version: 2.0.1;
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Little endian host
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: found configuration file global_conf.json, parsing
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: global_conf.json does contain a JSON object named SX130x_conf, parsing SX1302 parameters
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: antenna_gain 0 dBi
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Configuring legacy timestamp
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: no configuration for SX1261
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: radio 0 enabled (type SX1250), center frequency 904300000, RSSI offset -215.399994, tx enabled 1, single input mode 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: radio 1 enabled (type SX1250), center frequency 905000000, RSSI offset -215.399994, tx enabled 0, single input mode 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8, Explicit header
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: FSK channel 8 disabled
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: gateway MAC address is configured to AAxxxxxxxxxxxx (mac masked)
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: server hostname or IP address is configured to "router.us.thethings.network"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: upstream port is configured to "1700"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: downstream port is configured to "1700"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: downstream keep-alive interval is configured to 10 seconds
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: statistics display interval is configured to 30 seconds
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: upstream PUSH_DATA time-out is configured to 100 ms
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with a valid CRC will be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with a CRC error will NOT be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with no CRC will NOT be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: GPS serial port path is configured to "/dev/ttyS2"
....
Apr 23 03:17:37 rak-gateway ttn-gateway[17110]: # PUSH_DATA datagrams sent: 1 (124 bytes)
Apr 23 03:17:37 rak-gateway ttn-gateway[17110]: # PUSH_DATA acknowledged: 100.00%

[OP actively being edited and may change - will clean up as I go]

(Thanks JF for sharing some hardware/SPI related information especially on GPS as I have not worked with an LTS/A64 board until now)

My thought is to continue looking at what may not yet work, change things along the way until all is functional.

Having some odd things happen where I make a small edit to packet forwarder and it resets to original RPI, leading me to have to re-edit leading to starting of concentrator (as far as can see - will end up testing a node on it coming up and checking more details that might differ between RPI/Pine64- if you have anything helpful to share, thanks).

(For now mainly looking at Gateway and using rak_gateway as a starting point to test hardware and make changes).

If you have anything/thoughts/suggestions to add, related, or unrelated, please do! Smile]]> <![CDATA[Baking Pi style Course for Pine64-LTS]]> https://forum.pine64.org/showthread.php?tid=13553 Sun, 04 Apr 2021 17:05:19 +0000 lscdmore]]> https://forum.pine64.org/showthread.php?tid=13553
I recently got the Pine64-LTS board and was interested in delving very low-level into how the board works, how to understand the schematics and how to read the Allwinner64 datasheet. I'm interested in the Allwinner64 since I know it's used in the Pinetab and the Pinephone so my knowledge would be transferable. I saw a course

https://www.cl.cam.ac.uk/projects/raspbe...orials/os/

And it seemed like something I'd like to try with the pine64-lts. I know the chips and the board are different, but some of the things in the tutorial strike me as very possible to do, for example I should definitely be able to create a bootable image and write it to the SD card on the board and then boot into a baremetal program.

I recognize it may be a lot of work to try to find analogues to every section of this tutorial, but I'd like to give it a shot.

The first problem I was trying to figure out is the exact RAM address of the LED lights on the pine64-LTS. On my board, right next to the USB ports and the reset switches there are two LED lights. I wanted to try flashing them on and off with baremetal assembly code just like in the baking Pi tutorial. I'm struggling to relate the hookup of the Allwinner A64 with the schematics in Pine64-lts to spot exactly where this address is located.

If anybody has some hints or resources for doing this kind of reading I would deeply appreciate any links.

Thanks in advance!]]>
I recently got the Pine64-LTS board and was interested in delving very low-level into how the board works, how to understand the schematics and how to read the Allwinner64 datasheet. I'm interested in the Allwinner64 since I know it's used in the Pinetab and the Pinephone so my knowledge would be transferable. I saw a course

https://www.cl.cam.ac.uk/projects/raspbe...orials/os/

And it seemed like something I'd like to try with the pine64-lts. I know the chips and the board are different, but some of the things in the tutorial strike me as very possible to do, for example I should definitely be able to create a bootable image and write it to the SD card on the board and then boot into a baremetal program.

I recognize it may be a lot of work to try to find analogues to every section of this tutorial, but I'd like to give it a shot.

The first problem I was trying to figure out is the exact RAM address of the LED lights on the pine64-LTS. On my board, right next to the USB ports and the reset switches there are two LED lights. I wanted to try flashing them on and off with baremetal assembly code just like in the baking Pi tutorial. I'm struggling to relate the hookup of the Allwinner A64 with the schematics in Pine64-lts to spot exactly where this address is located.

If anybody has some hints or resources for doing this kind of reading I would deeply appreciate any links.

Thanks in advance!]]> <![CDATA[Docker Swarm Cluster with pine64-lts and armbian build]]> https://forum.pine64.org/showthread.php?tid=6724 Wed, 31 Oct 2018 09:35:26 +0000 tmorin]]> https://forum.pine64.org/showthread.php?tid=6724
For those interested you will find below details to setup a Docker Swarm cluster of pine64-lts boards.

All nodes are running with Armbian and the mainline kernel (currently 4.14). In order to boot pine64-lts boards using the Armbian build for pine64so, some additional fixes have to be done. The whole procedure to build a base image for each node of the cluster is available there: https://gitlab.com/tmorin/pine64-image-armbian

Once the base image is built, the cluster can be setup. All steps are described using Ansible playbooks. You will find all the details there: https://gitlab.com/tmorin/pine64-docker-swarm

Finally, I had to built some docker images by my-self for instance keepalived. You will find the source there: https://gitlab.com/tmorin/pine64-docker-images

Best regards]]>
For those interested you will find below details to setup a Docker Swarm cluster of pine64-lts boards.

All nodes are running with Armbian and the mainline kernel (currently 4.14). In order to boot pine64-lts boards using the Armbian build for pine64so, some additional fixes have to be done. The whole procedure to build a base image for each node of the cluster is available there: https://gitlab.com/tmorin/pine64-image-armbian

Once the base image is built, the cluster can be setup. All steps are described using Ansible playbooks. You will find all the details there: https://gitlab.com/tmorin/pine64-docker-swarm

Finally, I had to built some docker images by my-self for instance keepalived. You will find the source there: https://gitlab.com/tmorin/pine64-docker-images

Best regards]]> <![CDATA[Dual cluster with video bridge.]]> https://forum.pine64.org/showthread.php?tid=3171 Tue, 24 Jan 2017 17:33:40 +0000 Omnios]]> https://forum.pine64.org/showthread.php?tid=3171 <![CDATA[SoPine Photo Blog]]> https://forum.pine64.org/showthread.php?tid=2919 Thu, 08 Dec 2016 06:14:04 +0000 MarkHaysHarris777]]> https://forum.pine64.org/showthread.php?tid=2919
.jpg   sopine.jpg (Size: 81.14 KB / Downloads: 1137)

This is the SoPine board running an hdmi version of Android 5.1. I have had this sopine running as my primary play-desk for several weeks now preparing to run a flavor of gentoo linux on it shortly;  boxed in an ABS server box. 

I have powered the board via euler bus and PI filter. I am using an older Samsung monitor for this play-desk so I am using the hdmi-->vga adapter ( provided by the Pine store ) , a logitech keyboard K400r with trackpad, and the OpenHour IR controller for screen | mouse  controls.

Note:  the heatsink covers both the gpu|cpu (A64) and the new RAM chip which is a layered technology containing 2G of RAM on a single chip !  I'm using passive cooling here; however, will have a fan in the ABS case once I get gnu+linux running on the sodimm module. 

All is good.  The only negative at all is that the SD card cannot be swapped out without removing the sodimm module from the mother board.  

Again I'm using machine screws for supports; and the lipo battery from the Pine store;  U.S. only.


.jpg   sopine2.jpg (Size: 90.1 KB / Downloads: 990) ]]>
.jpg   sopine.jpg (Size: 81.14 KB / Downloads: 1137)

This is the SoPine board running an hdmi version of Android 5.1. I have had this sopine running as my primary play-desk for several weeks now preparing to run a flavor of gentoo linux on it shortly;  boxed in an ABS server box. 

I have powered the board via euler bus and PI filter. I am using an older Samsung monitor for this play-desk so I am using the hdmi-->vga adapter ( provided by the Pine store ) , a logitech keyboard K400r with trackpad, and the OpenHour IR controller for screen | mouse  controls.

Note:  the heatsink covers both the gpu|cpu (A64) and the new RAM chip which is a layered technology containing 2G of RAM on a single chip !  I'm using passive cooling here; however, will have a fan in the ABS case once I get gnu+linux running on the sodimm module. 

All is good.  The only negative at all is that the SD card cannot be swapped out without removing the sodimm module from the mother board.  

Again I'm using machine screws for supports; and the lipo battery from the Pine store;  U.S. only.


.jpg   sopine2.jpg (Size: 90.1 KB / Downloads: 990) ]]>