FranckM

Members
  • Content Count

    11
  • Joined

  • Last visited

About FranckM

  • Rank
    Member

Recent Profile Visitors

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

  1. Hi Replying to myself to keeping trace and maybe help someone. So after building a new kernel with CONFIG_BT_RFCOMM_TTY=Y (using a VM), I installed the new packages using build debs : dpkg -i armbian-config_19.11.4_all.deb dpkg -i armbian-firmware_19.11.4_all.deb dpkg -i linux-dtb-current-rockchip_19.11.4_armhf.deb dpkg -i linux-image-current-rockchip_19.11.4_armhf.deb So now my tinker uses : Ubuntu Bionic with Armbian Linux 5.3.18-rockchip and RFCOMM TTY is working
  2. root@astrotinker:~# cat /boot/config-4.19.69-rockchip |grep -i rfcomm CONFIG_BT_RFCOMM=y # CONFIG_BT_RFCOMM_TTY is not set Please can you enable this module ?
  3. Hi, It seems I'm not the only one : https://forum.radxa.com/t/rfcomm-failures-in-ubuntu-server-image-and-debian-desktop-image/375 If linux-rockchip64-current.config is the right configuration for my Tinker Board, then RFCOMM is set to # CONFIG_BT_RFCOMM is not set Trying to buil da new kernel root@armbuild:~/build# ./compile.sh [ o.k. ] Create example config file using template [ config-default.conf ] [ o.k. ] Using config file [ /root/build/userpatches/config-example.conf ] /root/build/lib/main.sh: line 136: dialog: command not found [ error ] ERROR in function source [ main.sh:138 ] [ error ] No option selected [ o.k. ] Process terminated
  4. Well, no, I did not compile the kernel. I think last update (apt upgrade) is from 13/11/19
  5. Dear all, I'm looking for help on having RFCOMM TTY working on a Tinker Board S. Any help will be welcome !! Using : Ubuntu Bionic with Armbian Linux 4.19.69-rockchip # uname -a Linux astrotinker 4.19.69-rockchip #5.95 SMP PREEMPT Mon Sep 2 07:34:36 CEST 2019 armv7l armv7l armv7l GNU/Linux I'm trying to have rfcomm tty working with a bt HC-05 dongle, but RFCOMM TTY seems not to be available. The BT HC-05 is well reconized and connected: # bluetoothctl [NEW] Controller 80:C5:F2:46:E2:C2 astrotinker [default] [NEW] Device 00:14:03:06:04:ED HC-05_TIC Agent registered # systemctl restart bluetooth.service # systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-11-25 22:23:51 CET; 3min 30s ago Docs: man:bluetoothd(8) Process: 5198 ExecStartPost=/usr/bin/rfcomm bind rfcomm1 00:14:03:06:04:ED (code=exited, status=0/SUCCESS) Main PID: 5196 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4784) CGroup: /system.slice/bluetooth.service └─5196 /usr/lib/bluetooth/bluetoothd -E Nov 25 22:23:51 astrotinker bluetoothd[5196]: System does not support network plugin Nov 25 22:23:51 astrotinker bluetoothd[5196]: Bluetooth management interface 1.14 initialized Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.73 path=/MediaEndpoint/A2DPSource Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.73 path=/MediaEndpoint/A2DPSink Nov 25 22:23:51 astrotinker bluetoothd[5196]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Nov 25 22:23:51 astrotinker bluetoothd[5196]: RFCOMM server failed for :1.73/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: Nov 25 22:23:51 astrotinker rfcomm[5198]: RFCOMM TTY support not available Nov 25 22:23:51 astrotinker systemd[1]: Started Bluetooth service. # journalctl -u bluetooth.service -- Logs begin at Mon 2019-11-25 00:30:28 CET, end at Mon 2019-11-25 22:23:52 CET. -- Nov 25 00:30:35 astrotinker systemd[1]: Starting Bluetooth service... Nov 25 00:30:35 astrotinker bluetoothd[1466]: Bluetooth daemon 5.48 Nov 25 00:30:35 astrotinker bluetoothd[1466]: Starting SDP server Nov 25 00:30:35 astrotinker bluetoothd[1466]: kernel lacks bnep-protocol support Nov 25 00:30:35 astrotinker bluetoothd[1466]: System does not support network plugin Nov 25 00:30:35 astrotinker bluetoothd[1466]: Bluetooth management interface 1.14 initialized Nov 25 00:30:35 astrotinker rfcomm[1467]: RFCOMM TTY support not available Regards Franck
  6. Using last Armbian Ubutuntu Bionic build (Armbian_5.59_Tinkerboard_Ubuntu_bionic_next_4.14.67) the Tinker is know booting powered using GPIO pins !
  7. Hi According to this thread on Tinker Board forum https://tinkerboarding.co.uk/forum/thread-1877-post-7965.html#pid7965 Hi, maniolias Since there is a bug on V2.0.4 u-boot, it will cause un-boot when powering by 40 pin GPIO, it needs the below commit to fix which is included in the v2.0.5 u-boot. https://github.com/TinkerBoard/debian_u-boot/commit/879646d1d6c714335eb065a404ae033261236213 So please use the v2.0.5 u-boot a fix is needed for the Tinker OS. Is this fix: https://github.com/TinkerBoard/debian_u-boot/commit/879646d1d6c714335eb065a404ae033261236213 applied (appliable ?) to Armbian Stretch or Bionic ?
  8. Well, I tryed with a AC/DC 5V 3A power, which voltage is correct, connected on pins 4 (vcc) and 6 (gnd) and the board does not boot !? It seems Tinker Board S can not be powered from the GPIO anymore ? Just made a support request to Asus
  9. Hi Tony, Yes it will. I think the power I use is not giving enough current. To correct my previous post, I of course did not use pin 1, but pin 2 or 4 for vcc.
  10. Hi everyone ! First post here, glad to meet you. I'm trying to powering up a Tinker Board S using pin 1 and 5 with a step down buck convertor. The main power is coming from a 12v ac/dc convertor connected to the dc/dc buck convertor set to 5V and 3A. The card just looping trying to boot. Did anyone experience this issue ? Do you have any advice on what step down buck convertor tu use ? Thanks