Jump to content

zipzit

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

1161 profile views
  1. I've been playing with Orange Pi Zero. I've been playing with both Armbian_5.25_Orangepizero_Ubuntu_xenial_default_3.4.113.img and Armbian_5.25_Orangepizero_Debian_jessie_default_3.4.113.img . I've been using a FTDI communication Serial adapter on a Mac Laptop via Terminal $ screen ≺port_name≻ ≺baud_rate≻ In my case the screen command looked like this: $ screen /dev/tty.usbserial-AE00BS5L 115200w What I've discovered is when I'm using serial communications, tools like $ nano filenamee or $ nmtui , the system interface gets all screwed up. If you have the commands memorized, you can still use Nano (barely) but not so easy with nmtui. The screen overwrites in a weird method and you can't really read anything. This only goes awry on Debian Jessie, but works fine Ubuntu Xenial. Things work just fine on both image flavors if you login via a SSH connection. Is this a bug? I do note Debian Jessie is no longer listed as prime on https://www.armbian.com/orange-pi-zero/ .
  2. Background: I'm using Orange Pi Zero for data I/O. I'm using https://github.com/zhaolei/WiringOP to manage the GPIO stuff. So I've been writing programs in C/C++ using the simple nano editor via SSH to my Orange Pi Zero. I start by doing all code edit within Atom.io on my laptop/desktop computer. (I ALWAYS want a record of what I'm changing... ) I keep track of code changes via Git and the Atom content on my laptop/desktop. When it comes time to push code to the Orange Pi, I SSH login to the orange pi: Delete my old workingCode.c file (erasing big blocks of code within Nano is a pain in the neck) Create the file again via Nano. Copy paste the new code (from Atom), exit and save the file. Run from SSH via gcc workingCode.c -o workingCode -lwiringPi This works fine, as long as you don't need to step thru the code. I've been playing around with Visual Studio Community Edition 2015 lately. I was using it to do OpenCV stuff using C/C++. I saw this posting, https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/ I did some playing around (basically hello world programs with lots of variables and calculations...) and wow. This works.. kinda, sorta. File master on my laptop/desktop within the Visual Studio project. When I compile and run, the system pushes the code from Visual Studio right over to my orange pi device. I can debug step through the code, including inspection of variable content at interim steps. Output is available via a console window within Visual Studio. For a "helloWorld.c" program, Visual Studio does create a few files on my Orange Pi: projects directory helloWorld directory bin directory ARM directory Debug directory helloWorld.out file <--- ./helloWorld.out works! obj directory ARM directory Debug directory helloWorld.o file helloWorld.c file My dilemma is I don't understand is how Visual Studio deals with on remote libraries. When I try to use GPIO on the Orange Pi, I get errors relating to the wiringIP library. Part of my problem is the zhaolei/WiringOP is called from within the C program via #include <wiringPi.h> and wiringPi library in its original form is already located within the Visual Studio system. Its not clear to me on how to set this system up to use the already-compiled-on-remote-device-library. Anybody else using Visual Studio Enterprise edition for Orange Pi (or other armbian) work? any hints on how to proceed here? It sure would be nice to be able to step thru code and inspect interim results during debugging. Many thanks.
  3. I'm trying to understand how you get from point A to point Z via that matrix repository at Github. That repository is intended "Nanopi2/Fire/M2" devices, yet the Orange Pi Zero is an Arm H2 device. Remember the orange pi zero is listed as the topic for this posting. Is the Orange Pi Zero Arm H2 really a Nanopi2 / Fire or M2 device? How do you know that? Are these things the same? (I'd refer to the readme.md sheet at the matrix repository, but alas, that doesn't exist... sigh.) Orange Pi Zero = Arm H2 Quad-core Cortex-A7 1.2Ghz. Raspberry Pi Zero =A Broadcom BCM2835 application processor with 1GHz ARM11 core (Note: no offense intended here.. I'm struggling to understand how to address the pins on the Orange Pi Zero, and I'm more than confused here... Any hints or links to help gain and understanding? Many thanks --Zip)
  4. Sorry.. I should have been more clear. Is there a setting somewhere that can be used to determine if the internal CPU temperate is stored as degrees Celcius or as milli-degrees Celcius. We could do a hack, like If value is numeric and less than 1, assume the data is milli-degrees C and divide by 1000 But that just seems wrong. I was thinking there is an internal value stored in that that could be polled to indicate CPU type / mfgr model / etc...
  5. So I just received a couple of Orange Pi Zeros. I thought for a fun first project I'd port the pi-hole project. The Pi-Hole project creates a black hole / dns server for your home network that filters out lots of extraneous advertising. Its a pretty nice project. Reference: https://pi-hole.net/and https://github.com/pi-hole/pi-hole I ended up using a semi automatic install for pi-hole: git clone --depth 1 https://github.com/pi-hole/pi-hole.git Pi-hole cd Pi-hole/automated_installer/ bash basic-install.sh There was one hiccup. The admin page for the pi-hole (run on your local network) in the browser includes a header that conveniently shows CPU temperature. Unfortunately the system scans for temperature at location: /sys/class/thermal/thermal_zone0/temp From what I can tell, that value on a Raspberry Pi is 1000 times greater than the core temp in deg Celcius. On the Orange Pi Zero, that reading seems to be straight degrees celcius. With that said, there is one minor software change to be made... You will change this line: $celsius = intVal($output)*1e-3; to $celsius = intVal($output); at location /var/www/html/admin/header.php (original source = https://github.com/pi-hole/AdminLTE/blob/master/header.php) Note: there should be a way to recommend a mod to the pi-hole repository team that says (if orange pi use 1 as the divider, else use 1000) but I'm not aware of what would work there. Anybody know of a handy technique?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines