**** BEGIN LOGGING AT Wed Nov 08 03:00:03 2017 Nov 08 03:27:04 hi how can i learn C language for robotic? Nov 08 05:41:22 while (!understand_c()) {learn_more_c();} Nov 08 05:57:20 bool understand_c(void) { return false; } // mrnuke Nov 08 06:00:14 Kitlith: only if you #include Nov 08 06:03:58 okay, okay, fine. Nov 08 06:04:20 int understand_c(void) { return 0; } Nov 08 06:04:54 I kinf of like C99 types though Nov 08 06:05:31 #include Nov 08 06:05:38 :) Nov 08 06:06:05 my code is littered w/ uint8_t and uint32_t Nov 08 06:06:19 sounds like you have very good code then Nov 08 06:06:35 I struggle with people sticking to u8 and u32 and brothers Nov 08 06:06:41 and I always get exasperated when people hand define u8 and u32... Nov 08 06:06:42 haha Nov 08 06:07:08 especially when some kernel reviewer asks me to change from uintxx_t to uxx Nov 08 06:07:12 that makes me go nuclear Nov 08 06:07:42 I mean, if that's the style they want to go for in the kernel, then fine. Nov 08 06:08:09 Kernel coding style allows and encourages stdint types for nbew code Nov 08 06:08:15 hah Nov 08 06:08:18 okay Nov 08 06:08:51 I don't do kernel development. Nov 08 06:09:57 Had to do it for my former client Nov 08 06:10:20 they had a custom ASIC, and hired some Huan-hung-lo charlie company to do the software porting Nov 08 06:10:29 nothing worked. Had to do everything myself Nov 08 06:10:34 :( Nov 08 06:11:10 yeah, had negative SLOC count contributions Nov 08 06:11:41 because my code consistently ended up being one fifth of the non-working code provided by the vendor Nov 08 06:12:18 so, was that company been taught the lesson of not using that vendor? Nov 08 06:12:19 at least the architecture stuff was done and supported by Synopsis, so didn't have to deal with that headache as well Nov 08 06:12:26 nope Nov 08 06:12:34 they're still paying that vendor big bucks Nov 08 06:12:55 you'd be surprised just how much of a driver cost is Nov 08 06:13:08 if they do it for less money, quality doesn't matter Nov 08 06:13:30 and this is why we have serious exploitable driver bugs. Nov 08 06:13:47 well, those drivers would never make it into mainline Nov 08 06:14:06 if you stickj to mainline, you'll be much better off Nov 08 06:14:12 oh right, we're talking about linux. was thinking of windows for a moment. Nov 08 06:14:57 #ifdef WIN32 #elifdef LINUX #elifdef OPENWRT #elifdef BARE_METAL .... Nov 08 06:15:44 if #elifdef an actual thing? Nov 08 06:16:22 at that point I mainly see people going #if defined(WIN32) #elif defined(LINUX) ... Nov 08 06:16:28 or #elif defined() Nov 08 06:16:49 I don't use the preprocessor too often Nov 08 06:16:58 that's fair Nov 08 06:32:16 hi..i have used beaglebone white ..i dont no stretch IOT and stretch beaglebone .which one i have used Nov 08 06:32:45 can one help me.. Nov 08 07:46:15 hi.. how to start windows 10 for beagle bone white using usb cable in python code Nov 08 07:46:27 or c Nov 08 08:07:42 hi..i have used beaglebone white using debian os.. Nov 08 08:08:13 my hist system using window10 ..how to communicate? Nov 08 08:08:25 sorry..host pc.. Nov 08 10:37:54 mrnuke: most kernel code uses u8/u16/u32, so it makes perfect sense to stick to it for consistency Nov 08 10:40:11 although CodingStyle indeed seems to imply that using stdint should not have been rejected in a new driver (as opposed to patches to existing code) Nov 08 14:39:48 Hello there! :) Is anyone familiar with Adafruit_BBIO-1.0.7 python lib? i have problems to asign gpios listed in common.c. In there I found { "GPIO2_7", "P8_46", 71, 3, -1}, but GPIO.output("GPIO2_7", GPIO.HIGH) time.sleep(0.5) GPIO.output("GPIO2_7", GPIO.LOW) time.sleep(0.5) does not work. Anybody any idea? thank you so much! :) Nov 08 14:41:02 is this on a beaglebone black? Nov 08 14:41:18 that pin number looks like one that's used for hdmi output by default Nov 08 14:41:25 I did GPIO.setup("GPIO2_7", GPIO.OUT) above but python outputs: ValueError: Set gpio direction failed, missing file or invalid permissions. Nov 08 14:41:41 yes you are right! Its bbblack Nov 08 14:42:00 then either disable hdmi (in /boot/uEnv.txt) or pick a different pin Nov 08 14:42:09 Thank you! It is an lcd pin, but isn't it possible to use it as gpio? Nov 08 14:42:17 ahhh Nov 08 14:42:23 ok i'll try!!! Nov 08 14:45:34 also be careful to avoid pulling any lcd_data pin up or down by an external load during power-on, since this can cause the beaglebone to fail to boot Nov 08 14:45:57 there is nothing like hdmi / lcd in there. so i cannot comment out. can i just write disable hdmi anywhere. Nov 08 14:46:07 no Nov 08 14:46:11 ah ok i will do so Nov 08 14:46:23 ok. what can i then do? Nov 08 14:46:36 there should be comments in that file regarding how to disable hdmi... what image version are you using? (cat /etc/dogtag ) Nov 08 14:47:18 BeagleBoard.org Debian Image 2017-08-31 Nov 08 14:47:37 that's very recent, then there should definitely be a config var there to disable hdmi Nov 08 14:47:51 disable_uboot_overlay_video Nov 08 14:48:40 there should be a line saying: #disable_uboot_overlay_video=1 Nov 08 14:48:46 uncomment that (remove the #) and reboot Nov 08 14:49:31 at least, I'm pretty sure that line existed already back then... Nov 08 14:49:36 I hope Nov 08 14:50:07 I think? Nov 08 14:52:57 hmmm....i cannot find :( Nov 08 14:53:00 #disable_uboot_overlay_video=1 Nov 08 14:53:17 #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e Nov 08 14:53:20 is in there Nov 08 14:53:39 crap, if that line isn't in there then maybe it was introduced just slightly after that :-/ Nov 08 14:53:54 no, that's not related Nov 08 14:54:00 hmmm...ok what shall i do now? Nov 08 14:54:10 :( Nov 08 14:54:45 any idea? Nov 08 14:55:13 the way to disable hdmi changed a number of times, so I'm not sure which instructions apply exactly to your particular version. can you pastebin the content of your /boot/uEnv.txt ? Nov 08 14:55:58 you may also consider reflashing to the latest version if that's not too inconvenient for you Nov 08 14:56:50 especially, if you don't need hdmi then you can flash an "iot" image which doesn't include a GUI Nov 08 14:56:58 it saves a _lot_ of space on eMMC Nov 08 14:57:57 which helps to avoid running out of space later on, e.g. when trying to install things Nov 08 15:03:47 perfect! i will try bone-debian-9.2-iot-armhf-2017-10-10-4gb within a couple of minutes Nov 08 15:08:22 note that when you make an sd card of that image and boot from it, it will not automatically reflash eMMC. you need to uncomment a line in the card's /boot/uEnv.txt to turn it into a flasher (and then reboot). see instructions on bbb.io/latest-images Nov 08 15:43:39 @zmatt: u are my hero!!! just worked! :) Nov 08 15:49:54 hi, i am having issues loading kali on beaglebone ....anyone have any experience with this? Nov 08 18:31:23 I WANT TO USE THE BBBWL-SC-562 WIRELESS AS STANDALONE AND NEED TO KNOW HOW MUCH CURRENT THE BOARD WILL DRAW FROM THE 5V IN WORST CASE LOAD. Nov 08 18:32:54 no need to scream like that Nov 08 18:34:28 if you don't connect anything else to the board, no USB devices, no capes, no nothing it should not exceed 1A. Although I'd probably want to use a supply with a bit of headroom. Especially those cheap wall-warts are notoriously under-specd. Nov 08 18:43:25 sorry was not screaming. i have a limited supply around 400mA. my test of the board at startup is around 300mA. but that doe not take into account transmission power. so the 1 amp generalized spec is not what i need. the board should have a max draw of current that should be defined. Nov 08 18:45:04 you might be able to reduce the power budget by limiting frequency scaling Nov 08 18:45:38 that's what happens automatically when a regular BBB gets booted powered over USB (to fit in the 500mA power envelope) Nov 08 18:46:29 you'll have to do qualification tests yourself to determine if you can sufficiently reduce power consumption by e.g. further limiting maximum CPU clock Nov 08 18:47:26 wifi can be quite power hungry, so I'm not quite sure you'll manage to fit into a 400mA budget Nov 08 18:47:53 i am talking only about the beagle board wireless board by itself, not the main bbb. there are no hardware specs i can find...just feature specs. i know i can reduce operations but at normal performance use where can i find a spec on power consumption? Nov 08 18:49:04 ah, I was guessing you meant the BBB with wireless on board. There is a variant Nov 08 18:50:14 looking at the mouser page, that is what you mean Nov 08 18:53:04 oh well... Nov 08 18:54:37 I doubt you'll find a power spec to your liking. Most that I've seen for such boards are "worst case", so with all sorts of peripherals attached, CPU, GPU, etc maxed out. Nov 08 18:55:10 does any one have a specific 5v current draw value for the beagle board wireless board BBBWL-SC-562 by itself when transmitting and when not? Nov 08 18:55:36 you could of course try contacting GHI or asking on their forum Nov 08 18:56:07 thanks......... Nov 09 02:24:57 Is there an overlay for the Motor Bridge Cape? Nov 09 02:26:35 Or...do I need to test out each of the overlays to be able to see? **** ENDING LOGGING AT Thu Nov 09 03:00:01 2017