-
Posts
3892 -
Joined
-
Last visited
Reputation Activity
-
martinayotte got a reaction from Aditya in Shut down OPi Zero using a push button on GPIO
Beware that even if you trigger event from GPIO to execute "halt" command using a "gpio-key" node in DT, the OPiZero will still be connected to PSU since there is no PMIC to really turn off the power...
-
martinayotte got a reaction from starman345 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)
Try that and reboot :
mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt
-
-
martinayotte got a reaction from gounthar in Orange Pi PC 1-Wire
I've used the NXP SA56004 in the past, but not necessarily on OPi ...
-
martinayotte got a reaction from TRS-80 in use f2fs on sdcard
I doubt it can be done easily : U-Boot is not aware of F2FS, so it requires that at least the /boot folder to be located in EXT4 or FAT partition.
What you can do is to manually shrink the ROOTFS partition and then add a new partition that you will format as F2FS.
Then, you can transfer ROOTFS contain to new F2FS partition using tools such "rsync" or "tar|tar", and leave the /boot folder, adjust both /boot/armbianEnv.txt and /etc/fstab to point ROOTFS to the new F2FS.
-
martinayotte got a reaction from TRS-80 in Need help in using 4x4 matrix Keypad on Orangepi Zero GPIO
Right ! Especially That I've provided an example in the 4th post more than three years ago ...
-
martinayotte got a reaction from _r9 in use f2fs on sdcard
I doubt it can be done easily : U-Boot is not aware of F2FS, so it requires that at least the /boot folder to be located in EXT4 or FAT partition.
What you can do is to manually shrink the ROOTFS partition and then add a new partition that you will format as F2FS.
Then, you can transfer ROOTFS contain to new F2FS partition using tools such "rsync" or "tar|tar", and leave the /boot folder, adjust both /boot/armbianEnv.txt and /etc/fstab to point ROOTFS to the new F2FS.
-
martinayotte got a reaction from reinisv in NanoPi M4 V2 - M4 Image not working
To get more verbose log details, you need to edit /boot/armbianEnv.txt and change "verbosity=7" as well as "console=serial" ...
-
martinayotte got a reaction from buratino in I put together a new kernel, what should I do to start a new kernel?
Are you sure about "plus" ? I'm not aware of "plus" variant, I only know "OrangePi3" ...
If you original image is an Armbian image, U-Boot is loading /boot/Image, which is a symbolic link to vmlinuz-5.4.7-sunxi64. But it also load /boot/uInitrd, which is a symbolic link to uInitrd-5.4.7-sunxi64 and you also need to make sure you installed modules in /lib/modules/5.4.7-sunxi64.
Maybe it would be easier for you to use Armbian build scripts and compile a kernel package that would be installed with "dpkg -i linux-image-dev-sunxi64_19.11.7_arm64.deb" ...
-
martinayotte got a reaction from jsorocil in Rock PI 4 A not starting
No ! Not true ! Trust me, or as Igor said, read the Rockchip datasheets !
All RK3399, as well as any other Rockchip SoC, are loading U-Boot from eMMC first.
The fact that some boards is looking at SDCard is simply that this U-Boot loaded from eMMC is checking for SDCard with specific format, partitions, or uEnv.ini, and then continue boot process from SDCard.
-
martinayotte got a reaction from starman345 in NanoPC T4
Maybe you should try another firmware :
mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt And then reboot ...
-
martinayotte got a reaction from sgjava in NanoPi Duo disable shutdown button
It is better to use "-@" option on "dtc", this is to keep symbols. But it is only available on device-tree-compiler_1.4.7-3_arm64.deb or newer.
-
martinayotte got a reaction from gounthar in Orange PI Win - Blink LED -
Although some will say that way is almost deprecated, the simplest way is to use /sys/class/gpio !
Here is a small bash script that toggle the green LED of OPiWin which is on PH11/GPIO235 :
#!/bin/bash echo 235 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio235/direction while true; do echo 0 > /sys/class/gpio/gpio235/value sleep 0.25 echo 1 > /sys/class/gpio/gpio235/value sleep 0.25 done
-
martinayotte got a reaction from gounthar in OPI WIN how to steering RGB LED APA106
You need some NeoPixel library ...
Here are some info extracted from https://gist.github.com/probonopd/97f6826cc5aa3c0c0950682b0bc266bc
WS2812B Neopixels driven by Python Connect the data line of the WS2812B Neopixels to pin SPI1_MOSI/PA15. In /boot/armbianEnv.txt we need: overlays=spi-spidev param_spidev_spi_bus=1 param_spidev_max_freq=100000000 We can successfully compile the needed Python libraries on the device itself: git clone https://github.com/doceme/py-spidev.git cd py-spidev make -j4 make install cd .. git clone https://github.com/joosteto/ws2812-spi.git find ws2812-spi/ -type f -name '*.py' -exec sed -i -e 's|spi.open(0,0)|spi.open(1,0)|g' {} \; find ws2812-spi/ -type f -name '*.py' -exec sed -i -e 's|tx=\[\]|tx=\[0x00\]|g' {} \; Make sure to use spi.open(1,0); we need to use SPI bus 1 since the internal SPI Flash is connected to SPI bus 0. # Make 16 LEDs red ./ws2812-spi/ws2812.py -c "[[0,255,0]]" -n 16 # Make 16 LEDs white ./ws2812-spi/ws2812.py -c "[[255,255,255]]" -n 16 # Switch 16 LEDs off ./ws2812-spi/ws2812.py -c "[[0,0,0]]" -n 16
-
martinayotte got a reaction from gounthar in GPIO and Armbian for OrangePi Zero.
The offical place to look is on linux-sunxi site :
http://linux-sunxi.org/Orange_Pi_Zero#Expansion_Port
Schematic is here :
https://linux-sunxi.org/File:Orange-Pi-Zero-Schanetics-v1_11.pdf
So 2 I2C buses are available on the header, the third one is normally for CSI port, but OPiZero doesn't have such port ...
-
martinayotte got a reaction from NicoD in NanoPi M4 Mainline wifi not working
Most probably NetworkManager issue again and again ... Try to disable it and do "old school" /etc/network/interface config, I bet it will work ...
-
martinayotte got a reaction from guidol in Switching SUNXI-DEV to 5.5.y
Both !
I still have to test some boards but 75% of my garden is now on 5.5.0-rc2 ...
-
martinayotte got a reaction from Werner in Switching SUNXI-DEV to 5.5.y
I've committed the sunxi-dev switch to 5.5.y !
The only patches that I didn't took time to fix, so I've disabled them, are :
0128-drm-bridge-extract-some-Analogix-I2C-DP-common-code.patch-disabled 0130-drm-bridge-Add-Analogix-anx6345-support.patch-disabled v3-1-2-si2168-Set-TS-clock-mode-and-frequency.patch-disabled v3-2-2-dvbsky-Add-support-for-MyGica-T230C-v2.patch-disabled But I will try again later ...
-
martinayotte got a reaction from aaditya in RockPi 4b 'board bring up'
Maybe their U-Boot check for presence of SDCard and give it a new priority, but the Rockchip SoC itself looks in this specific order is SPIFlash, eMMC, and then SDCard ...
So, if their U-Boot is erased/replaced by Armbian one, the order will be the one I've mentioned.
-
martinayotte got a reaction from MaxT in C2 eth0 fails on some board
Michael was asking me in a PM where the MAC address is persisted during "first boot" ...
@TonyMac32 are you aware of the persisted address file location ?
-
martinayotte got a reaction from Bernie_O in Switching sunxi current to 5.4.y
I will spend sometime during next 2 weeks to migrate DEV to @megi 's 5.5.y branch ...
-
martinayotte got a reaction from eminguez in pine64: massive date/time clock problem
I've just added the patch, and will do testing when my new build is finished :
https://github.com/armbian/build/commit/d688244fea291e81a42c64aaf3588ee1f83b741c
-
martinayotte got a reaction from yoq in OPi Zero: XR819 wifi broken in new builds
In my case, I'm using "old school" /etc/network/interface, running Stretch 5.4.2, and WiFi running properly as soon as I disabled NetworkManager service.
-
martinayotte got a reaction from guidol in OPi Zero with fresh installs of Ubuntu Disco has apt-get broken
As I said in this other thread :
-
martinayotte got a reaction from chwe in Image for M4 V 2
I've just done a RockPi4 build, will test in in the next hour ...
EDIT : Tested ! It works ! But again, I had to manually finish the eMMC install with "dd" ...
Next ! RockPro64 ! And later cleanup of both families to avoid forgetting patches during migration ...