jhpadjustable

Members
  • Content Count

    9
  • Joined

  • Last visited

About jhpadjustable

  • Rank
    Newbie

Profile Information

  • Location
    Michigan

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. A. It looks like you had it working at one point, before you uninstalled lightdm. Reinstalling lightdm should restore the local GUI. If not, you also should undo tightvncserver configuration. B. There is no desktop until you login. You would need to configure the display manager to auto-login as a user, then configure that user's desktop to auto-start sharing upon login. People more familiar with Xfce4 and GNOME's version of desktop sharing might help me with the details...
  2. If you can see console text on the monitor, 1, 2, 3 are not relevant because your video output hardware is working fine. I only skimmed the video with the sound off, but I didn't see any suggestion that the author had a local monitor on the Zero simultaneously observing the same desktop. There is no shared desktop in X as there is on Windows. VNC desktops are separate from local desktops. If you really need some sort of screencasting, the easiest way would be to run the local X server with auto-login and add the VNC server to auto-start from within the desktop session environment. The VNC server will then accept connections and use its access to the local desktop to share it with network users.
  3. With Orange Pi Zero you really have to apply a quality power supply, not just grab any old microUSB charger out of the charger drawer. Overheating has been associated with insufficient power supplies. Even in the black box with no heatsink, I have never exceeded 62°C when powering the device from a decent adapter.
  4. Could be a bad/insufficient/old power supply, bad/counterfeit/mis-inserted SD card, bad/wrong/corrupted image, .... you really should view the serial console[1] to see if there's any useful message or any legible output at all. If you must fly blind, first try rewriting the SD card, making sure you're using the correct stable image for the board and verifying that it was downloaded, extracted, and written to the card properly. [1] See http://lucsmall.com/2017/01/19/beginners-guide-to-the-orange-pi-zero/ (read the note on the USB-to-serial converter voltage level before the "Software requirements" heading, then skip to "Alternative strategy, using USB-to-serial converter")
  5. See the "Orange Pi Zero wireless module status" pinned thread and other XR819-related threads in this H2/H3 subforum. Shorter: Are you volunteering? If not, then probably not: too many users with too little patience having too high expectations of too weak a wireless chip with too little and too poor public documentation/drivers You could fall back to the ill-reputed legacy kernel, obtain a supported USB wireless adapter, or configure and build your own kernel with xradio_wlan enabled https://github.com/armbian/build/. Whatever you choose, good luck.
  6. Did you use cp -r or cp -R ? Neither of those copy exact ownership, permissions or symlinks. I've never, ever had a problem copying system disks with cp -a ...
  7. The low-level hardware driver has loaded, but no application level drivers are plugged into it. Maybe you want to blacklist the rfcomm module? Try this answer from way back (covers both Wi-Fi and BT)
  8. The Opi0 has only one 16-bit-wide RAM, probably to reduce circuit board layers, and so cost. The OpiPCs have a 32-bit-wide channel to RAM.
  9. I'll assume for UI you want to use the console, i.e. built-in video out and keyboard/pointer input. In that case, since you want good IDE support, consider Electron (https://electron.atom.io) which is sort of a Chromium + Node.js mashup. The familiar programming model of HTML5/DOM/CSS/JavaScript and the I/O and package management model of Node.js are available to you. Some rasPi Node.js I/O modules will work directly, or with some modification. You should be able to use any web-development IDE of your choice that works with Node.js and Chromium, even over-the-wire debugging. You can even start an HTTP API and/or serve a web interface in a few dozen lines of code! On the other hand, JIT-compilers and browsers are big and hungry, so there is little room to spare in 512MB. Avoid using other heavyweight frameworks and libraries, disable or bypass unneeded services, etc. If you need something more lightweight, consider wxLua (http://wxlua.sourceforge.net/), which I haven't tried, but which appears to fit your bill. It comes with some sort of code editor. I have successfully used the "periphery" module which supports GPIO, SPI, UART, and more. Beware, Lua is barebones and single-threaded. If you want multi-tasking, you must bring your own scheduler (the LOOP object oriented programming library has a few) and often you must hook things up to it manually. If you wanted a great out-of-box experience, BeagleBone Black and its vendor Linux distro would have been the best choice. It has HDMI out, a fine web IDE (Cloud9) on board, an Ethernet gadget enabled by default, Node.js modules for much of its hardware ensemble, and many tutorials. On a general-purpose Linux like Armbian, you get to combine all the myriad possibilities for yourself. Poring over catalogs and web sites to learn all of what's available and to make tradeoffs between the options is half the fun. Welcome to embedded development I hope this helps.