Jump to content

broodwich82

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by broodwich82

  1. I'm going to try to order one through the current coronavirus situation and we'll see if it gets here. I'll probably test my existing one in a loopback config sooner or later, too.
  2. Note to self: found a description of how to test on loopback at https://raspberrypi.stackexchange.com/questions/36938/garbled-text-using-serial-to-usb-connection
  3. It's USB 1a86:7523 - USB device database says that's a HL-340 / CH340 from QinHeng electronics. I do note that FriendlyElec sells a USB-serial adapter which claims to be based on the "CH340T" but the one I've got isn't the exact same PCB. My PCB looks a little different and is selectable for 3.3V or 5V logic levels and I have it selected for 3.3V. I'm not sure I completely understand about hooking it up as loopback. I don't actually have a second serial adapter or anything else with an external serial port in the house. I guess I wouldn't be all that surprised if the hardware wasn't managing the weird 1500000 bps rate.
  4. minicom is a full blown terminal emulator. I had it set to 1500000bps, 8N1. I should actually correct myself about the behavior I mentioned, actually sometimes one square and sometimes two squares are printed when I press a key.
  5. Also I feel like this is a configuration error on my part because behavior seems consistent.. at the "hit any key to stop autoboot" prompt, if I hit the esc key it prints two squares, if I hit enter or a letter it prints one. This doesn't vary.
  6. Hi there, this might be a dumb question but I've done some searching and haven't gotten any closer to a solution, so, my apologies. I need to connect to my NanoPi M4 over the serial UART because I've made the eMMC unbootable, and I need to tell the board to boot from microSD so I can fix it. I've attempted to do this in both 'minicom' and 'screen' at 1500000 8N1 and the result is the same either way. I can see output from the NanoPi just fine, but when I attempt to send characters, it only displays a question mark imprinted on a square for each character, similar to what I'd expect if e.g. the character was not in my terminal font. It's not just a display problem either - I can pause the boot sequence by mashing keys, but blindly typing commands does nothing. So I don't think the characters are making it intact to the NanoPi. My serial interface is a USB to serial device which was known working properly before my friend mailed it to me. Currently I'm suspicious that I have something configured wrong and that the USB dongle is probably fine. But that's just my best guess. Apologies if this is something very basic, I've been thru the docs and search on the forum but haven't found the answer.
  7. I've run into bugs in console mode... refuses to output anything other than 1920x1080, including on hardware which maxes out at 720p. Sadly I've never figured out the correct incantations to pass to the kernel in the bootEnv (?) to force it to a resolution... everything I've tried just causes it to freeze completely during boot.
  8. This is on a 4GB NanoPi M4 v1. There are a number of files matching the spec '/etc/ssh/ssh_host_*' but they are all zero bytes, which renders the machine inaccessible by ssh. I'm pretty sure this is happening on every install, I've been troubleshooting and reinstalled several times from the latest image and ssh was not working at any time.
  9. After I edit the u-boot settings in armbian-config, do I then need to select "install" to update the boot loader each time? Edit: figured out by looking thru /var/log/armbian-hardware-monitor.log that I do not.
  10. I got as far as 'cat /sys/class/graphics/fb0/modes' and see only 1920x1080 in there ...... that seems weird. Still have not been able to figure out how to get this board to boot to console mode at a specified resolution. Edit: editing the u-boot environment in armbian-config and setting either of the following didn't work: video=HDMI-A-1:1366x768@60 video=card0-HDMI-A-1:1366x768@60 nor did choosing a standard resolution of 1024x768@60 work with either of those connector specifications. nor did setting 'drm.edid_firmware=edid/1024x768.bin' in u-boot in armbian-config.
  11. Hello, I'm trying to use a NanoPi M4 with an old TV. When the system boots, the TV displays "Invalid resolution." However, it works with a different TV, which unfortunately I cannot use full time. I note that on the working TV, there's a line in dmesg stating "Console: switching to colour frame buffer device 240x67" which would imply that this can be configured somewhere?? However I tried searching, the only docs I get are outdated, for other hardware, or don't work. I tried adding 'disp.screen0_output_mode=1280x720p60' to /boot/armbianEnv.txt, but it had no effect. A pointer as to where these settings are actually controlled would be very helpful. Thanks
  12. I'm confused about how this 2-pin fan header does PWM fan control. It sounds to me like the PWM pin just completely turns the power on/off to the 2-pin socket. But I just want to use standard 4-pin PWM fans with this board. Sounds like that would require extra hacking on the linked post (and an extra pin if monitoring fan RPM is desired). Is that correct? I may for the time being just buy a couple $5 4-pin PWM fan controllers with a temp sensor off Amazon, and worry about this later. Kinda wish they'd made it easy to support standard 4-pin 12V PWM fans, even with just a physical connector.
  13. FYI neither of the above answers was correct because ram logging is provided by log2ram on the Cubieboard2 image I am using. I found the answer as to how to disable it elsewhere: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=3448
  14. Didn't get to this and found /var/log full again... still wondering if there is a reason I shouldn't disable log2ram when using a spinning disk?
  15. Thanks for the responses, folks. Why would it be a problem to disable ramlog on a system that has / on a spinning disk? I want the 50MB of RAM back. Edit: also, I'm using this as a development box for something that generates a lot of logs, 50MB was not enough for more than a week before it was filling up, etc ... so I just want logging to work how it does on a vanilla linux box, seeing as I've got a real disk, unless there's a good reason.
  16. Hello, I've searched through various threads on here and can find no comprehensive answer on how to disable log2ram completely, forever, and preferably end up with only one /var/log with mainstream logrotate settings. This is for a situation where I'm using an actual hard drive and don't need to worry about destroying flash memory. I suspect it is more involved than just 'systemctl disable log2ram'. Any additional pointers would be very helpful, thank you!
  17. This was the result of the Cubieboard 2 units (I have two) being VERY finicky with HDMI to DVI adapters. If possible, it would be best to use native HDMI with these boards, I think. Edit: Actually, they seem to hate some older LCD panels altogether. If you're having any kind of boot problem with the Cubie 2, try a video connection with no adapters, to the newest/best panel you can find.
  18. That NanoPi M4 looks really great, even though it's still pretty new and software support is still in the works. I might be willing to take a gamble on this board since I suspect the Rockchip 3399 will become fairly well supported. I forgot to mention that small form factor is important to me as my project is concealing a wifi-enabled server in an RGB accent lamp which I will carry around with me while living an "ultramobile" lifestyle So, the NanoPi M4 wins on form factor as well. I suspect I could arrive at a tolerable thermal situation by some combination of a copper shim to the heatsink, mounting non-horizontally and building the enclosure with convection in mind, and perhaps some tinkering with clock speeds as needed. Looks like wifi might still be a bit dodgy. I suppose I'll have to take my chances with that and fall back on a known good USB adapter if support is problematic for longer than I have to wait. Thanks so much for the pointers!
  19. Very very interested in an availability date for the SATA HAT. I am somebody who will connect an SSD to this board, not so much for performance as for lower power dissipation and noise. I could use the USB 3 ports for this, but the enclosure I'm envisioning would make this far more awkward than something which attaches to the top of the board.
  20. Thanks for the information on this board, I was considering buying one but it doesn't seem fully baked enough for me.
  21. Hey folks, I'm looking to build a little portable server to hold a local mirror of my cloud drive and run a light-duty testing server for medium-weight web apps (Django, big PHP blobs, etc). 2GB RAM, SATA support, and fanless are critical, USB 3.0 and GPIO ready to go with no soldering a big plus. I'm planning to get a 500GB SSD and use an Alfa AWUS036ACH 802.11ac USB dongle. Box will run headless except for configuration. I was looking at the EspressoBin but kernel support appears to still be incomplete and there isn't that big of a userbase. I also don't need two of the Ethernet ports on that board. I've looked around and it seems the combo of >1GB RAM + SATA support (even 2.0 is okay) + fanless isn't common. Of those criteria I'm willing to give up USB 3 first. I know my wifi dongle is USB 3 but I'm okay with putting it in a USB 2 port if need be, I care far more about the dongle's ability to transfer data in marginal conditions than I do about max throughput.
  22. Thanks for the input folks, I'm going to try either a new microSD or the UART adapter or both. I'll try to report back.
  23. My Cubieboard 2 absolutely refuses to boot from microSD. It will boot into Android from flash when there is no microSD card inserted, but with a card in, it just produces a single red LED and no video output. Eventually it will respond by flashing green and powering down when the power button is depressed, so I feel like it's getting somewhere, but those are the only signs of life. I don't know how to look at serial output from this machine. I've tried two different power supplies, and two different monitors because one had I think been dodgy with this machine before. Same problem on all permutations. I also tested the SD card with F3 and wrote it with Etcher, and I've used it before and it was known good, so I'm 90% confident that the SD card is good. Ideally I would like to install the system to a SATA or USB hard drive, if there's any way I can skip microSD and just do that from the start, that would also work for me. I'm attempting to boot Armbian with the mainline kernel, BTW, not the legacy one.
  24. Thanks! Yeah, I saw about the crowdfunded effort to bring it to mainline - very exciting. I'll try with a few different video sources to see if it's a problem with the specific ones I'm trying, maybe they are encoded at too high a profile or something... they're 720p, x264, a bit over a GB for 45 minutes of video, that's all the detail I've got so far.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines