Anna Vahtera

  • Content Count

  • Joined

  • Last visited

About Anna Vahtera

  • Rank

Recent Profile Visitors

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

  1. Also, note that OrangePi Android images cannot be flashed to microsd cards with a simple Etcher or WinImager (or whatever it was called). You need to use PhoenixCard v4.1.2 I'll type that out again; 4.1.2. I know, google tells you that the latest version of PhoenixCard is 3.1.x, but you can find the 4.1.2 from orangepi's site somewhere, I forgot exactly where. At least for me, the 3.1.x did NOT work at all. Once I found the v4.1.2 everything worked.
  2. Hello! I've just recently gotten a few (okay, several. I might have a problem here.) small single-board computers and I'm thoroughly in love with them. I also purchased a few small LCDs so I could make small independent thing that wouldn't require a huge display - perhaps even portable ones. While I do enjoy using the terminal for practically anything (give me lynx, rtv, byobu and the likes and I'm happy), there are certain advantages in a graphical user interface. But let's face it, the default UIs with modern window managers are... not exactly designed for small, low-res screens. With a 800x480 screen it's plausible to use just a normal WM and be rather fine with it. But let's take the more common 3.2" and 3.5" screens that have either 320x240 or in my case 480x320 resolution. Trying to navigate and use a computer with a 480x320 resolution with a normal window manager is not exactly the most joyous activity in the world. I can drive mine at 720x480 and that is almost usable with LXDE, but I'd prefer to run it at 480x320 because text is better at that res. So, anyone got any suggestions? Requirements are that it runs on ARM (of course) and is lightweight, preferably. Bonus points for being designed for touch screens (as most of the screens do have touch), but is not necessary (I don't have touch drivers installed on most of them, I prefer mouse + keyboard). But I admit having the advantage of being designed for touch use would be nice.
  3. Wait.. both pins, 2 and 4 are +5V pins, you can't use a cooler between to positive pins, you need a ground. Pins 6, 9, 14, 20 and 25 are ground. Connect the cooler wires so that one goes to any of them and the other to pins 2 or 4. (The manual calls those two DCIN, but as far as I know, they work perfectly well as outputs also. Just be aware of that. YMMV.) Also do note that some coolers drain quite a lot of power, so be sure your PSU can power the cooler AND the OPi3 at the same time.
  4. Hello. I have a couple of Chinese 3.5" TFTs, model MPI3508. I'm trying to get it to work with my Orange Pi 3. The module supports either connecting via GPIO or HDMI, either is fine for me. I'm using Linux orangepi3 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 GNU/Linux I'm trying to get it to display the console - no GUI installed, just the console is enough. The module also supports touch, but I don't care about that - I just want to use it as a monitor.. If I use HDMI, I can get a picture, but the resolution is all wrong. It's a 480x320 display but because Chinese manufacturers, it reports itself as having a maximum res of 1920x1080, which obviously is unusable (at this resolution each line in the console is about 2 pixels tall - no way to read text). I've tried following a dozen or so tutorials dealing with changing the resolution via boot.cmd, but up to this point I haven't gotten ANY of the advice to work. I've tried all of these lines in boot.cmd (obviously just one at a time): setenv video-mode sunxi64:480x320-24@60,monitor=dvi,hpd=1,edid=0 setenv video-mode sunxi64:480x320-24@60,monitor=dvi,hpd=0,edid=0 setenv video-mode sunxi64:480x320-24@60,monitor=hdmi,hpd=1,edid=0 setenv video-mode sunxi64:480x320-24@60,monitor=hdmi,hpd=0,edid=0 setenv video-mode sunxi64:480x320-24@25,monitor=dvi,hpd=1,edid=0 setenv video-mode sunxi64:480x320-24@25,monitor=dvi,hpd=0,edid=0 setenv video-mode sunxi64:480x320-24@25,monitor=hdmi,hpd=1,edid=0 setenv video-mode sunxi64:480x320-24@25,monitor=hdmi,hpd=0,edid=0 setenv video-mode sunxi:480x320-24@60,monitor=dvi,hpd=1,edid=0 setenv video-mode sunxi:480x320-24@60,monitor=dvi,hpd=0,edid=0 setenv video-mode sunxi:480x320-24@60,monitor=hdmi,hpd=1,edid=0 setenv video-mode sunxi:480x320-24@60,monitor=hdmi,hpd=0,edid=0 setenv video-mode sunxi:480x320-24@25,monitor=dvi,hpd=1,edid=0 setenv video-mode sunxi:480x320-24@25,monitor=dvi,hpd=0,edid=0 setenv video-mode sunxi:480x320-24@25,monitor=hdmi,hpd=1,edid=0 setenv video-mode sunxi:480x320-24@25,monitor=hdmi,hpd=0,edid=0 and saveenv at the end of the file. recompiled with 'mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr' and rebooted twice after any change in the files. Nothing has worked. With HDMI connected it always displays the picture, but with that resolution everything is really small carbage - unreadable. So I disconnected the HDMI and tried via GPIO, but each and every tutorial with these displays deals with fbtft, which apparently has just been removed, so no dice there. I'm okay with either approach: HDMI with resolution set to 480x320, or via GPIO (and of course same resolution, but at least there shouldn't be any auto-detect via that).. armbianmonitor -u:
  5. Did you ever figure this one out? I have the same problem on my Orange Pi 3 - it boots with the official image just fine, but HDMI output isn't working. Funnily enough, it boots perfectly well with the same Armbian version, if I use the Orange Pi Lite 2 image... there has to be something different with the OPi3 image that makes HDMI not work...
  6. Mine too, HDMI *is* working, perfectly. With Android 7/9 AND the same Armbian version with the Lite2 image - that's why I said I highly doubt it's the monitor. HDMI *is* working, it's just the OPi3 image that won't display anything. It displays everything just perfectly if I boot it with the Lite2 image (since the hardware is pretty much identical, the OPi3 just has the option for eMMC and it has more ports, that's pretty much it) EDIT: Here's too captures (via serial) of the board booting: OPi3 booting Lite2 image: (HDMI Out IS working with this image) OPi3 booting OPi3 image: (HDMI Out is NOT working with this image) The Lite2 has UART3 enabled, otherwise it is the same. I noted that there is a bunch of voltage info at the top which is missing from the OPi3 image. I don't know if this is relevant. I also don't know what to make of this, but just noting that both of the boards boot well with the Lite2 image and neither of the boards boot with the OPi3 image. There's GOTTA be a difference there, it's not hardware. EDIT2: Here's 'dmesg' from the two images booted on the OPi3:: Image "Lite2", Working HDMI: Image "OPi3", No HDMI:
  7. Well, the OPi3 has the option of having an eMMC, it doesn't necessarily have it - mine doesn't. I don't even have a slot for it, just solder markers on the board. So maybe that's the problem? If the OPi3 image assumes the board has eMMC when it doesn't, and then that doesn't work? It would be too weird if it was the monitor, as both the boards work well with the same monitor when booting the Lite2 image. It works on the OPi3 when booting either OPi3 Android 7 or OPi1+ Android 9. It works with RPi and Rasbian, RetroPie. I highly doubt it would be the monitor if the Lite2 image works with both boards just fine. It's just the OPi3 image that doesn't work. ps. The Lite2 does not boot with the OPi3 image either, just tested.
  8. I hope I can ask here (I'm new so it won't let me post a question on the main H6 page). What's the difference between the images for Orange Pi 3 and Orange Pi Lite 2? I have both boards, downloaded both images. The Lite 2 image (Armbian_20.02.1_Orangepilite2_buster_current_5.4.20.img) works on both boards, flawlessly (well as flawlessy as Armbian and Orange Pi ever do). Both boards boot just fine with that image. However the OPi3 does not display anything with the 3 image (Armbian_20.02.1_Orangepi3_buster_current_5.4.20.img). I can connect to the board via serial console and I can see it booting fine and I can interact with it, but it does not display anything at all. So there's some difference between those images that prevents the OPi3 from displaying anything. I haven't yet tried to boot the Lite2 with the OPi3 image, will get to that later.
  9. SomeBloke, what program are you using to flash the image to the SD card? I ask because there is a plethora of options available, but not all of them apparently work with OPi3/Armbian images. I had the most success using Etcher (from Balena). I recommend using that if you're on Windows.
  10. I wrote that command, pressed enter: it takes about 15~20s and then just gives me a new prompt. Does exactly nothing. anna@orangepizero:~$ sudo dpkg-reconfigure keyboard-configuration [sudo] password for anna: anna@orangepizero:~$ There is nothing in any logs that I could find, no messages, no user.log, no faillog, no syslog.. etc. It's like that command never run.
  11. Hello. I have a small problem: I can't change the language on my OPi Zero. I have successfully done that with OPi Lite 2 and OPi 3, but for some reason on the Zero when I go to change it, the module fails to load and just quits back to the same "menu page". (essentially does nothing). The only thing I can think of, is that both of the other boards have 1Gb RAM and this only has 512Mb and thus it runs out of memory? That doesn't sound too plausible though - a list of keyboard languages shouldn't take tens or hundreds of megs of RAM. As far as I know, each board is running the same version of Armbian, so that shouldn't be a problem.