Power & Source of Big Ideas

Armbian Bionic or Stretch for T3/T3+/M3/Fire3

Moderators: chensy, FATechsupport

+ kernel 4.14.39
+ 2GB memory support
+ ethermet works
+ wlan works
+ desktop works
+ mali works
+ cpu scaling works
+ docker support

- eMMC install fails (T3+), BT does not work yet
- power off reboots the board

Images
https://www.armbian.com/download/?tx_soc=s5p-6818
Nice ! :D

Maybe we'll get somewhere with this !

Thanks Igorp ! ♥
Updated images, more recent kernel, support for 2Gb boards
what is not working with Bluetooth? the stack cannot be installed? The Fire3 doesn't even have it however it seems that it shouldn't be that difficult to bake the stack in?
I flashed the last recent Armbian Bionic (desktop mainline kernel 4.14.y) dated on 22.08.2018.

I2C is available:

Code: Select all

# fdtget /boot/dtb/nexell/s5p6818-nanopi-fire3.dtb i2c0 status
okay

# ls -la /dev/i2c*
crw------- 1 root root 89, 0 Sep  2 09:15 /dev/i2c-0
crw------- 1 root root 89, 1 Sep  2 09:15 /dev/i2c-1
crw------- 1 root root 89, 2 Sep  2 09:15 /dev/i2c-2
crw------- 1 root root 89, 3 Sep  2 09:15 /dev/i2c-3


But SPI is not available

Code: Select all

# fdtget /boot/dtb/nexell/s5p6818-nanopi-fire3.dtb spi0 status                                                                                                                                                 disable

# ls -la /dev/spi*
ls: cannot access '/dev/spi*': No such file or directory


I compared the DTB from the running Armbian Bionic (kernel 4.14) system (dtc -I fs /sys/firmware/devicetree/base) with the DTS from FriendlyArm (kernel 4.4) (https://github.com/friendlyarm/linux/blob/nanopi2-v4.4.y/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi)
They are very different. Especially there is no `spidev`

There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.

How can I hack on the Armbian kernel for Fire3 (modify device tree, merge touch screen support from FriendlyArm kernel 4.4, etc.)

Thanks,

Andreas
tebachi wrote:
I compared the DTB from the running Armbian Bionic (kernel 4.14) system (dtc -I fs /sys/firmware/devicetree/base) with the DTS from FriendlyArm (kernel 4.4) (https://github.com/friendlyarm/linux/blob/nanopi2-v4.4.y/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi)
They are very different. Especially there is no `spidev`

There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.

How can I hack on the Armbian kernel for Fire3 (modify device tree, merge touch screen support from FriendlyArm kernel 4.4, etc.)

Thanks,

Andreas


SPI bits exits in the common include file arch/arm64/boot/dts/nexell/s5p6818.dtsi and probably works ... so you just need to enabled them. A touchscreen will be a bit more challenging but it should be doable. Try to port bits from 4.4.y kernel and check if there is any special driver for it. And port that too.

We provide Fire3/T3+ images but we can't afford to provide end user support because only one person is working on it. That is too little and below support rules threshold. We have a special part of the forum for older or non-supported boards: https://forum.armbian.com/forum/25-peer ... l-support/

But nevertheless, we are still improving overall support.
https://twitter.com/armbian/status/1038146549124083715

Relevant commits, the first one is included in the image you are running, second not:
https://github.com/armbian/build/commit ... 2875ac2436
https://github.com/armbian/build/commit ... 935bf095f9
igorp wrote:
tebachi wrote:
I compared the DTB from the running Armbian Bionic (kernel 4.14) system (dtc -I fs /sys/firmware/devicetree/base) with the DTS from FriendlyArm (kernel 4.4) (https://github.com/friendlyarm/linux/blob/nanopi2-v4.4.y/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi)
They are very different. Especially there is no `spidev`

There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.

How can I hack on the Armbian kernel for Fire3 (modify device tree, merge touch screen support from FriendlyArm kernel 4.4, etc.)

Thanks,

Andreas


SPI bits exits in the common include file arch/arm64/boot/dts/nexell/s5p6818.dtsi and probably works ... so you just need to enabled them. A touchscreen will be a bit more challenging but it should be doable. Try to port bits from 4.4.y kernel and check if there is any special driver for it. And port that too.

We provide Fire3/T3+ images but we can't afford to provide end user support because only one person is working on it. That is too little and below support rules threshold. We have a special part of the forum for older or non-supported boards: https://forum.armbian.com/forum/25-peer ... l-support/

But nevertheless, we are still improving overall support.
https://twitter.com/armbian/status/1038146549124083715

Relevant commits, the first one is included in the image you are running, second not:
https://github.com/armbian/build/commit ... 2875ac2436
https://github.com/armbian/build/commit ... 935bf095f9

There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.
azzysisi wrote:
There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.


Other supported boards
Odroid XU3/XU4/HC1, Nanopi Fire3, Nanopc T3/T3'+
https://forum.armbian.com/forum/11-othe ... ed-boards/
igorp wrote:
azzysisi wrote:
There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.


Other supported boards Torrent TurboTax Gogoanime
Odroid XU3/XU4/HC1, Nanopi Fire3, Nanopc T3/T3'+
https://forum.armbian.com/forum/11-othe ... ed-boards/

cool
igorp wrote:
tebachi wrote:
I compared the DTB from the running Armbian Bionic (kernel 4.14) system (dtc -I fs /sys/firmware/devicetree/base) with the DTS from FriendlyArm (kernel 4.4) (https://github.com/friendlyarm/linux/blob/nanopi2-v4.4.y/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi)
They are very different. Especially there is no `spidev`
iTunes Mobdro TutuApp
There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.

How can I hack on the Armbian kernel for Fire3 (modify device tree, merge touch screen support from FriendlyArm kernel 4.4, etc.)

Thanks,

Andreas


SPI bits exits in the common include file arch/arm64/boot/dts/nexell/s5p6818.dtsi and probably works ... so you just need to enabled them. A touchscreen will be a bit more challenging but it should be doable. Try to port bits from 4.4.y kernel and check if there is any special driver for it. And port that too.

We provide Fire3/T3+ images but we can't afford to provide end user support because only one person is working on it. That is too little and below support rules threshold. We have a special part of the forum for older or non-supported boards: https://forum.armbian.com/forum/25-peer ... l-support/

But nevertheless, we are still improving overall support.
https://twitter.com/armbian/status/1038146549124083715

Relevant commits, the first one is included in the image you are running, second not:
https://github.com/armbian/build/commit ... 2875ac2436
https://github.com/armbian/build/commit ... 935bf095f9

Maybe we'll get somewhere with this !
tebachi wrote:
I flashed the last recent Armbian Bionic (desktop mainline kernel 4.14.y) dated on 22.08.2018.

I2C is available:

Code: Select all

# fdtget /boot/dtb/nexell/s5p6818-nanopi-fire3.dtb i2c0 status
okay

# ls -la /dev/i2c*
crw------- 1 root root 89, 0 Sep  2 09:15 /dev/i2c-0
crw------- 1 root root 89, 1 Sep  2 09:15 /dev/i2c-1
crw------- 1 root root 89, 2 Sep  2 09:15 /dev/i2c-2
crw------- 1 root root 89, 3 Sep  2 09:15 /dev/i2c-3


But SPI is not available

Code: Select all

# fdtget /boot/dtb/nexell/s5p6818-nanopi-fire3.dtb spi0 status                                                                                                                                                 disable

# ls -la /dev/spi*
ls: cannot access '/dev/spi*': No such file or directory


I compared the DTB from the running Armbian Bionic (kernel 4.14) system (dtc -I fs /sys/firmware/devicetree/base) with the DTS from FriendlyArm (kernel 4.4) (https://github.com/friendlyarm/linux/blob/nanopi2-v4.4.y/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi)
They are very different. Especially there is no `spidev`

There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.

How can I hack on the Armbian kernel for Fire3 (modify device tree, merge touch screen support from FriendlyArm kernel 4.4, etc.)

Thanks,

Andreas

Updated images, more recent kernel, support for 2Gb boards
SlappyMcPhee wrote:
what is not working with Bluetooth? the stack cannot be installed? The Fire3 doesn't even have it however it seems that it shouldn't be that difficult to bake the stack in?

There is no forum from Armbian that I can ask question on Fire3. So I ask my questions here.
Sarkari Result iTunes Notepad++
How can I hack on the Armbian kernel for Fire3 (modify device tree, merge touch screen support from FriendlyArm kernel 4.4, etc.)

Thanks,
JAGITA wrote:
There is no forum from Armbian that I can ask question on Fire3.


There is. Here:
https://forum.armbian.com/forum/11-othe ... ed-boards/
Another update! Download new image or via apt update ; apt upgrade

Kernel update to 4.14.116

More info:
https://twitter.com/armbian/status/1124592076962836480
Added Debian Buster images with many small fixes on kernel level and:

- kernel 4.14.131
- added wireless drivers for 88x2bu
- updated wireless drivers for Realtek 8811, 8812, 8814 and 8821
- updated wireless drivers for rtl8188eus & rtl8188eu & rtl8188etv
- added latest Wireguard driver

Who is online

In total there are 5 users online :: 0 registered, 0 hidden and 5 guests (based on users active over the past 5 minutes)
Most users ever online was 825 on Wed Aug 28, 2019 3:18 pm

Users browsing this forum: No registered users and 5 guests