**** BEGIN LOGGING AT Thu Mar 15 03:00:02 2018 Mar 15 04:23:35 Hi All, Anyone know how to test how a beaglebone board is powered? I have a board powered via the Cape and connected via the USB port. The board is smart enough to take power from the cape over the USB port but I want to test if the cape is powered or not from the beagle board. Seeing the beagle board can start from USB power. Mar 15 04:30:52 darn, that was an interesting question, too Mar 15 05:00:09 sudo i2cget -f -y 0 0x24 0x0a # bit 3 Mar 15 05:02:09 at least, bit 3 indicates valid power is present on the barrel connector / p9.05-06 Mar 15 05:05:52 they still haven't gotten the PMIC into the power supply class to expose all those things? Mar 15 05:09:08 the tps65217 driver in 4.14-bone is still garbage Mar 15 05:11:32 there's a power_supply class tps65217_charger driver, but it's just for the battery charger Mar 15 05:11:53 and it's stupid too, it actually changes the NTC_TYPE to its non-default value Mar 15 05:12:02 something the datasheet explicitly advises against Mar 15 05:12:33 (since it means you can't charge while powered off) Mar 15 06:13:56 Hi, where can i get the documentation about kernel command line,such as : capemgr.disable_partno Mar 15 06:14:41 This works in kernel 3.8.13, in uEnv.txt. What is the equivalent command for kernel 4.15 Mar 15 06:14:59 for boot.txt Mar 15 06:16:11 there is no capemgr Mar 15 06:16:29 you configure overlaysys through uenv Mar 15 06:16:48 and there is a userspace way to change pinmuxing Mar 15 06:17:00 Thanks for the respond. Are you talking about kernel 4.15? Mar 15 06:17:21 any newer kernel currently available Mar 15 06:17:37 Yes, as far as i know capemgr is the userspace Mar 15 06:17:45 no Mar 15 06:18:08 May I know what is the userspace, any link or documentation would be apprciated Mar 15 06:19:01 There is no uEnv.txt exist as you metioned Mar 15 06:19:14 only boot.txt Mar 15 06:19:31 config-pin is the tool Mar 15 06:19:46 do you have an old image installed? Mar 15 06:20:08 this requires up to date u-boot Mar 15 06:20:50 I have old uboot installed and running well, migrating to newer kernel Mar 15 06:21:01 the configuration all mes up Mar 15 06:24:08 I'd recommend to do a clean reflash Mar 15 06:31:57 checkitout: installing such a new kernel onto an overall ancient system is probably not a good idea Mar 15 06:34:35 but assuming you use a kernel that still has capemgr (it's deprecated but I'm not sure if it's already removed in latest -bone kernels), install the latest overlays in /lib/firmware, and change capemgr.* to bone_capemgr.* in /boot/uEnv.txt ... it *might* work Mar 15 06:35:29 the replacement mechanism (u-boot overlays) requires updating u-boot and a substantially different /boot/uEnv.txt, in addition to a sufficiently recent kernel and overlays Mar 15 06:54:09 checkitout: I just checked, 4.14-ti and 4.14-bone still have capemgr, 4.15-bone does not Mar 15 06:54:56 so either it just hasn't been forward-ported (4.15 isn't an LTS kernel) or 4.14 is the last kernel with capemgr Mar 15 08:41:00 Hello everyone Mar 15 08:41:14 I have a question about Beaglebone Black and 1080i video output Mar 15 08:41:23 already discussed it ones here and got a few more questions Mar 15 08:41:30 anybody familiar with this topic? Mar 15 08:41:48 just ask, and if somebody knows you will get an answer Mar 15 08:42:39 Does the Beaglebone Black support 1080i video ouput? We need 1080i50 to be precise. Mar 15 08:43:24 Last time, someone said that it doesnt. But one of our developers send me this message Mar 15 08:43:25 The short answer to your question is: It seems theoretically possible for the BBB to output 1080i50, although I haven't seen it explicitly mentioned in the documentation. In terms of GPU power, it would be difficult to understand why the BBB designers would use a GPU incapable to rendering a 2D scene at such a standard resolution. This shows how to change the resolution: http://blog.machinekit.io/2013/06/force-beaglebone-black-hdmi-r Mar 15 08:43:54 This shows the values to set to the "video" kernel parameter: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt So we should be able to set it to something like that: `video=HDMI-A-1:1920x1080@50i` Mar 15 08:44:27 so.... does the Beaglebone Black support 1080i50 using HDMI video ouput? Mar 15 08:44:36 bjoern: its not a decision that the BBB designers have, because the GPU is integrated in the soc and cannot be changed Mar 15 08:45:01 given the repots here, i would think the answeris no: Mar 15 08:45:03 https://elinux.org/Beagleboard:BeagleBoneBlack_HDMI Mar 15 08:46:17 LetoThe2nd: Thank you for the answer. Mar 15 08:55:51 AFAIU you can get 1080p24 or such Mar 15 09:00:30 if it's a one off thing, you can probably use something like one of those *Fury devices to double the frame rate or such Mar 15 09:00:58 obviously that won't increase the actual frame rate Mar 15 09:32:18 it doesn't support interlaced to begin with Mar 15 09:32:57 (and this doesn't have anything to do with the gpu) Mar 15 12:08:36 zmatt: how's everything? do you have an idea of max power consumption of bbb with hdmi etc enabled but no capes? Mar 15 15:25:40 microdevel: the hdmi framer specifies typ 60 mW max 75 mW for 720p60 Mar 15 15:25:48 oh, you left Mar 15 20:46:48 Hi everyone, can you recommend any specific modules for the X15 for RS485 input? Mar 15 21:25:51 aaand gone again Mar 16 00:28:34 I need a consultation. Just got BeagleBone green wifi, grove cape and temp/humidity sensor. Sensors suppose to work both with 3v and 5v. Does it matter to what grove port I attach the sensor? Mar 16 00:29:12 what sort of sensor is it? Mar 16 00:29:45 this guy http://wiki.seeed.cc/Grove-TemperatureAndHumidity_Sensor/ Mar 16 00:31:31 ah, dht11 Mar 16 00:31:52 I am a bit confusing about other aspects. First, they say in the description: sensor provides a pre-calibrated digital output. Then they instruct to attach it to analog port. How does that work out? Mar 16 00:32:49 I think that's just how the pin is labeled, but it's used as digital gpio Mar 16 00:33:19 labeled on some arduino model I mean Mar 16 00:33:45 is the DHT11 I2C? Mar 16 00:34:26 well, it doesn't use some normal protocol like i2c, it uses some awkward digital protocol kinda like 1-wire but iirc not compatible with it Mar 16 00:35:09 so it's gonna have to be bit-banged with a gpio, hence it shouldn't matter which grove port you use Mar 16 00:36:49 there's a dht11 kernel driver Mar 16 00:39:29 which of course is going to be annoying to use since it'll require a DT overlay and conflict with cape-universal Mar 16 00:39:53 hmmm thought the grove ports are I2C only Mar 16 00:40:06 since when does the beaglebone have "i2c only" ports? Mar 16 00:40:11 and no, grove is all sorts of things Mar 16 00:40:21 you have grove buttons, grove leds, etc Mar 16 00:40:26 'k Mar 16 00:41:01 the bone is flexible... thought those 4 pin connectors were power, i2c, and gnd? Mar 16 00:41:08 * ds2 goes to look Mar 16 00:41:15 the grove cape has two connectors with i2c support, two with uart support, two with adc support: http://wiki.seeed.cc/Grove_Cape_for_BeagleBone_Series/ Mar 16 00:41:25 power, ground, and two signal pins that vary Mar 16 00:41:57 http://wiki.seeed.cc/BeagleBone_Green/ <-- uart/i2c Mar 16 00:42:26 Nepenthes: the adc ports on the grove cape aren't suitable Mar 16 00:42:36 Nepenthes: any other should be fine Mar 16 00:43:02 where "fine" doesn't include the general awkwardness of these sensors ;) Mar 16 00:43:43 zmatt: he's got the BBGW Mar 16 00:44:16 with grove cape is what he said Mar 16 00:45:11 oh nice that pinout table for the grove cape on the wiki is definitely wrong Mar 16 00:45:42 the grove ports on the BBGW itself are fine too Mar 16 00:47:12 Hmm? Mar 16 00:47:13 I need a consultation. Just got BeagleBone green wifi, grove cape Mar 16 00:47:14 +and temp/humidity sensor. Sensors suppose to work both with 3v and 5v. Does Mar 16 00:47:14 +it matter to what grove port I attach the sensor? Mar 16 00:47:59 Oh both Mar 16 00:48:03 nevermind Mar 16 00:48:05 they're equivalent to... P9.19+20 for the I2C port (same as J5 on grove cape) and P9.21+22 for the UART port (same as J6 on grove cape) Mar 16 00:50:41 actually, the I2C port on the BBGW and J5 on the grove cape will default to i2c Mar 16 00:51:27 so uh, use J1, J2, or J6 Mar 16 00:52:26 Nepenthes: ehm, are you even still here? Mar 16 00:56:59 last spoke 24 minutes ago Mar 16 00:57:09 I am aware of that Mar 16 00:57:31 which is also why I'm not spending any further braincell activity on this Mar 16 00:57:53 sounds good Mar 16 01:30:45 I am here Mar 16 01:30:50 just got back Mar 16 01:31:19 my cape is for bb green wifi from seeed Mar 16 01:31:55 Can we conclude that it generally safe to plug it anywhere? Mar 16 01:33:24 my cape has 2x ADC. I must avoid those with this sensor, is it correct? Mar 16 01:33:47 Not sure which ones though! Mar 16 01:34:04 folks, I appreciate your support) Mar 16 01:36:03 4 labelled as i2c, 4 as digital IO which is GPIO?, 2 uart and two analog. This means I am only limited by those two analog ones? Mar 16 01:37:08 It says on the packaging of the sensor that it is based on DHT1 Mar 16 01:37:18 if it matters, of course Mar 16 01:42:12 I see now, ADC = analog digital converter Mar 16 01:43:28 So I am concluding I have only two ports available. What happens if I plug incompatible sensor? Mar 16 01:44:43 zmatt, what happens if I plug it to ADC? Mar 16 01:45:11 Hello! Mar 16 01:46:48 Analog! Mar 16 01:52:40 Now cleared all my doubts Mar 16 01:52:44 thanks Mar 16 01:56:03 Nep: What are you doing? Mar 16 01:56:32 You got a Cape or something? Mar 16 01:59:02 <<<<<< on break Mar 16 02:09:32 Yup, bb green wiwi + grove cape+dht11 Mar 16 02:09:58 was wondering where not to plug the sensor and potentially could happen if ever would. Mar 16 02:39:07 Nepenthes: if you've plugged it into the adc, then you've plugged it into the adc Mar 16 02:39:11 :) Mar 16 02:40:06 normally that would actually be fairly hazardous since the adc inputs of the beaglebone accept max 1.8v, but the grove cape already protects the pins against overvoltage Mar 16 02:41:30 but mainly it's just very inconvenient to try to receive a digital signal via an analog input Mar 16 02:42:03 the i2c2 connector should probably be avoided since it's configured for i2c by default Mar 16 02:42:12 the other three are fine and should default to gpio use Mar 16 02:45:25 (connecting the sensor to a port that's configured for i2c wouldn't work) **** ENDING LOGGING AT Fri Mar 16 03:00:01 2018