**** BEGIN LOGGING AT Thu Mar 07 02:59:57 2019 Mar 07 03:00:55 Not me. Mar 07 12:01:56 hello Mar 07 12:02:31 I need a photo of BeagleBone Pocket Mar 07 12:02:46 o be placed in the online store Mar 07 12:03:17 https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual only BW photo Mar 07 12:03:41 it's called the PocketBeagle, not "BeagleBone Pocket" Mar 07 12:05:47 ok Mar 07 12:10:37 Why the Beaglebone foundation does not provide colorful photos of Pocket Beagle? Mar 07 12:12:59 https://beagleboard.org/pocket Mar 07 12:13:03 is that not enough ? Mar 07 12:15:52 No, small resolution, one photo (only from above) with a coin, is not suitable for publication in the online store Mar 07 12:16:18 paatryk93: so you actually expect people to provide the full assets for your sho for free, right Mar 07 12:16:23 good plan. Mar 07 12:20:17 Dlaczego w System-Reference-Manual https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual w sekscji 10.0 Additional Pictures są zdjecia czarno biale a nie kolorowe nie rozumiem tego :/ Mar 07 12:20:23 Why in System-Reference-Manual https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual in sex 10.0 Additional Pictures are pictures in black and not colored do not understand this: / Mar 07 12:20:33 Bye Mar 07 12:21:10 1, 2, 3, …, no profit Mar 07 12:22:40 Hi all! I'm investigating the power consumption of the BeagleBone Black. Mar 07 12:22:42 I power the board via VDD_5V and DGND (pins 7+8 and 1+2 on the cape headers). Mar 07 12:23:08 In On state, the board consumes 0.5 A (idle) to 0.7 A, which seems reasonable. Mar 07 12:24:04 But if I turn it off (by "poweroff" on the Linux console), I still get 0.294 A after the Power LED became dark. Mar 07 12:24:45 Why is the power consumption in Off state so high? Mar 07 12:26:17 I have an LCD display adapter (4D Systems BBB 4DCAPE Adaptor) and a custom-made CAN transceiver board. Mar 07 12:26:36 OK, probably the CAN transceiver is responsible for the high power in Off state, sorry for asking... Mar 07 12:45:54 For your reference: My selfmade power / CAN-transceiver adapter shorted VDD_3V3 to VDD_5V (but somehow the BeagleBone survived :)). So it still applied power to the CAN transceiver after shutdown. Mar 07 15:44:09 m Mar 07 18:03:09 hello, I am trying to configure beaglebone green Mar 07 18:03:35 When I run the installer, none of the device drivers install Mar 07 18:07:01 jkridner[m]: I will be at SCaLE tomorrow afternoon Mar 07 18:08:38 jkridner[m]: I am liking the Beaglebone AI, I shared it with some coworkers and they can see it being used on projects, particularly on some vision/object recognition Mar 07 19:57:03 I have a new BBBW and am having BlueTooth issues. When using hcitool inq command it works for a short time, then I start getting 'Inquiry failed.: Device or resource busy'. It starts in that mode until I reset the device. Same behavior with both the internal and an external adapter Mar 07 19:57:08 Any thoughts? Mar 07 19:59:35 "with both the internal and an external adapter" ? what do you mean? Mar 07 19:59:54 you mean powered via usb or 5v adapter? Mar 07 20:01:31 BBBW has integrated BlueTooth. Same problem with it or an added BT dongle Mar 07 20:01:36 ah Mar 07 20:01:45 so it's not a hardware issue but a software-related issues Mar 07 20:01:56 So I suspect Mar 07 20:02:00 some googling suggests that hcitool is deprecated by bluez Mar 07 20:02:12 I installed latest Debian build Mar 07 20:02:13 https://wiki.archlinux.org/index.php/bluetooth#Troubleshooting Mar 07 20:02:47 maybe hcitool meddles with the bluetooth device in a low-level way that conflicts with simultaneous use of it by the bluez stack? Mar 07 20:03:49 I think it is a part of the bluez suite Mar 07 20:03:57 it is, but https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=b1eb2c4cd057624312e0412f6c4be000f7fc3617 Mar 07 20:04:06 "The behavior of the deprecated tools may be unstable or simply don't work anymore. Mar 07 20:04:47 so if you're having problems with hcitool, my assumption based on this commit would be that the solution is not using hcitool Mar 07 20:06:19 It appears there is not direct replacement (short of writinbg code) Mar 07 20:06:25 exactly what I suspected: "All the tools using raw socket shall be considered deprecated, these tools may interfere with the so called Management interface since they can alter the controller state in a way that other applications cannot detect." (from: https://www.spinics.net/lists/linux-bluetooth/msg70489.html ) Mar 07 20:08:29 based on what I read, bluetoothctl seems to be the main tool for bluetooth-related stuff Mar 07 20:08:46 Interestingly, all the examples in the first link use hci* commands Mar 07 20:09:23 OK - I'll dig into btmon and the others to see if they can replicate what I need - thanks Mar 07 20:09:25 you mean in the Troubleshooting section with the warning at the top "This article of section is out of date" ? Mar 07 20:09:30 *or section Mar 07 20:10:23 you probably first want to look at bluetoothctl, it seems to be the first thing that gets mentioned (both earlier on that wiki page, and by other sources) Mar 07 20:11:23 also for things that have a dbus interface but no commandline utility, you can use busctl to perform dbus calls from the commandline Mar 07 20:13:51 Cool - I'll dig around a bit on these. Mar 07 20:20:16 e.g. try busctl tree org.bluez or busctl introspect org.bluez /org/bluez/hci0 Mar 07 20:21:26 of course poking directly at dbus should be a last resort in case adequate tools indeed are lacking :P Mar 08 00:51:33 O **** ENDING LOGGING AT Fri Mar 08 02:59:56 2019