kgb

I found a way to boot after having deleted the U-boot partition, which prevents any useful boot to allow repair. I could then complete the armbian install. This applies to my Pinebook A64, 14" (not the pro pinebook - i cant test that) After removing the U-boot partition, it would only boot to a "busybox" with limited features, not enough to do a repair. I had a copy of armbian jammy on an sd-card, and this had booted OK before my stupid error. But with the SD card inserted, it stilll only booted to the busybox . The trick was to start the boot, and then insert the SD-card mid-boot, and it then booted the working system from the SD-card. During the defective boot, there is a pause with a few lines of text on the screen before it then proceeds with more error messages and into the busybox. I inserted the SD-card during that pause and it completed the boot from the SD-card. (you may need to time this carefully, but it worked on first try for me) Then you have a complete working system and can use armbian-config, > install system to eMMC and it copies the system to the eMMC and fixes the u-boot issue. It will now boot direct from the eMMC. Took me a while to find this trick which I have not seen documented anywhere, but is essential to get a system running to effect a repair.

Checkout the code solution from nopnop2002 at orange pi forum here http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2549&extra=

I have solved my problem above by manually selecting each of the 2 slave devices by using 2 spare gpio pins as outputs and using digitalWrite(...) to select the desired slave device before then accessing either device through the single spi driver - /dev/spidev0.0 Its a bit of a kludge, but works. I suspect the problem is that the kernel module fails to allow for multiple slaves on a single spi bus.

I have an ADC and DAC board built for Raspberry Pi which has 2 slaves on the SPI bus, requiring ce0 and ce1. This works fine on the Raspberry pi 3, which installs devices /dev/spidev0.0 and also /dev/spidev/0.1, to access each slave. On the OPi PC I can access slave 0, but not slave 1. In /dev on the Opi there is only a single spidev device: /dev/spidev0.0 and no spidev0.1 device. I have modified the script.bin (I am using Armbian legacy OS - Armbian_5.14_Orangepipc_Debian_jessie_3.4.112_desktop) by editing the .fex (and making a new script.bin) to add a spi_cs1 = port:PC07<3><default><default><default> line. But adding this prevents any spidev device from loading, even spidev0.0 is now missing. I have tried many variations to add a spi_cs1 connection in the fex file, but nothing works. the OPi pinout description includes SPI-CE1 (header pin 26) but how can i make this active? How can I make the spi system on the OPi PC work with 2 slave devices on the bus as the rasberry pi does easily? Is this an issue with the armbian OS, the fex file configuration, or a hardware issue with the OPi PC. I read that there is an issue with SPI on the OPi One - but does this problem with NAND access also affect the OPi PC?