arox

I can decode HTSP from tvheadend with vlc on a pi zero at 1280x1024 but need something more powerfull for 1920x1080. (PI3B+ do the job so I think a PI3A+ would do). Can you give me some advice for small device that can do it ? Do you think a Rock64 could transcode DVD mpeg2 to h264 on the fly ?

I never manage to have g_ether working with mainline kernel on H3 device. Last time, I thought I had it working with FA distro ... but only one end was receiving packets. So my nanopi -air is on the shelf and I use pi zero W (s).

May come for bad addr to name resolution. Check your resolver.

Maybe @igor could have a look because I think no external usb sound card can run ?

Try : zcat /proc/config.gz | grep -i USB_AUDIO If you dont see CONFIG_SND_USB_AUDIO=m then I think you may need to recompile the kernel ...

Can you see (lsmod) the kernel module 'snd_usb_audio'. (Try modprobe if not)

I understand you use a bench or enterprise PSU with high amperage, voltage regulation and security ... So why should you be bothered by an 1,2 m USB cable ? Cant you use another cable, short and with big wires ? What I always asked myself is the resistivity of the contacts on micro USB and how much it can change from one plug to another or over time. I spent the day trying to fix my old audio amp and speakers (more than 20 years) : the potentimoeters are dead, the resistivity change with the charge (or when I adjust them) and so the sound is horrible. Imagine what happend to your board if some crappy contact do the same when the processor demand a power burst ! The response is that the board can crash anytime but more probably when doing heavy computation or accessing disk or network ...

try : hciconfig hci0 up hcitool dev or hciconfig hci0 reset hciconfig hci0 up hcitool dev or ps -ef | grep hciattach if not present, respawn hciattach process (check command line after boot) then re-up hci0 there should be a gpio for hard reset but it depends on uboot, DT and kernel version ... How to restart bluetoothd depends on system and version. You may need to re-up hci0 after restarting bluetoothd and handle hciattach yourself before starting bluetoothd : because it is hardware dependant, it is always a dirty tweak in startup scripts ... You should provide some information about SBC, ap6212 rev, Armbian version, Bluez version, firmware version (downloaded by hciattach) ... So somebody may perhaps help ...

I suppose that some manufacturer spare money by not registring an address. Nanopi air should anyway have one. For my part, what I donnot understand is the 115200 in hciattach command : AP62XX is a serial module, and all BT traffic is routed in HCI over serial communication link. So how could someone reach 3 Mb/s of data rate over a 115200 b/s line ?!?. I always change this for 1500000. Otherwise an a2dp link drop packets for example. Another funny thing is the usage of 11:xx...etc or 43:xx...etc addresses. By default the system load a BNEP module, but dont try to configure a NAP acces point with that : it will try to use the address as an ethernet address in BNEP emulation - and fail with bad reporting because an address with an even first byte is illegal for Ethernet. I use a Nanopi neo 4.14.14 kernel with btusb dongle to create ppp/rfcomm links. I previously used a Nanopi air or a BPIM2+ 3.4.17 kernel for BNEP links. With nanopis or bpi I crash the kernel every other day. So did you achieve some stability with that ? Anyway, with BR/EDR mode and bluez, I need to reset the controller periodicaly because it became anable to create basic link (ACL) after some time when forming multiple piconet. So I also experiment with BLE. I tested Bluepy - wich can handle "central" (but not peripheral) role in python. But I doubt to achieve stability and low latency in connected mode. So I am now developping my own trivial mesh protocol by advertising/scanning transmission with gatt/paypal in golang on RPI (and chip with some tweak in scan report demux) ... I didnt try bleno/noble. It seems to shunt BLUEZ insane routing through dbus/xml unstable/undocumented messaging API (as do also gatt/paypal) and handle itself the HCI interface. I am not sure about the difference in socket interface in both implementation ? I am not sure of the role of 4343A0.hcd or so files downloaded by hciattach. If this is the firmware for BT controller, there certainly is a lot of bugs in this and we need more robust version ?

Well, I repaired by soldering 2 RPI and destroyed by soldering a nanopi air. And that is just remarkable seing the number of times I found my boards crashed and boiling hot, generally because of network failure. (wifi, bt ... )

I suppose you have a host B that want to join Internet through A (bananapi) and Router R. In that case, B send packets to A, A forward packet to R, R forward to Internet. But the reverse path should be OK : R send packet to A when Internet reply to B. The normal, basic configuration should be that A - is configured as router (ip_forward = 1) - present 2 different neworks on etho and wlan0 - forward traffic by default to R (default route) But B should have default route to A and Router should have a route to B or network of B threw A. But this is just basic configuration, you can also bridge or subnet/proxy or nat or ... If you use bridging, wlxx interface should not have an address but be associated (with eth0) to a bridge (install bridge-utils) and forget about ip_forward or iptables

Does your router know it should send to bananapi ?

You didn't tell what BT device you use and what usage you intend to do with BT. The BT chips on board (AP6212 for example) need an "hciattach" process - sometimes tricky with the init system. USB dongle need not. You probably will need a bluetoothd process (and check that it does not put your "hci0" device down). And then you will need the dbus running (and configured) -- even if BT is the only app needing that sort of thing on a "minimal system".

"Thanks for the tip on losetup" With "losetup -o offset" (and --sizelimitzelimit if needed) you can do a resize2fs on an image disk file and truncate it (and update part table on file with fdisk). Not that easy to calculate the size for truncate -- I got 102400 too short, and I havent find why untill now. "Having a disk full of large images is wasteful in many different resources, the small files are faster and easier to administrate." "tar zcvf - . | ssh svghost dd of=/svg/svg.tgz bs=1M" is your friend "mount -o bind / /mnt" is also your friend, BUT beware of saving a running system for database constistency !

Compress your backup ! You only have problem when you want to restore on a card with lower capacity. If this is the problem, you need [to learn] linux tools to handle linux data ! (tar, dd, losetup, fdisk, parted, mount ...)

"I have test the router and it only need RX/TX/GND to work." Then beware of a security breach ! I will never buy such sort of device ! What use to force users to put passwords everywhere if you leave the session open for the next who gets hand on console of the major telecommunication equipments !

"since I can use the converter from RS323 to TTL, I think it is working. it just can not convert from TTL to RS232." There is no "from" / "to" usage ! You transmit characters in both direction whatever you are doing with the converter : when you type a character in a serial console, it is sent to the other end and the othe end send it back so it is displayed on screen "could anyone test his converter if control the router/switch via SBC works?" "control" is just an application. If you can "control" the SBC from PC, then the hardware is OK because that mean you can transmit AND receive characters - and both ends are transmitting and receiving. So your problem is only software. Your software needs only to take into account the fact that YOUR RS232 cable transmit or shunt the control wires and the flow control wires - or not. If we donnot use the same software, we can have our app working and you not. If I understand well, "control" mean you want to acces the "console interface" of the router. Then the application is a shell on the router and minicom on SBC. And you cannot modify the software ! So you need to use a good RS232 null modem cable because that sort of device use DTR/DSR control.

Yes, my FriendlyArm converter is cabled as DTE (without DTR/DSR/DCD). So I would use a "Full hanshake" or "No handshake" "null modem" cable to connect to a PC or a router.

I bought the FriendlyArm converter to get access to my "legacy" PC on console port ... but I never bothered to use it ! If you can use minicom on the PC to send and receive characters from the SBC, then your links and the converter is working. If you intend to get a login prompt from the PC using minicom on the SBC, then you may have a problem with DCD, DTR/DSR. Because of security, a login should be permitted and a session maintained on serial line (by default) only if the Carier Detect (DCD) is asserted and maintained - and Data Set (=modem) Ready (DSR) received (the session is closed if the modem hangup)

How is your converter powered ? (The converter need to provide positive/négative tensions - theorically 15V for the PC). And check you really provide 3.3V for the sake of your SBC ! "RS232" has no "initialisation" phase but some circuit (DTR, DSR, RTS, CTS, DCD ...) to coordinate the transmission on Tx, Rx circuit. You need to program drivers at both end to ignore the flow control circuits or have them shunt (RTS with CTS for the flow control, DTR and DSR with DCD for the peer detection)

I would like to test or reinstall my nanopi air, but I can only find download for "neo core / air" "testing version" with mainline kernel. In fact I was looking for an uptodate uboot/kernel for legacy kernel or a "usable" version with mainline - that is for me - with an asix module and working WIFI / BT.

Add 2 branches to make stereo glasses

If I understand well ... You fail to clone a Linux image with a Windows/Mac software and complain Linux is bad ?!? Linux is not user friendly very much (for beginners). It was from the start a unix derivative and a study project from a student. And SBC are not user friendly - and SBC other than RPI are even less. So what use complaining and why not instead buy a full Intel (tm) with Windows (tm) computer ? And if sofware for your SBC is not as good as expected, why not complain to the manufacturer which sell "development cards" and rely on "developper community" without helping them in return ?

Are you powering the board through Dupont connectors ?

Maybe there are good and less good thermal pads ... Nevertheless, I remember the old times and the AMD Duron (the cheap version of Athlon - 100W to evacuate). If the heatsink was badly assembled, you could be certain to burn the proc ! BTW : have someone tried an odroid XU4 with passive heatsink ?