webbbn
-
Posts
52 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by webbbn
-
-
I am trying to get composite video fully working on an Orange Pi Zero Plus 2. I installed the legacy kernel image, and I've been able to turn on composite out, but I just get a blank screen on boot and there is no /dev/fb0. Is there anything else I have to do to enable the framebuffer.
This is the (I believe) relevant portions of the script.fex file:
[boot_disp]
advert_disp = 0
auto_hpd = 1
output_type = 4
hdmi_channel = 0
hdmi_mode = 4
cvbs_channel = 1
cvbs_mode = 11
output_full = 1
hdmi_mode_check = 1
[disp_init]
disp_init = 1
disp_mode = 1
screen0_output_type = 3
screen0_output_mode = 5
screen1_output_type = 2
screen1_output_mode = 14
fb0_framebuffer_num = 2
fb0_format = 10
fb0_pixel_sequence = 0
fb0_scaler_mode_enable = 1
fb1_framebuffer_num = 2
fb1_format = 10
fb1_pixel_sequence = 0
fb1_scaler_mode_enable = 1[hdmi_para]
hdmi_used = 0
hdpc_enable = 0[tv_para]
tv_used = 1
tv_dac_used = 1
tv_dac_src0 = 0these are some possible relevant lines from boot.
[ 0.000000] Kernel command line: root=UUID=ab03f9a3-0ba3-4236-8857-33f3229b7a85 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 monitor=composite-ntsc panic=10 consoleblank=0 loglevel=1 ubootpart=75ceecdb-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M cgroup_enable=memory swapaccount=1
[ 0.614087] [DISP]disp_module_init
[ 0.614413] cmdline,init_disp=
[ 0.614448] cmdline,disp=
[ 0.615200] [DISP]disp_module_init finish
[ 1.029299] cmdline,disp=
[ 1.029629] [DISP] disp_init_tv,line:539:screen 0 do not support TV TYPE!
[ 1.029647] [DISP] bsp_disp_tv_register,line:998:'ptv is null
[ 1.029710] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr1<-->device1, type=2, mode=14
-
I installed the experimental version of the NanoPi Neo Air distribution on my Air a month or two ago. At the time I believe Bluetooth was not working on that version. I don't see any indication that it is not working now, but it doesn't seem to be working on my install.
Is Bluetooth working on the experimental kernel? If so, should I just re-install, or is it not hard to get it working on an existing install? I just installed the latest updates and rebooted, and that didn't fix it.
The symptom that I'm seeing is that if I run bluetoothctl it prints a prompt, but seems to lock up.
-
About heatsink : I don't have any. If you install FA heatsink, you cannot solder pin anymore ? Right ?
I have a huge copper heatsink in a drawer. Do you think it could be possible to increase frequency on these boards (neo with v1.1 PCB or air) ?
The heatsink is just bolted on, so it's easy to remove, but it doesn't interfere with the pins, so it's possible to solder pins on even with the heatsink installed.
-
Hi
Having now got my NEO to work as a Network Attached Audio Device I want to power it with a 5V linear power supply.
Do I use the
TTL To RS232 Module（PSU-ONECOM）connected like http://www.friendlyarm.com/image/catalog/description/NanoPi-NEO_en_07.jpgWill this power the board without the micro usb connected?
Regards
Carl
It doesn't look to me like that comes with a power supply, and I don't know why you would want to use that anyway if you just want to power it.
Why not use something like this: https://www.amazon.com/Raspberry-Power-Supply-KuGi-Adapter/dp/B01E6YLFAO
-
Okay, so you have to have the sdcard inserted at boot time for it to be recognized. I have it working now, but can't it be made to auto-mount on insert?
-
Any recommendations on how to mount the sdcard when booting off the eMMC? Is there a module that I need to load?
-
"I used nmtui, and it worked perfectly"
Well, I edited a config with nmtui, but by me it doesn't work. And now my nanopi crash regularly. So I think the driver may be buggy.
Do you use dhd or bcmdhd ?
I just logged in and, ran nmtui, selected an access point, typed in the password, and it worked. I don't know what dhd or bcmdhd are.
-
Well I don't know. Network manager and systemd are making me crazy. My image is :
Armbian_5.21.161020_Nanopiair_Ubuntu_xenial_3.4.112.7z
It is beta image... I cannot make wlan even take an ssid. As I don't want to solder anything on the board, I have no console and I cannot test gadget modules without loosing my connection. I will try to disable g_serial and load g_ether, but if it does not work, I will end the tests and install my own system.
I'm confused. In one post above you describe how to connect via g_ether, then you reply to yourself that it doesn't work.
What are you using to configure your wlan? I used nmtui, and it worked perfectly. I just selected a SSID, typed in the password, and it worked.
And what do you mean "install my own system"? Do you have your own distribution that works better than Armbian?
Remember, this is beta, and the developers of Armbian haven't even gotten their hands on hardware yet. I'm sure it will be working very well shortly. I think it's already working pretty well.
-
Dont't try that with the nanopi air beta image : it already load g_serial and g_ether would not load :
modprobe: ERROR: could not insert 'g_ether': No such device
When you boot the nanooi air image with a usbA - microusb cable, the connected host create a /dev/ttyACM0 device. You can connect to the nanopi air by :
screen /dev/ttyACM0
and start to hack your system ...
That's odd. I'm able to load g_ether on the Armbian beta image (I believe from the 19th).
-
Regarding Wi-Fi power management please see https://github.com/igorpecovnik/lib/issues/505
@arox: you know that you can access eMMC with our new flash/backup tool? In case there's a script called turn-wifi-into-apmode could you please post the contents?
Thanks. That is exactly what I remember now from my past experience. The latency is not too bad, but it makes the device feel slow, since it can take a second to respond to commands. It's also bad if you're trying to control anything over WiFi that would be affected by higher latency.
Also, copied off the contents of the eMMC before I overwrote it, so I should be able to poke around it if necessary. I should also be able to post it somewhere if others want to look through it. I don't think there should be any issues with distributing it.
-
I noticed a couple of potential problems with the NanoPi Air firmware.
First, there seems to be some latency over the wireless connection. I remember having this problem on another embedded system and it had something to do with power saving mode on the wireless adapter. Does that ring any bells with anyone?
Second, I don't know how to access the sdcard. When I insert an sdcard it doesn't show any new partitions. Is there a driver that's missing?
I'm also trying to increase the number of g_serial ports and running into a problem. If I do a "modprobe g_serial n_ports=2" I get:
[ 73.413493] ep_matches, wrn: endpoint already claimed, ep(0xc0a0365c, 0xd4d65940, ep1in-bulk) [ 73.413519] ep_matches, wrn: endpoint already claimed, ep(0xc0a0365c, 0xd4d65940, ep1in-bulk) [ 73.413534] ep_matches, wrn: endpoint already claimed, ep(0xc0a036a8, 0xd4d65940, ep1out-bulk) [ 73.413547] gadget_is_softwinner_otg is not -int [ 73.413556] gadget_is_softwinner_otg is not -int [ 73.413574] ep_matches, wrn: endpoint already claimed, ep(0xc0a0365c, 0xd4d65940, ep1in-bulk) [ 73.413591] ep_matches, wrn: endpoint already claimed, ep(0xc0a036a8, 0xd4d65940, ep1out-bulk) [ 73.413608] ep_matches, wrn: endpoint already claimed, ep(0xc0a0365c, 0xd4d65940, ep1in-bulk) [ 73.413625] ep_matches, wrn: endpoint already claimed, ep(0xc0a036a8, 0xd4d65940, ep1out-bulk) [ 73.413639] ep_matches, wrn: endpoint already claimed, ep(0xc0a036f4, 0xd4d65940, ep2in-bulk) [ 73.413653] ep_matches, wrn: endpoint already claimed, ep(0xc0a0365c, 0xd4d65940, ep1in-bulk) [ 73.413667] ep_matches, wrn: endpoint already claimed, ep(0xc0a036a8, 0xd4d65940, ep1out-bulk) [ 73.413681] ep_matches, wrn: endpoint already claimed, ep(0xc0a036f4, 0xd4d65940, ep2in-bulk) [ 73.413695] ep_matches, wrn: endpoint already claimed, ep(0xc0a03740, 0xd4d65940, ep2out-bulk) [ 73.413709] ep_matches, wrn: endpoint already claimed, ep(0xc0a037d8, 0xd4d65940, ep4-int) [ 73.413728] g_serial gadget: acm/d4adb480: can't bind, err -19 [ 73.422018] WRN:L2558(drivers/usb/sunxi_usb/udc/sunxi_udc.c):ERR: Error in bind() : -19 [ 73.431161] g_serial sunxi_usb_udc: failed to start g_serial: -19
From what I've gathered, it looks like there might not be enough endpoints in the USB device. Does anyone have any experience with this?
-
I installed the latest version of the NanoPi Air firmware, and WiFi configuration works perfectly.
-
To complete the steps, after running start.sh a new drive was detected (/dev/sdd). I then dd'ed the Armbian image to /dev/sdd and power cycled the board, and it appears to have worked.
A new tty device was created, which brings up a console login. There is a wlan0 network interface, but I wasn't able to configure it because nmcli is missing. The latest version of the firmware was not available yet, so I'm using yesterday's version, which apparently doesn't have it yet.
After going though that, wouldn't it be easier to just have a small boot disk image that contains the full image and automatically dd's the image to the eMMC partition on boot?
-
Clearly I'm missing some crucial information. I wrote the fel-sdboot.img to an sdcard and booted it, connected to USB. A device came up that has the same IDs as described in the fel-mass-storage instructions, but what do I do to write the image? The page you keep referring me to stops at detecting the device. I don't see any instructions on how to then write an image file to the device. The closest I can see is "sunxi-fel write address file", but I don't know what the address should be.
-
Please keep in mind that you need an SD card with a minimal SPL on it that forces the Air into FEL mode (see here how/why) and that currently if you're using our build system to create a fresh image for the Air the nand-sata-install script doesn't work (needs some time to adjust it to get also UUID support if I understood correctly).
That was meant to burn the OS image directly to eMMC (feedback needed) and then setting up Wi-Fi would be interesting (feedback needed). Please keep in mind that it's already confirmed that the Air image can boot from SD card and works as long as Wi-Fi/BT aren't considered (since tested with NEO).
I think the part that I was missing is how to bring the NEO Air into FEL mode. Now I see that there is a fel-sdboot.img that is in that repo, which must be the missing piece. I didn't see the last sentence that mentions booting that image. Maybe that should be moved to the top of the README, since I believe it has to happen before the other parts of the README will work, right?
Once I boot that image and connect via USB, will it show another drive that I then write the provided image to?
In any case, I'll try again tonight add see what happends.
-
Please test Armbian_5.21.161016_Nanopiair_Ubuntu_xenial_3.4.112.7z. And of course both Windows and Linux are fine. Simply follow the descriptions here:
- https://github.com/zador-blood-stained/fel-mass-storage (any SBC with Armbian will do it too and sunxi-fel is already installed there)
- https://github.com/igorpecovnik/lib/issues/493#issuecomment-252751466 (to setup Wi-Fi)
I'm not sure I fully understand what I have to with this image. I booted it, and it came up just fine, then rebooted after a few minutes (not sure what that was about). Now it's booted, and it added a COM device that I'm able to log into, which is nice. I'm not sure what I do with the sunxi-fel, though.
-
If you think you have an image to test, I'm willing to test it. I don't have a Mac, but I do have Windows and Linux if Linux is required or easier to test on.
-
Thanks.
I ordered a neo and an air. I hope I will at least be able to use the armbian setup of the neo to get access to the air threw micro-usb without first playing with the iron ?
At the very least, if you have a Linux system, you should be able to mount the root FS and edit files that way.
BTW, I was talking about the default installation, not Armbian. Armbian doesn't appear to load g_ether by default either.
-
Do they load g_ether and provide a config for usb0 ?
No. The only modules loaded by default are: bcmdhd, cfg80211, and compat, and the only network interfaces are lo and (unconfigured) wlan0.
-
Nope, but we added support for AIR based on available information recently and already built test images (more or less by accident):
Unless you are able to attach a serial console to the 4-pin header it's useless to even try them out. Two questions from our side:
- is the 4-pin header to provide power and attach a serial console populated or not?
- if the eMMC pre-flashed?
Please get back to us with this information first, we will then update the NanoPi Air thread and might ask potential Air users a few questions. Thanks!
None of the headers are populated. The box comes with the headers, but they're not soldered on. I populated all the headers, connected a USB-serial adapter to the serial console and tried powering it up. I don't see anything on the console, and no LEDs blink, so I don't think there is anything installed on the eMMC.
I'll try your images and see what they do.
Where is the NanoPi air thread? I didn't see it.
Edit: It turns out that my USB-serial adapter must not provide enough current to boot. I powered from USB without an sdcard, and now the blue LED is flashing. I'm not seeing anything over the serial console, but there could be a problem with the configuration of my USB-serial. I'm not sure what the baud rate is for starters...
Edit2: I'm an idiot! I soldered a dual row 90 degree header on the console pins and the other (single) row, then a single row along the rest of the row. The back (console) row aligns with the single row, and I had the USB-uart on the wrong pins. Now I am able to power the board from my USB-uart, and it boots from eMMC with the console at 115200, so it does come pre-installed with FriendlyArm Ubuntu on the eMMC.
Edit3: The provided Ubuntu image works perfectly. It appears to be finding the wireless correctly, but I haven't tried configuring it yet.
-
Got a couple of NanoPi NEO Airs today. Anyone tried Armbian on them yet? I imagine the standard NEO image will work, but how hard will it be to install it onto the internal flash?
-
The standard for flight controllers are 30.5mm hole centers, at least that's the standard for OpenPilot boards, which pretty much defined the current standard.
We already contacted FrendlyArm to see if they might be considering building such a board, and they say they have no plans, but I suspect if they hear enough interest it might spur them on to doing something.
I (just yesterday) designed a carrier/breakout board just for such a purpose. I already found some things that I plan to change in the design, but I think it's going to just barely work. The intent is to have multiple options for connecting to existing flight controllers (UART, SPI, USB) to experiment with using the NanoPi for the higher-level control algorithms.
-
I know how to work with GPIO though the /sys interface, but that's not fast enough for my application. Is there a faster interface for working with GPIO on the H3, similar to the fast GPIO on the RPi. I believe fast GPIO on the RPi manipulates GPIO though a memory map interface. Is that possible with the H3. Has anyone done it?
Composite video framebuffer on OPi 0+2
in Allwinner sunxi
Posted
I should add that this is the H3 version of the board.