**** BEGIN LOGGING AT Sat Apr 18 02:59:59 2015 Apr 18 16:13:03 Hi! Apr 18 16:17:14 Total noob here /!\ I don't understand how to activate Mode 3 on P9 pins 1-2-3-4 and 19-20, BB Black rev.B. Any clue -including tutorials links-? Apr 18 16:18:19 I'm using latest image, kernel 3.14 by the way Apr 18 16:21:21 *latest Thing image Apr 18 16:27:21 Thing image? Apr 18 16:30:13 For a 3D printer Apr 18 16:30:41 Thought so ... su you plan on using ubuntu? Apr 18 16:30:48 it's labeled "Thing image (Angstrom, stable)" Apr 18 16:31:31 angstrom is less burdensome but you have a step by step settup for it? I was just looking at that an hour ago :D Apr 18 16:32:37 I simply followed http://wiki.thing-printer.com/index.php?title=Thing_image Apr 18 16:33:11 But now, I've no power on pin 3 and 4 and I need this +3.3V Apr 18 16:35:18 And I need mode 3 on P9 pins 19 and 20 too... Apr 18 16:35:26 But I'm lost right now Apr 18 16:35:41 * GenTooMan mutters about people who use tape to make things work once in a while. "hmmm not much their I noticed", he muses. Apr 18 16:36:33 I noticed they are using a crappy slicer program for handling STL data (argh) I won't complain too much but that algorythm is 18 years old. Apr 18 16:37:54 I'm not a big fan of "do things quickly" erstwhile your problem WHICH header are you talking about? You have 2 big plugs on the BBB Apr 18 16:39:55 "Maximize your experience with Code Composer Studio v6" .... they're not really specific in what *kind* of experience. If it's similar to previous experience with CCS, I'm not sure I'm particularly looking forward to having it maximized Apr 18 16:44:03 maybe they misspelled 'avoidance of' Apr 18 16:44:13 LOL CCS6 includes compatibility with using the newer FET430-2 which includes nanoamp power consumption measurement Apr 18 16:44:23 Their are some other things they added too. Apr 18 16:51:07 actually I'm already using CCS6, just doing a fresh install/upgrade Apr 18 16:51:57 nice job packaging... an installer and readme without enclosing folder in a tar gz... installer isn't executable Apr 18 17:25:45 Linux versino? Apr 18 18:17:19 GenTooMan: obviously Apr 18 18:23:41 heh :D Apr 18 18:24:16 I remember attempting v5.5 and I didn't meet the "binary" dependencies. Apr 18 18:24:40 you need a shitload of 32-bit shared libs Apr 18 18:25:09 (although not all it claims) Apr 18 18:25:25 hmm I have a 64bit system Apr 18 18:25:34 it only has 8 gigs but still Apr 18 18:25:40 .... like everybody else :P Apr 18 18:25:54 I've had it for 4 years time to upgrade Apr 18 18:28:51 argh, I want to check how badly they screwed up the CPSW driver for AM335x TI/RTOS (to see if I can confirm for someone on E2E that his problems indeed lie there)... but it's not actually included with TI/RTOS, you need the Industrial SDK, which is a Windows-only installer -.- Apr 18 18:52:00 I know your pain ... Apr 18 18:52:02 :D Apr 18 18:53:09 gawd I just can't stomach the redicuous complexity and 15 million levels of indirection in this code Apr 18 18:55:20 Have you looked at their "simpliciTI" network stack for wireless? Don't get me wrong it's not BAD but it has some major short commings for example as a wireless network protocol it uses STATIC links. You look through the "pile" of stuff in it and it refers to itself practically in the 3rd person. So from me no surprise? Apr 18 18:56:05 "not BAD" sounds like quite a compliment Apr 18 18:56:30 most code I've seen is... http://goo.gl/zBMxPr Apr 18 18:57:18 I had to almost completely bypass it to make it form dynamic links for polling I was told "it won't allow you to do a join operation that way cause it won't clean up properly." mutter. So I use it's equivalent to UDP Apr 18 18:57:34 e.g. code to update an MMU entry by.... turning the MMU *off* (including flushing all caches), changing the entry, and then turning the MMU back on Apr 18 18:58:11 Ummm is their a bug in the MMU hardware that necessitates that? Apr 18 18:59:09 no, and it's almost guaranteed to break stuff Apr 18 18:59:44 on an ARMv7 processor you should turn the MMU on asap keep it that way Apr 18 19:00:12 the only reason to turn it off is to avoid complication in the hand-off from bootloader to OS Apr 18 19:01:17 Yes so they are obviously budding kernel writers. :D Apr 18 19:02:06 Hmmm For a robot OS does ROS work? It seems the most up to date. Not sure I want to use linuxCNC for something that isn't machining. Apr 18 19:02:55 no idea sorry Apr 18 19:03:37 their uart driver is nice too... in the routine you use to enable or disable some of its interrupt sources, it briefly enters uart config mode Apr 18 19:04:03 ... which is absolutely forbidden, since it'll halt uart operation immediately, even in the middle of transmitting a character Apr 18 19:04:18 (and also completely unnecessary) Apr 18 19:11:48 Funny things that simpliciTI did some dumb crap like that too. Apr 18 19:12:32 For example when it was using the SPI port it pulled for the interrupt flag instead of using the uart busy flag caused all sorts of stupid crap to happen Apr 18 19:14:02 This created an issue with the receive interrupt never clearing or getting out of sync (when transmitting) Apr 18 19:24:16 I really do hate the uart though.... that thing has a seriously fucked-up interface (yay for decades of backwards compatibility -.- ) Apr 18 19:27:21 which uart is it compatible with? Apr 18 19:27:57 16C750 Apr 18 19:29:07 irritating modal register interface Apr 18 19:29:52 even if the compat is still useful, they should have made the registers accessible directly also Apr 18 19:31:01 especially since some registers which imho are perfectly reasonable to change at runtime require entering config mode Apr 18 19:31:10 but the irq handling is braindead too Apr 18 19:32:12 and no option to pack 4 bytes into a single read from / write to the fifos Apr 18 19:32:16 which also means no efficient dma Apr 18 19:32:49 at least the McSPI controller got that aspect right Apr 18 19:33:43 I noticed this was a problem with ARM not persea the implementation. Some processors allow packing in tranfers via DMA IE byte to word (not aligned but 2 byte reads to an aligned word for example) Apr 18 19:34:09 the uart's bus interface is 32-bit Apr 18 19:34:35 (also, the DMA engine is not in any way related to ARM) Apr 18 19:36:48 a larger fifo window than 4 bytes would allow even greater efficiency when accessing it from the CPU (which can only do linear bursts), but a 4-byte window would suffice to allow the DMA engine to do a streaming burst Apr 18 19:37:07 now, to use streaming bursts you'd have to store your characters as an array of 32-bit ints Apr 18 19:38:28 a transfer controller of the dma engine can only have 1 read request and 4 older write requests open at any given time Apr 18 19:38:47 regardless of whether that's a request for 1 byte or a request for a 64-byte streaming burst Apr 18 19:40:11 (as a result the CPU can actually write data to the uart _faster_ than the dma controller) Apr 18 19:41:30 too fast actually, I discovered the UART can't deal with 8 or more writes in immediate succession, it fucks up some internal pointer or counter or something Apr 18 19:42:12 my guess would be some clock domain crossing issue in the fifo logic :/ Apr 18 20:03:14 Well you can have sync in and out fifo (IE different clocks for input and output) however might be a bit messy. Apr 18 20:29:25 hi Apr 18 20:29:49 can anyone assist me in making my beaglebone a wifi repeater Apr 18 21:02:57 You would need some software that supports that function no? Apr 18 22:13:56 Hi I've been trying to figure out how to make a custom emmc flasher for the beaglebone black for the past few hours and I can't seem to instructions that do enough ahnd holding Apr 18 22:14:12 I've been looking at https://github.com/RobertCNelson/omap-image-builder Apr 18 22:15:09 But I can't figure out how one actually generates an imagethe one shown here Apr 18 22:15:21 http://elinux.org/BeagleBoardDebian#Flasher Apr 18 22:15:59 I'm trying to generate an image with my own packages Apr 18 22:16:14 and boot scripts Apr 18 22:17:07 I found a number forum posts about it like this one Apr 18 22:17:08 https://groups.google.com/forum/#!topic/beagleboard/gkVwuE7324U Apr 18 22:17:23 but they are genrally out of date Apr 18 22:21:06 foundatron .. pop in Monday, and Rob Nelson will be back in here to ask himself Apr 18 22:22:07 I can do that... Apr 18 22:24:44 Has anyone else here had experience building their own images? Apr 19 00:24:59 Not I Apr 19 00:25:08 * GenTooMan says 2 hours later Apr 19 00:32:49 I've made some progress Apr 19 00:33:04 But I still haven't made an image that works Apr 19 00:34:00 If anyone actually knows the order of operations for using the image-builder to build an image I would love to know Apr 19 00:34:02 https://github.com/beagleboard/image-builder Apr 19 00:34:17 I ran ./beagleboard.org_image.sh Apr 19 00:34:25 it did a bunch of stuff Apr 19 00:34:41 I wanna read serial number of the beaglebone black in the kernel booting process. Anyone can help me? Apr 19 00:34:45 but I can't find any output imgs anywhere on my system Apr 19 00:35:25 Their should be something on the angstrom website Apr 19 00:36:01 they have made bootable images for a bunch of platforms Apr 19 00:36:10 foundatron: https://eewiki.net/display/linuxonarm/BeagleBone+Black Apr 19 00:36:45 I've seen this page... Apr 19 00:37:21 I don't think it answers my question though Apr 19 00:37:43 what are u trying to do? Apr 19 00:40:56 How do you use https://github.com/beagleboard/image-builder to create an image? Apr 19 00:41:59 I've been unable to generate a working img Apr 19 00:42:25 The read me doesn't really specify much in the way of input and outputs Apr 19 00:42:38 just out of curiosity .. why do you want an image, rather than just setting up a uSD card? Apr 19 00:43:02 i'm trying to set up a emmc flasher that has custom packages installed Apr 19 00:43:24 but I would like to first make a vanilla emmc flasher before I modify it Apr 19 00:44:09 make sense? Apr 19 00:44:17 mkay Apr 19 00:44:56 * GenTooMan scratches his mind and looses neurons. Apr 19 00:45:13 We're just talking about generating an emmc flasher Apr 19 00:45:17 nothing crazy Apr 19 00:45:26 using https://github.com/beagleboard/image-builder Apr 19 00:45:53 heh you'd think .. :P Apr 19 00:46:00 rather than downloading the prebuilt ones Apr 19 00:46:12 i want to bake my own bread :) Apr 19 00:46:47 something like that--->>https://github.com/RobertCNelson/tools/tree/master/scripts Apr 19 00:47:24 Those involve copying from sd to emmc, or emmc to sd Apr 19 00:47:41 yes Apr 19 00:47:44 not generating the image Apr 19 00:47:51 which is what i want to do Apr 19 00:48:38 ok nvm Apr 19 00:49:00 Before it hits an sd card or emmc , I want install packages, and change what runs at start up Apr 19 00:49:25 This is part of CI testing pipeline Apr 19 00:49:30 so no humans involved Apr 19 00:50:25 but where are you gonna get those packages? Apr 19 00:50:26 commit happens in repo X which causes an image to generated Apr 19 00:50:36 debian angstrom buildroot Apr 19 00:50:40 same way the builder does now Apr 19 00:50:46 ubuntu Apr 19 00:50:47 just list them in the dependecies Apr 19 00:53:37 tholm I'm assuming I can just add them here https://github.com/beagleboard/image-builder/blob/master/configs/rcn-ee_console_debian_wheezy_armhf.conf#L14 Apr 19 00:56:17 I think so Apr 19 00:57:01 ? Apr 19 01:00:25 foundatron: yes Apr 19 01:00:26 Add some package in that line and see what happends Apr 19 01:00:30 add them there and they will get installed Apr 19 01:00:32 i am using it Apr 19 01:01:28 vvu! Apr 19 01:01:37 Iyou're using it? Apr 19 01:01:41 yes Apr 19 01:01:51 you can script it at the ultimate level :) Apr 19 01:01:59 i am genrating my own rootfs images Apr 19 01:02:01 I've been trying to get it to work for about 5 hours Apr 19 01:02:02 sick Apr 19 01:02:10 what are you trying to achieve here ? Apr 19 01:02:11 I wanna read the serial number of the beaglebone black in the kernel booting process!!!! Apr 19 01:02:35 I'm trying to generate a custom emmc flasher Apr 19 01:03:04 foundatron: one sec to find the script Apr 19 01:03:13 Yessss!!!! Apr 19 01:03:19 foundatron .. don't forget you only have 2gb or 4gb emmc :P Apr 19 01:03:24 You're the man/woman/internet robot! Apr 19 01:03:36 I have 2gb Apr 19 01:04:12 and it's about 1 gig more than I need Apr 19 01:04:17 ideal Apr 19 01:04:28 well ..looks like you found your solution :) Apr 19 01:04:45 you can generate the rootfs normally Apr 19 01:04:52 then use https://github.com/ungureanuvladvictor/BBBlfs to flash the eMMC Apr 19 01:05:33 foundatron: i cannot find the line where the eMMC script is activated Apr 19 01:05:52 foundatron: https://github.com/RobertCNelson/omap-image-builder/blob/master/target/boot/eMMC-flasher.txt Apr 19 01:06:03 this is the uEnv.txt for uboot to run the emmc flasher Apr 19 01:06:51 So I guess wee need to take a step back Apr 19 01:07:01 and this is the script https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh Apr 19 01:07:08 you're using https://github.com/RobertCNelson/omap-image-builder correct? Apr 19 01:07:26 yes Apr 19 01:07:52 i am using it just to generate a normal rootfs Apr 19 01:07:54 not an emmc flasher Apr 19 01:08:20 but you can also use the image-builder to generate an emmc flasher image Apr 19 01:08:46 Ok so what's your order of operations Apr 19 01:09:13 do you run ./beagleboard.org_image.sh at all? Apr 19 01:09:33 or just RootStock-NG.sh Apr 19 01:09:37 generate normal rootfs using the basic eewiki_minfs_debian_wheezy_armhf Apr 19 01:09:40 ./RootStock-NG.sh -c eewiki_minfs_debian_wheezy_armhf Apr 19 01:09:49 this is what i run to generate my rootfs Apr 19 01:10:08 which produces a ./deploy/something.tar correct? Apr 19 01:10:22 yes Apr 19 01:10:37 then i use https://github.com/ungureanuvladvictor/BBBlfs Apr 19 01:10:39 to flash the eMMC Apr 19 01:11:25 and you never touch setup_sdcard.sh? Apr 19 01:11:40 nop Apr 19 01:11:45 i flash directly the eMMC via USB Apr 19 01:12:34 Ok, so my use case is I need to produce emmc flasher imgs Apr 19 01:12:46 via jenkins Apr 19 01:14:09 So I just successfully generated that rootfs using "./RootStock-NG.sh -c bb.org-debian-wheezy-console" Apr 19 01:14:26 so I guess what i'm confused with now is how to do I take that Apr 19 01:14:46 and make a emmc flasher with setup_sdcard.sh Apr 19 01:15:00 foundatron: check the options https://github.com/RobertCNelson/omap-image-builder/blob/master/beagleboard.org_image.sh#L59 Apr 19 01:15:35 need to go now, paste here results :) Apr 19 01:16:00 thanks vvu Apr 19 01:27:01 vvu I think that worked Apr 19 01:27:13 I flashing my bbb now Apr 19 01:41:03 good to hear that Apr 19 02:15:32 * GenTooMan wonders Apr 19 02:26:25 Hmm, so I suppose a BeagleBone's USB port doesn't supply power, or at least enough power to satisfy a Tiva C Launchpad? Apr 19 02:31:26 its not designed to supply power, no Apr 19 02:31:34 you might try a powered usb hub Apr 19 02:31:55 May swipe one from work Apr 19 02:32:18 But since I can't even power the launchpad, it may be worth asking Apr 19 02:32:49 The other concern I had, that since the Black, they removed something that allowed the BB to be communicated with on a Serial Port Apr 19 02:32:58 ala via PuTTy Apr 19 02:33:49 Does that mean that plugging a serial device into the beagle bone (eg, my Launchpad using UART -> Serial comm) May not be read on a ttyACM port? Apr 19 02:43:18 you need a standard usb ttl debug cable you can plug onto the pin header marked 'debug' .. check out 'debug cables' on the 'beagle bone black accessories' page on elinux :) Apr 19 02:43:40 and on that note. . I gotta sleep .. its almsot 4am :/ Apr 19 02:43:46 bbl :p **** ENDING LOGGING AT Sun Apr 19 02:59:59 2015