martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
reboot the board ...
-
If it is like other OpenWrt, there should be accessible using sysfs, ie : /sys/class/gpio, doing such commands :
echo 20 > /sys/class/gpio/export echo out > /sys/class/gpio20/direction echo 1 > /sys/class/gpio20/value -
To isolate the issue, maybe you should try to do a simple loopback test first, a jumper between 8 and 10, and use minicom or picocom to get local echo.
BTW, in the case of Mainline, without having other uart enabled other than debug uart0, when I load overlay for uart2, it comes up as /dev/ttyS1, since debug is on /dev/ttyS0.
-
Some of you probably saw that I added recently the OrangePi-Prime to the build process.
Unfortunately, I'm still struggling to get the WiFi.
It is even worst than the WiFi issue still present on OrangePiWin.
For the OrangePi-Prime, even the DT doesn't process the WiFi entries, and the mmc1 is still "disabled" in /proc/device-tree at boot time.
The strange thing is that if I load a small overlay to change the mmc1 status to "okay", the kernel start processing it.
But, unfortunately, I'm seeing "sunxi-mmc 1c10000.mmc: no support for card's volts" error, although I didn't found obvious errors in vqmmc-supply setting of mmc1.
I will have to dig further, but start running out of ideas ...
-
No !
Edit /etc/rc.local and add "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint &" before the "exit 0"
-
For the change in red, Yes !
I've all my OPi as headless, so, I can't answer for the HDMI2DVI questions.
-
You're lucky ...
SPI is designed only for few inches of wire. So, in you case, it is really out of specs.
-
What do you mean ?
Do you mean "how long SPI wiring can be" ? Shortest as possible !
SPI isn't design to work on long distance, especially with high speed.
Although reducing speed could help, it is not designed to support more than few inch of wires.
You are better having two OPiZero is the MFC are meters away from each other ...
-
It is already installed on any images ...
-
-
In such case, since Windows is so stupid, you won't have much choice to have a separate sdcard mounted in a USB reader, having a single FAT partition on this one.
Another solution is to have a Window's folder shared and having your SoC board mounting that CIFS network share.
-
euuhhh ?
libusb-1.0-0-dev as nothing to do with your issue...
why sunxi-fexc ? the tools I've mentioned are "bin2fex" and "fex2bin", but of course, sunxi-fexc can work too.
Of course, it is better to keep manual backups before overwriting any files.
Check this page : http://linux-sunxi.org/Fex_Guide
-
It is not the patching tool that is broken, it is the content of the patch that doesn't match code changes in 4.11.
You probably need to find out those change by comparing 4.10 and 4.11 together, and check which parts of the patch are broken.
-
Unfortunately, this grid is soo incomplete that you can't rely on it for any purchase decision.
(No OPiPC, no OPiPC+, no OPiPlus2E, no OPiPC2, etc)
-
@tkaiser, has it been added recently to builds (and how ?) ? in my recent builds I had to install it manually ...
Also, when I configure user-patches to install them during build process, it is installing them but failed to run their post-install scripts :
Setting up libavahi-common-data:arm64 (0.6.31-5) ...M Setting up libavahi-common3:arm64 (0.6.31-5) ...M Setting up libavahi-client3:arm64 (0.6.31-5) ...M Setting up libavahi-core7:arm64 (0.6.31-5) ...M Setting up libdaemon0:arm64 (0.14-6) ...M Setting up avahi-daemon (0.6.31-5) ...M You are required to change your password immediately (root enforced)M chfn: PAM: Authentication token is no longer valid; new one requiredM adduser: `/usr/bin/chfn -f Avahi mDNS daemon avahi' returned error code 1. Exiting.M dpkg: error processing package avahi-daemon (--configure):M subprocess installed post-installation script returned error exit status 1M dpkg: dependency problems prevent configuration of libnss-mdns:arm64:M libnss-mdns:arm64 depends on avahi-daemon (>= 0.6.16-1); however:M Package avahi-daemon is not configured yet.M M dpkg: error processing package libnss-mdns:arm64 (--configure):M dependency problems - leaving unconfiguredM Setting up libtalloc2:arm64 (2.1.2-0+deb8u1) ...M Setting up libwbclient0:arm64 (2:4.2.14+dfsg-0+deb8u5) ...M Setting up samba-common (2:4.2.14+dfsg-0+deb8u5) ...M M -
Don't move this first/main partition, simply shrink it at the end, and add new FAT partition at the end of the SDCard.
-
-
script.bin is located in /boot. you need to decompile it into script.fex using bin2fex, edit it, and then recompile it into script.bin with fex2bin.
-
What do you mean exactly ? How to flash SPI-NOR or How to make LCD work on RaspberryPi ? this is completely 2 different subjects.
For the SPI-NOR, as Zador said, it is not enabled by default. I personally suggest to use Mainline kernel anyway, it is much more easy to enable the overlay.
-
The IP address 169.254.134.132 is or is not the IP of your MAC ?
How did you figured out that this IP could be the one from OrangePiPC ?
If your router doesn't help to figure out the real IP of the OPi, your will need to connect using Serial USB-TTL and do "ifconfig" on the board itself.
"orangepipc.local" doesn't work until "avahi-daemon" is installed on the OPi, when you will get access to it, simply go "apt-get install avahi-daemon".
-
8189ES isn't not the same as 8189FS.
But, anyway, the 8189fs is already part of Armbian build for some boards such OPiPC+.
Which board do you have ?
And why do you need it under 4.9 ? Armbian is on 4.10 since months ...
-
That is pretty normal if both wlan0 and eth0 are on the same subnet.
the default gateway route is pointing by default to eth0, so when disconnecting eth0, it has no gateway.
Simply boot your OPiZero without eth0 plugged in, the gateway will then point to wlan0.
-
~$ is effectively a command prompt shel, where the ~ means home directory.
For Desktop, did you use a Desktop image for your SDCard ?
Because Server image are headless by default, no Desktop installed ...
-
Check the back of your OPiZero to make sure you have a SPI_NOR already soldered.
If your PCB has blank SOIC8 pads, you will need to purchase a flash chip and solder it there.
Another TV out questions.
in Beginners
Posted
Personally, none of my OPis have any video monitor.
So, I tried to help about FEX, but I can't debug video issues.