**** BEGIN LOGGING AT Sat Aug 02 03:00:00 2014 Aug 02 11:47:43 does BBB support wake on lan? Aug 02 12:09:53 Laurenceb__: I don't think so, but the answer will be in the SRM and the TRM Aug 02 12:15:39 Laurenceb__: do I understand your remark of earlier right in that linear regulator U4 stays enabled after shutdown? Aug 02 12:17:08 I'm guessing you have BBB rev A6 or later? (I have A5A which predates changes made to U4 enable) Aug 02 12:19:22 (and that you fixed it by pulling down U4's EN input?) Aug 02 12:24:55 yes Aug 02 12:25:00 i have A6 Aug 02 12:25:35 i was wondering if it was a deliberate decision to allow WOL Aug 02 12:25:40 but it doesnt look like it Aug 02 12:26:31 so ive got VDD_AUX -> 100nF and 100k in parallel -> U4 EN pin -> 200k ground Aug 02 12:27:31 there is lots of hysteresis on U4 enable but VDD_AUX only swings from 3.3v to 1.2v Aug 02 12:27:37 since the implications are pretty bad: it means that 3V3B stays on while all other power rails are off by leaking enough current through I/Os back into the 3V3A supply to keep it high enough for the regulator to stay enabled, even with the LDO's discharge to ground Aug 02 12:27:47 VDD_AUX isn't used as EN since A6 Aug 02 12:28:01 hmmm Aug 02 12:28:12 3V3A is the enable Aug 02 12:28:24 that's the main 3V3 supply for the CPU Aug 02 12:28:38 that 1.2V is leakage through protection diodes and such Aug 02 12:28:45 i should check my board, its not here atm Aug 02 12:29:35 I'll measure my board in a bit, but VDD_AUX has no reason to stay at 1.2V: it only connects to the power led and (pre-A6) U4's enable Aug 02 12:29:35 im looking at BBB revision C schematic here Aug 02 12:29:48 yeah Aug 02 12:29:54 same on my board Aug 02 12:30:11 and the LDO supplying it has 360 ohm resistor to ground when disabled Aug 02 12:30:13 but the way the PMIC works makes it hard to turn off aiui Aug 02 12:30:26 no Aug 02 12:30:27 it looks like its outputting regulated 1.2v Aug 02 12:30:29 no Aug 02 12:30:30 hmmm Aug 02 12:30:45 i dont know whats wrong then, but my board works ok now Aug 02 12:31:00 oh Aug 02 12:31:11 just checked a photo of my board, its rev B6 Aug 02 12:31:25 I'm looking at rev C schematic, it has VDD_3V3A as EN for U4, not VDD_3V3AUX Aug 02 12:31:44 change log notes for A6: 1. Moved the enable for the VDD_3V3B regulator to VDD_3V3A rail. Aug 02 12:31:55 ah Aug 02 12:32:02 that sounds like a good change Aug 02 12:32:09 except it isn't Aug 02 12:32:14 oh? Aug 02 12:32:31 since now 3V3B is kept alive even when all other power is off Aug 02 12:32:31 what is the problem with that? Aug 02 12:32:37 ah Aug 02 12:32:39 lolz Aug 02 12:32:46 due to power leaking through protection diodes back into the 3V3A rail Aug 02 12:32:54 which is a sure way to violate a chip's absolute maximum ratings :P Aug 02 12:33:00 so it ends up having the same problem Aug 02 12:33:05 very interesting Aug 02 12:33:29 so if my assessment is right, this is a very serious hardware bug Aug 02 12:33:48 yeah just a bit lol Aug 02 12:33:55 well i have a fix for B6 at least Aug 02 12:34:40 U4 has lots of hysteresis, needs <0.4v to go low (disabled) and >2v to go high (enabled) Aug 02 12:34:49 the R C network achieves that Aug 02 12:35:04 but basically you connected it to VDD_AUX again? Aug 02 12:35:25 it was already on VDD_AUX as i was modding a B6 board Aug 02 12:35:34 B6 is already 3V3A as EN Aug 02 12:35:47 A5C was the last to have it on AUX Aug 02 12:36:02 oh shit Aug 02 12:36:08 ive confused myself totally Aug 02 12:36:18 lolz Aug 02 12:36:33 I'll measure my A5A to verify it shuts down properly there Aug 02 12:37:27 maybe i have an A6 board Aug 02 12:37:35 its at work lol :P Aug 02 12:37:35 also, wake-on-lan is definitely not available Aug 02 12:37:43 ok Aug 02 12:37:51 i did wonder if this was a feature :D Aug 02 12:38:25 or well, the cpu could enter some low-power state of course, but the ethernet subsystem and most of the device would need to remain powered Aug 02 12:38:37 yeah... as it does :P Aug 02 12:39:03 ok, let's see.. where's that U4... Aug 02 12:39:21 ah there Aug 02 12:39:22 yeah i think i got confused, i'll make some organised notes on monday, hardware is at work Aug 02 12:39:44 well it seems pretty obvious to me, I don't see any other explanation Aug 02 12:39:57 ok Aug 02 12:40:02 especially since a disabled LDO activates a 360 ohm discharge resistor to ground Aug 02 12:40:20 so no way that rail is staying at 1.2V without significant current injection from elsewhere Aug 02 12:40:35 i see Aug 02 12:40:50 so you measure 1.2v on pin 1 of U4 ? Aug 02 12:41:17 no, that's what you said Aug 02 12:41:19 in shutdown Aug 02 12:41:32 I'm about to measure my board, but I have A5A so I'm expecting a clean shutdown there Aug 02 12:41:37 if you shutdown what is the voltage on pin1 of U4 Aug 02 12:41:42 ok Aug 02 12:42:04 i never realised there were so many board revisions Aug 02 12:43:22 will take a look on monday :P, R C fixed my revision, whatever it is Aug 02 12:48:51 interesting... my regulator's definitely shutdown Aug 02 12:49:12 but Aug 02 12:49:48 my SYS_5V measures at 0.777 V Aug 02 12:51:38 the battery power switch hardware is probably partially on Aug 02 12:52:03 I'm checking whether it's supposed to be on or off during shutdown Aug 02 12:52:08 my SYS_5v is always on Aug 02 12:52:17 either way I'd expect it to be 0V or around 5V, not 0.78V Aug 02 12:52:44 I'm pretty sure that's the way it's supposed to be Aug 02 12:52:45 yeah, but im guessing you dont have V_Bat shorted to V_Bat_Sense ? Aug 02 12:53:07 TP5 and TP6 Aug 02 12:53:22 i shorted them Aug 02 12:56:08 I'm measuring: TP5 0.777 TP6 0.3 TP7 2.24 Aug 02 12:56:52 sounds like the power switch is behaving strangely Aug 02 12:57:07 ive got a lipo cell permanently installed Aug 02 12:58:49 well, it seems consistent with it trying to charge the battery with SYS_5V... only question is why the fuck is it at 0.777V Aug 02 12:58:56 and see V_lipo on SYS_5V Aug 02 13:03:37 ah wait, it's supposed to be off Aug 02 13:03:51 but "Battery voltage always supplies the system (SYS pin)" Aug 02 13:03:59 ah Aug 02 13:04:07 i should read the datasheet :P Aug 02 13:06:37 ive also taken a wire jumper from the MUX pin on the TPS65** PMIC to AIN7 Aug 02 13:06:59 well it's not exactly short, but yeah if you're doing stuff with battery power I'd say you may want to read it Aug 02 13:07:00 so the voltages can be monitored using i2cset on /dev/i2c0 Aug 02 13:07:09 heh :P Aug 02 13:13:48 connecting TP5 and TP6 has some effect Aug 02 13:14:33 aiui thats a "battery detect" function Aug 02 13:14:56 yeah, and not just in a binary fashion Aug 02 13:15:33 sense is very sensitive indeed: just touching with a wire (other end unconnected) causes SYS_5V to change significantly Aug 02 13:15:47 in the upward direction Aug 02 13:16:02 connecting it to VBAT drops the voltage to 0.4V Aug 02 13:16:03 maybe it should have pulldown or pullup Aug 02 13:16:18 so I think I'm just seeing the battery charger trying to do its thing Aug 02 13:16:21 on TP6 Aug 02 13:16:28 no definitely not Aug 02 13:16:35 it needs to measure the battery voltage Aug 02 13:16:47 yeah i see Aug 02 13:17:02 Battery voltage sense input, connect to BAT directly at the battery terminal. Aug 02 13:17:18 i meant for when no battery is connected Aug 02 13:17:49 depends on what's desired for SYS_5V I guess Aug 02 13:18:45 datasheet says for batteryless system: "The battery pins (BAT, BATSENSE, TS) are floating" Aug 02 13:19:53 alternative is connecting VBAT and VSENSE to 5V supply, and 10k resistor from TS to ground Aug 02 13:20:30 which has the advantage of "higher power-efficiency because the internal power-path is by-passed and power-loss across the internal switches is avoided." Aug 02 13:20:39 but you lose overvoltage protection Aug 02 13:21:21 interesting Aug 02 13:21:41 im seeing lower idel current from Debian then Angstrom Aug 02 13:21:52 about 100mA lower from my lipo Aug 02 13:22:00 ah wait, with the former case they do connect BAT to BAT_SENSE in their example diagram Aug 02 13:22:07 150mA versus 250mA Aug 02 13:23:03 given angstrom's goals of being specifically targeted at embedded systems versus debian primarily desktops and servers, that's pretty sad Aug 02 13:23:33 given that the image was NOT power optimized, I am not surprised Aug 02 13:23:44 the debian image is? Aug 02 13:23:49 it runs a full graphical environment, etc Aug 02 13:24:01 fair enough Aug 02 13:24:09 zmatt: no, but there is so much cruft enabled on both Aug 02 13:24:17 right, so it's pretty random Aug 02 13:24:17 makes it impossible to comare Aug 02 13:24:43 Laurenceb__: you can try running powertop maybe Aug 02 13:24:53 heh, same thought Aug 02 13:25:03 ok Aug 02 13:26:45 can ethernet, gpu and hdmi be disabled? Aug 02 13:27:41 the am335x has fine-grained power management... question is what opinion the board and linux have on it Aug 02 13:27:42 im trying to assembled an embedded device that runs an ultra high fps camera on gpio signals, then grabs h.264 over usb and does some CV stuff Aug 02 13:27:53 right Aug 02 13:28:00 *assemble Aug 02 13:28:45 ethernet phy can be put in powerdown mode via mdio Aug 02 13:28:56 you can disable the virtual capes for hdmi Aug 02 13:28:58 typical 5.6 mW consumption Aug 02 13:32:20 the big NXP IC, its a "HDMI framer" ? Aug 02 13:34:47 wow .. relying on usb for h264 .. on the am335x .. thats brave. Aug 02 13:34:57 you did know the driver was broken?! Aug 02 13:36:21 is the cpu really fast enough to do the encoding too? Aug 02 13:36:50 I'm using a dm368 with optimised codecs for some hd video capture Aug 02 13:37:06 but a different scale project I would imagine :) Aug 02 13:37:35 oh dear... Aug 02 13:37:45 i thought it was less broken than Rpi Aug 02 13:37:59 this isnt for live video, the camera has internal flash Aug 02 13:38:00 different kinda broken .. the usb is the onyl real weakpoint Aug 02 13:38:12 and its been well patched .. but it is patched lol Aug 02 13:38:14 does mass storage work? Aug 02 13:38:25 the camera mounts as mass storage Aug 02 13:38:27 I'm using mine with a usb ide hdd .. works :) Aug 02 13:38:37 at least the am335x doesn't cause random data corruption on I2C if a slave dares to use clock stretching (the rpi does) Aug 02 13:38:43 cool, thats all i need Aug 02 13:38:43 omg .. never try to network share a usb hdd with a Pi. Ever. Aug 02 13:38:50 hehe Aug 02 13:38:51 Laurenceb__: so you're not doing real time? Aug 02 13:38:54 no Aug 02 13:39:00 should be ok then Aug 02 13:39:01 :) Aug 02 13:39:14 should work then Aug 02 13:39:27 its for monitoring machinery Aug 02 13:39:43 when I first started working with the beagle . the usb wouldn't work unless a device was plugged when the board was powered .. hotplug has improved Aug 02 13:39:49 i get a gpio signal a few seconds before the event, set the camera to record at a few k fps Aug 02 13:40:03 ah .. low scale control .. should be fine Aug 02 13:40:05 then grab the video later and save only statistics from some basic CV Aug 02 13:40:24 its a good cheap solution :) Aug 02 13:40:34 yeah :D Aug 02 13:40:35 although the arduino/etc is just as good for basic io with usb ;D Aug 02 13:41:06 there's quite a good set of low cost solutions for different purposes comeing out Aug 02 13:41:25 veremit: you don't want to do any video processing on an arduino though, also not offline video processing :P Aug 02 13:41:40 yeah, but h.264 decode to framebuffers is not feasible on most other hardware Aug 02 13:41:41 nope .. not on anything less than the stm32 ones ;P Aug 02 13:41:48 stm32f4 would work Aug 02 13:41:57 the new arduinos look very cool Aug 02 13:41:59 but i dont fancy hacking h.264 decode Aug 02 13:42:06 nope .. if its decode that be fine Aug 02 13:42:15 Laurenceb__: for power management I think you'll be reading lots of datasheets... the phy has powerdown mode, the HDMI framer " can be switched to very low power Standby or Sleep modes to save power when HDMI is not used", etc etc Aug 02 13:42:24 but I'm guessing you will need to configure them into those modes yourself Aug 02 13:42:29 ok Aug 02 13:42:33 yea won't be an easy ride Aug 02 13:42:42 I was gonna say 'custom board' but that doesn't usually come easily :) Aug 02 13:42:43 ill check the schematic and have a think Aug 02 13:42:48 heh :D Aug 02 13:42:51 sources are all out there Aug 02 13:43:09 thanks for the help Aug 02 13:43:09 veremit: custom board, with a chip like the am335x... have fun Aug 02 13:43:17 stuff like ddr3 layout Aug 02 13:43:33 yeah you gotta know what ya doin .. but if you do .. Aug 02 13:43:45 custom with stm32f4 would be doable Aug 02 13:43:48 we're about to start on imx6 layout Aug 02 13:43:51 dunno if itd be less or more work Aug 02 13:43:57 based on the imx rex designs Aug 02 13:44:10 most of my projects are stm32f4 based Aug 02 13:44:13 I do like my wandboard though :) Aug 02 13:44:19 but video transcoding looked like a pita Aug 02 13:44:35 we have a dm814x-based board... the company that usually does our electronics design had to partially outsource it because it was kinda over their heads Aug 02 13:44:35 you don't want to transcode on anything that doesn't have some grunt Aug 02 13:44:47 encoding is bad without dedicated hardware .. decode is fine Aug 02 13:44:47 (it ended up a 14-layer PCB iirc) Aug 02 13:44:55 14?! holy cow Aug 02 13:45:00 rex is only 6 Aug 02 13:45:07 yeah that was my reaction too Aug 02 13:45:23 what on earth happened there? besides someone wanted to make some money lol Aug 02 13:45:30 well i should have said decode then encode at jpeg only Aug 02 13:46:10 how many balls is that iMX of yours? Aug 02 13:46:15 mjpeg or still ? Aug 02 13:46:35 can't remember .. project's been shelved for now whilst we do video over IP work :) Aug 02 13:47:13 I remember the pin descriptions run to about 4/5 pages of a4 :D Aug 02 13:47:23 I was comparing the quad/single cores Aug 02 13:47:26 they are compatible Aug 02 13:49:15 http://www.imx6rex.com/download/design-files/imx6-rex-module/v1i1/docs/iMX6%20Rex%20Module%20V1I1%20PCB%20STACKUP.pdf Aug 02 13:49:18 that's 12 layers Aug 02 13:49:55 if I understand what I'm looking at Aug 02 13:50:06 (I just clicked something, wasn't looking for this :P ) Aug 02 13:50:19 silkscreen's don't count :P lol Aug 02 13:52:30 ah about comparable number of balls Aug 02 13:52:45 its got enough lol .. its just above our expertise Aug 02 13:54:39 but manufacture is subcontract anyway .. Aug 02 13:54:51 most likely just lift the design and add bits :) Aug 02 13:55:20 and I don't know enough about pcbs to know what you meant with "silkscreen's don't count", I also don't know how the "14" of our pcb was counted (or even if I remember it right) Aug 02 13:56:08 lol .. usually you refer to the 'copper' layers .. yes there are technically possibly up to 16 or so 'physical' layers , but its the ones that need photo etching and drilling that count :) Aug 02 13:57:12 it looks to me they only numbered copper layers, otherwise there'd be 28 :P Aug 02 13:57:19 ouch :) Aug 02 13:57:27 fun stuff Aug 02 13:57:41 (talking about the iMX6 rex pdf I linked to) Aug 02 13:59:07 yea I'm with ya Aug 02 13:59:15 I haven't looked in much detail tbh Aug 02 13:59:53 Laurenceb__: to briefly touch back on the custom board. look at blue-steel. it's a stripped down BBB design. Aug 02 14:03:08 lol thats awesome hehe .. stripped :) Aug 02 14:04:06 anyhow, time to get some groceries Aug 02 14:05:51 I like it "you can actually get it now, which is smoething you can't say about the beaglebone black" lol Aug 02 17:06:51 I have a black rev c running debian, can I boot off SD and dd the internal partition to usb (or over ethernet) as a backup, flash a different OS, then if I decide to go back, I can dd the image back? Aug 02 17:21:36 acovrig: I don't think it's that simple Aug 02 17:22:04 that's what I'm afraid of... Aug 02 17:22:56 tbr, I got a screen that I can't get working in debian, but want to keep debian; they have an angstrom image I could flash, but would want to switch back to debain and continue working on getting it working if I see it work in angstrom Aug 02 17:25:02 you can download a stock debian image Aug 02 17:28:54 acovrig: run angstrom from sd-card then Aug 02 17:29:52 .. or that .. ^^ :) Aug 02 17:29:55 veremit: BBB is widely available on ebay Aug 02 17:30:11 ive ordered 3 board, all shipped in Farnell/element 14 boxes from china Aug 02 17:30:13 eww not payin those grossly inflated prices .. besides .. I have one .. two .. Aug 02 17:30:19 i suspect someone is diverting their stock Aug 02 17:30:23 oh definitely Aug 02 17:30:28 easy market Aug 02 17:30:49 don't think the foundation got a handle on that Aug 02 17:30:57 if i was feeling more helpful i would let farnell know Aug 02 17:31:04 tbr, I'm not sure the image I downloaded from the display manufacture is standalone bootable, or if it installs itself on boot. Aug 02 17:31:06 but they should be able to work this out by themselves Aug 02 17:31:11 ah not el14 too?! I thought that was just cco Aug 02 17:31:25 farnell won't care .. they just shift boxes .. fast :D Aug 02 17:31:38 farnell is owned by element 14 Aug 02 17:31:46 yes, and cpc and onecalls too Aug 02 17:31:46 acovrig: oh, is it a custom display cape then. those are tricky Aug 02 17:32:32 ok afk a bit Aug 02 17:32:57 tbr, *sigh* yea... I downloaded the ~900MB zip (with a stock angstrom and their image) from their server at ~3KB/s (my connection isn't the issue, I can download at ~5MB/s)... Aug 02 17:45:34 acovrig: chalkboard? tigal? Aug 02 17:47:25 tbr, you asking brand? waveshare (cheep on ebay from china) Aug 02 17:49:34 never heard Aug 02 17:49:40 tbr, this is the 'guide' I am trying to follow: http://www.wvshare.com/downloads/accBoard/DVK53X/Documentations/Porting_Drivers.pdf Aug 02 17:56:18 acovrig: your best chance is if you can get the sources for their kernel Aug 02 17:56:24 and extract the patches Aug 02 17:56:30 or the patches themselves Aug 02 17:56:56 the really really ugly way is ripping out the kernel and modules out of their image and transplanting them into the debian image Aug 02 18:06:52 tbr, I compiled the kernel from their source, but when I coped the uImage over and rebooted, it wouldn't boot (I don't remember the error I saw via my TTL cable) Aug 02 18:07:21 lovely Aug 02 18:20:08 Hi Aug 02 18:20:18 Need a help on BeagleBone Black Aug 02 18:21:37 my arm gcc compiler throws error for this code. Aug 02 18:21:47 ******************************************************************************/ /** * \brief This API can be used to switch from user mode to privileged mode * The priviledge mode will be system mode. System mode will share * the same resources as user mode, but with privileges. * * \param None. * * \return None. * * Note : All the access to system configuration which needs privileged access * Aug 02 18:31:57 pastebin pls Aug 02 19:28:00 re: imx6rex pcb stackup... I believe the SOM is 12 layer and the carrier board is 6 layer, hence the confusion. Aug 02 19:28:52 I don't remember seeing 12 layers in the gerber .. but I didn't look in a lot of detail :) Aug 02 19:29:13 could be I guess Aug 02 19:29:29 thats six boards Aug 02 19:38:12 veremit: what do you mean by "that's six boards?", it's quite clear on their website documentation for the SOM versus DBB, there are seperate documents just for the stackup, no need to look at gerbers. Aug 02 19:38:57 anyway this channel is about BB so I go back to lurking. Aug 02 19:39:00 I haven't looked for a few months .. I don't honestly know .. but 12 layers to me .. is 5/6 thinknesses of board :p Aug 02 19:39:14 sandwiched :) Aug 02 19:40:46 anyhow .. time to afk .. bbl Aug 02 19:41:59 there is standard terminology for this stuff, and you are not using it. Aug 02 23:45:45 if I have a BBB with remote connection (ssh), how can I read its revision A, B or C? Aug 02 23:46:30 look at the label on the p8/9 header Aug 02 23:46:39 there is no software versioning afaik Aug 02 23:58:31 fdisk could tell you if you're on a rev C as it has additional eMMC **** ENDING LOGGING AT Sun Aug 03 03:00:00 2014