**** BEGIN LOGGING AT Tue Apr 25 03:00:03 2017 Apr 25 04:07:39 hello Apr 25 04:08:20 is there a flasher image for the 4GB emmc? I see 2GB listed on beagleboard.org Apr 25 04:28:50 zmatt: nothing a good hammera can't fix Apr 25 05:39:56 Good morning Apr 25 06:59:26 morning Apr 25 09:05:17 Hello Apr 25 09:05:50 Where I can buy BeagleBoard-X15? Apr 25 10:00:44 Where I can buy beagleboard-15? Apr 25 10:35:19 Maybe not a typical BBB question, I am looking for a metal case that is purchasable in Europe for my BBB. Any suggestions/recommendations on this? Apr 25 12:16:20 rhaen: we used a lot of https://www.logicsupply.com/bb100-orange/ it was quite nice, but I'm not sure if they still make it. Apr 25 12:16:52 Spidler: thanks :) - I'll check if I get one from them. Apr 25 12:25:28 helllo Apr 25 13:02:51 hi, so i have a beageboard and whant to use it to do some xml parsing that comes from a ftp and send it to another ftp server, any resources/pointers how to make it user frendly(like setting a webpage to configure ip's and all that stuff)? Apr 25 13:27:58 pathrocle: Making what user friendly? finding the beagles ip and setting that, or configuring your ftp using software? Apr 25 13:31:03 pathrocle: Either way, when it comes to configuring the stuff on the Beagle itself, that's "tricky". configuring your own software? Depends on what you're comfortable with. I'd personally go for a simple webapp written in some language I'm cozy with. In my case, python, perhaps a simple flask app. Apr 25 13:33:24 Hello, I would like some information about your cards: Apr 25 13:33:46 Do you have some with built-in CAN interface? Apr 25 13:34:01 If not is it possible to add one? Apr 25 13:34:26 Can the eMMC be flashed to change the OS? Apr 25 13:35:25 some people have done CAN addon cards Apr 25 13:35:44 and yes, you can put whatever you want on the eMMC Apr 25 13:37:38 thank you for the quick answer Apr 25 13:38:21 since eMMC is built-in do I need something special to modify it? Apr 25 13:38:36 for instance if I want to change the OS Apr 25 13:38:55 you can just boot from SD card Apr 25 13:38:59 do I need to plug a bootable key? Apr 25 13:39:06 and then modify the eMMC to your hearts content Apr 25 13:39:20 ok Apr 25 13:39:35 and the choice is made in the BIOS? Apr 25 13:40:13 (between eMMC and SD-Card boot) Apr 25 13:40:32 there is no BIOS, this is not an intel PC Apr 25 13:41:11 not only intel PCs have BIOS Apr 25 13:41:31 yes, but it's the most common example Apr 25 13:41:59 then what decides which peripheric to check first? Apr 25 13:42:03 the SoC ROMBL evaluates the SYSID pins upon power up Apr 25 13:42:19 ok thank you Apr 25 13:42:23 for details, refer to the TRM Apr 25 13:43:32 to sum it up I need a bootable SD Card in order to change the eMMC Apr 25 13:43:33 right? Apr 25 13:44:15 that is the easiest option, yes Apr 25 13:44:38 ok Apr 25 13:44:43 thank you for your time Apr 25 13:44:46 have a nice day Apr 25 17:21:29 tbr: s/SYSID/SYSBOOT/ Apr 25 17:27:09 plz send me best prices of this beaglebord prices Apr 25 17:30:28 I personally don't have any for sale, maybe you should consider consulting the websites of resellers (or contact them directly for a quote if you want a larger quantity) Apr 25 18:00:55 Q've had enough, ur Qut off Apr 25 18:01:15 wrong program (hit up and then enter) :3 Apr 26 00:02:34 Okay... Apr 26 00:02:52 I set up ADC with Adafruit_BBIO on the BBB. Apr 26 00:03:21 Now...I am trying to set up three separate PWM pins. Why can I not set up PWM the way I set up ADC on my BBB? Apr 26 00:05:39 For instance, I will need PWM1A, PWM2B, and PWM2A for my script I found on the Adafruit site written by Monk. Does setting up PWM pins differ from ADC pins? Apr 26 00:10:00 Example here: I thought I could just type cape_enable=bone_capemgr.enable_partno=BB-PWM1A and be done but I came across issues with my cmd line errors. I received a RuntimeError: Problem with Cape Manager on the prompt. Apr 26 00:19:40 adc pins are dedicated and have no other function, hence require no configuration. the adc itself still need some setup, but the pins don't Apr 26 00:19:55 Oh. Apr 26 00:20:03 the digital I/O pins are all multipurpose hence require configuration Apr 26 00:20:54 also, I don't know where you typed that, but that line is meant for uEnv.txt and is not a command that is useful somewhere Apr 26 00:21:16 Okay...I swore up and down I had to add ADC to the cape_enable=bone_capemgr.enable_partno=ADC1 to write the script successfully. Apr 26 00:21:37 without the 1 presumably Apr 26 00:21:41 I typed that info. into the uEnv.txt file. Apr 26 00:21:49 I guess. Apr 26 00:22:00 yes that would have been to enable the ADC Apr 26 00:22:07 I would have to set up that BBB to check. Apr 26 00:22:09 Okay. Apr 26 00:22:27 That is what I did. I thought it was that simple with PWM too. Apr 26 00:22:27 I don't know the exact name of the relevant overlay either Apr 26 00:22:39 No issue. Thank you anyway. Apr 26 00:22:39 it might be, if there's a pre-made overlay for it Apr 26 00:23:26 Someone on the Google Board for the BBB said they had something for my script in ADC instead of using PWM but I want it to work with this PWM for now. Apr 26 00:24:02 I just checked, it would have been "BB-ADC". so, what that line does is setting an u-boot variable named "cape_enable" to the value "bone_capemgr.enable_partno=BB-ADC" Apr 26 00:24:30 somewhere in the bootscript this is presumably used to pass that value along as kernel parameter Apr 26 00:25:05 which causes the "enable_partno" variable of the "bone_capemgr" module to be set to "BB-ADC" Apr 26 00:25:19 See sir, I really cannot comprehend the root cause. I have had trouble with simplifying things. Oh. Apr 26 00:25:41 I am still reading on the subject and learning. Apr 26 00:25:56 which at some point during boot causes bone_capemgr to load the overlay /lib/firmware/BB-ADC-00A0.dtbo Apr 26 00:26:08 Aw. Apr 26 00:26:17 the 00A0 is a version suffix and implicitly used when there's no version info Apr 26 00:26:52 zmatt: is there a specific site that the BBB.io people have info. on the Cape Manager? Apr 26 00:27:16 there isn't a single specific source I can point to, it's just stuff I learned over time Apr 26 00:27:42 I could do random searches but I thought that there might be some Wiki produced by specific BBB.io personnel. Apr 26 00:28:31 some stuff is on some wiki pages, some of which is sometimes updated by people working for beagleboard.org Apr 26 00:29:07 I looked to the https://github.com/RobertCNelson/bb.org-overlays and tried some ideas on slots. Apr 26 00:29:18 anyway, to get back to your original question, using BB-PWM1A there doesn't work since no such overlay probably exists Apr 26 00:29:32 Got it. Apr 26 00:29:44 I see three pwm-related overlays, named BB-PWM0, BB-PWM1, and BB-PWM2 Apr 26 00:30:00 If I were to make an overlay, would I have to use .sh files? Apr 26 00:30:02 Oh? Apr 26 00:30:06 That is great news! Apr 26 00:30:21 I don't know immediately which pins they set up, for that I'd need to check their source code Apr 26 00:30:25 which you can find here: https://github.com/beagleboard/bb.org-overlays/tree/master/src/arm Apr 26 00:31:02 unfortunately the source code format for overlays is kinda horrible Apr 26 00:31:39 I am using an import Adafruit_BBIO.PWM as PWM for my first line and then import time. Simple yet effective. Apr 26 00:32:23 note that for pwm you probably don't need to use overlays on sufficiently recent images at least, since they made cape-universal default Apr 26 00:33:10 I thought this fact was true. My cape-universal is not commented in my uEnv.txt file. Apr 26 00:33:29 also, those BB-PWM0/1/2 overlays seem to have been written by someone who doesn't understand how overlays work Apr 26 00:33:40 Oh? Apr 26 00:33:47 Okay. Apr 26 00:33:55 they probably still work... Apr 26 00:34:06 but they're really strange Apr 26 00:34:36 oh btw, if you enable *any* overlay in uEnv.txt (using bone_capemgr.enable_partno) then cape-universal is automatically disabled Apr 26 00:34:56 Aw. I did not know this was true. Apr 26 00:35:08 Okay. I am getting somewhere. Apr 26 00:35:14 they did this because cape-universal tends to conflict with everything Apr 26 00:35:25 it's universally-conflicting ;-) Apr 26 00:35:50 Oh. So conflict is good for now. This is cool, I guess. I am still trying to learn things. Apr 26 00:36:28 So, say you wanted to use cape-universal, I would just not use any overlay, right? Apr 26 00:37:16 e.g. BB-ADC and/or BB-PWM2 or whatever? Apr 26 00:38:04 yes that is a prerequisite for the option that enables it (also in uEnv.txt) to take effect Apr 26 00:38:33 I don't remember its exact name, I think it was cape_universal=true or something like that, I think in the "cmdline" variable Apr 26 00:39:07 Okay zmatt: Will rebooting reset cape-univeral for some reason, i.e. even when it has not been uncommented or recommented? Apr 26 00:39:16 I can check the name later. Apr 26 00:39:27 what do you mean by that? Apr 26 00:40:00 I wanted to reboot the BBB and make sure things were registering after my change in file operation. Apr 26 00:40:27 Oh hold. Let me check the name of the cmd line operation. Apr 26 00:42:42 enable_uboot_cape_universal=1 is the cmd line operation in that specific file. Apr 26 00:42:46 The comment (#) has to be there for the operation to be disabled. Apr 26 00:43:50 So, if #enable_uboot_cape_universal=1 means it is disabled, does it disable upon every reboot or shutdown and boot? Apr 26 00:48:30 it applies on every boot Apr 26 00:51:31 Okay. Apr 26 00:54:31 I can check it out but if I was to set up specific .txt files, like in the uEnv.txt file, I could run something at boot and not have it work because of that file not staying converted to the changes I make. Right? Apr 26 00:55:38 ? Apr 26 00:56:53 I have no idea what you're saying Apr 26 00:57:36 Like for instance: I change the uEnv.txt file to support my needs. Then when I boot, the uEnv.txt file goes back to its default state. Right? Apr 26 00:57:44 no? Apr 26 00:57:47 it's a config file Apr 26 00:57:48 Oh. Apr 26 00:57:52 they don't magically change Apr 26 00:57:52 Okay. Apr 26 00:58:25 Okay...I was thinking that the .conf files were default files that went back to how they were originally typed out Apr 26 00:59:56 you might lose changes if you modify it and then cut power or hard-reset if the changes haven't actually been committed to eMMC yet (alternatively, this might leave the file corrupted), but if you cleanly reboot or shut down the file is going to remain in whatever state you left it in Apr 26 01:00:52 Okay...thank you sir. Apr 26 01:53:23 https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/am33xx_pwm-00A0.dts is what I found. Apr 26 01:54:01 zmatt: You were right. The PWM info. on these .dts files do not explain pin configuration. Boo! Apr 26 01:54:39 If I chose an overlay, I would never know what pin to use for my software. Apr 26 01:54:53 ... Apr 26 01:55:10 zmatt: ha, I keep mixing that up Apr 26 01:55:30 I have bigger problems. I cannot create a file, echo out > direction, echo 1 > value, and get what I want. Apr 26 01:56:06 that's a different overlay than any of the ones I mentioned Apr 26 01:56:14 it looks like it doesn't setup pins at all Apr 26 01:56:32 I know. Oops. Apr 26 01:56:38 I have no idea why that overlay even exists Apr 26 01:56:44 Give me another, please sir. Apr 26 01:57:02 I already explicitly stated their names Apr 26 01:57:50 Okay...I will review what was typed out. Apr 26 01:58:00 they were the first hit when I searched "pwm" in that list Apr 26 01:58:10 On GitHub? Apr 26 01:58:24 yes Apr 26 01:58:29 I already tried the site within the uEnv.txt file. Apr 26 01:58:36 ? Apr 26 01:58:59 Yes sir, they have a couple of Wiki pages for doc. stuff. Apr 26 01:59:42 I have no idea what you're talking about now Apr 26 01:59:47 (as usual) Apr 26 02:00:53 I know sir. Their are two Wiki sites listed on the page, i.e. the uEnv.txt file within the BBB Linux Distro. Apr 26 02:01:10 ok, and? Apr 26 02:01:44 I went to those sites and found some interesting info. but I would need an extra 145 MB of space for the files. Apr 26 02:02:34 .dtbo files... Apr 26 02:03:02 Right now, I am working on a 2GB Rev. A. No go! Apr 26 02:03:20 tbr: I think some other TI SoCs (e.g. omap5) do also have pins named sysid or something vaguely like that, also used as strapping options, but for setting some id related to debug (so you can distinguish multiple devices tied in a tap.7 star configuration) Apr 26 02:04:14 Set_: uhh, you should already have the relevant dtbos in /lib/firmware/, and I have trouble believing a bunch of dtbos could take up anywhere near that much space Apr 26 02:04:46 Otay. Thank you again. Off for now! Peace be with your life, matey! Apr 26 02:06:23 Hu Hu Apr 26 02:09:19 Tieng Sai Lee Chen Soi Pau Loi Xa Sa Hu Xa Pei Lai Feng Sai Apr 26 02:09:54 o.O Apr 26 02:10:06 Hush Hush Apr 26 02:10:24 Pei Se Cho Apr 26 02:10:34 ehm Apr 26 02:10:44 Tui Lei Pau Apr 26 02:10:48 are you sure you're in the right channel? Apr 26 02:10:56 クチミミチ Apr 26 02:11:04 здаров Apr 26 02:12:26 I am Bruce Lee's puppet Ghost Apr 26 02:12:49 Uuuuuuwaaaa yeeeeeeaaaahha Apr 26 02:17:00 zmatt: https://github.com/beagleboard/bb.org-overlays/commit/16f76f79058958f8741ff6020435b146ab6dd271#diff-c84188b82e2b37fc99958c17a559f9a6 is what I found. Apr 26 02:17:41 I thought you were off? Apr 26 02:17:45 If I clone git , will I be ready to use those pins? Apr 26 02:17:51 I know...I gave up on "off." Apr 26 02:18:26 again, as I already said, the compiled dtbos are probably already in /lib/firmware/ Apr 26 02:18:51 Okay...since those dtbo's are already listed, how can I use them? Apr 26 02:18:53 (which, as I explained, is where capemgr looks for them) Apr 26 02:19:09 in the same way as you already have used overlays previously Apr 26 02:19:44 Okay but sir...I keep getting the Runtime Error: Problem with Cape Manager error. Apr 26 02:19:52 I have tried many things and came up empty. Apr 26 02:20:11 I have never seen or heard of that error I'm afraid Apr 26 02:20:19 Dang. Me either! Apr 26 02:20:27 I am baffled. Apr 26 02:23:10 Lookie, Lookie at what I found: http://elinux.org/Capemgr. Apr 26 02:24:26 a few random fragments of quite old information regarding capemgr? Apr 26 02:24:48 besides, I thought you were going to use cape-universal instead of an overlay? Apr 26 02:25:28 (either should work fine though) Apr 26 02:26:01 I have tried over and over. Did I mention I have failed each time? Apr 26 02:26:49 I looked at the Runtime Error: Problem with Cape Manager "error" and researched like a el cheap-o, depot. I came up with this old info. Apr 26 02:27:43 How would I know my board name? Apr 26 02:28:39 you're going to make a cape? Apr 26 02:28:47 e.g. I am working on a Rev. A5C for now. Apr 26 02:29:15 No...I just want this silly gadget to work to know I can produce four wires to make things work. Apr 26 02:29:35 the information on the page you linked is not relevant for you Apr 26 02:29:40 Oh? Apr 26 02:30:08 (I hope I can save you some further time and confusion by just saying that) Apr 26 02:30:16 zmatt: I looked at the site you had listed. Apr 26 02:30:32 It was for a cape (LCD cape). Apr 26 02:30:36 no Apr 26 02:30:39 Oh? Apr 26 02:30:49 *yawn* Apr 26 02:30:49 I made a mistake then. Apr 26 02:31:36 I looked at those PWM0, PWM1, and PWM2. It was from Seeed Studio's LCD capes. Apr 26 02:31:58 no, they were just committed at the same time as some overlay for an lcd cape Apr 26 02:32:09 Oh. That is odd. Apr 26 02:32:35 why? Apr 26 02:32:59 So, what I listed from Github can and will work? I am having a hard time believing that for some reason. Apr 26 02:33:16 Because...I tried all things possible already and I still get familiar errors. Apr 26 02:33:33 ... Apr 26 02:33:34 that github repository contains the source code for the overlays Apr 26 02:33:56 Sir, how can I introduce that code into my BBB? Apr 26 02:34:07 git clone, wget? Apr 26 02:34:08 04:18 < zmatt> again, as I already said, the compiled dtbos are probably already in /lib/firmware/ Apr 26 02:34:11 zmatt: Can you think of a good reason to have OSC1 (the 32K xtal) given the state of the RTC? Apr 26 02:34:29 ds2: yes, it's used in deep sleep Apr 26 02:35:16 zmatt: to wake up from it? there is hints of a RC osc Apr 26 02:35:59 to keep the time while in it, and wake up from it if you wish Apr 26 02:36:09 rc osc is known to be very *very* inaccurate Apr 26 02:36:24 *nod* Apr 26 02:36:39 like getting 50% frequency error should not be viewed as strange Apr 26 02:36:44 if the premise is the RTC is broke and one adds an external RTC, I don't see how that matters Apr 26 02:37:00 rtc broken? in what sense? Apr 26 02:37:06 afaik it works fine Apr 26 02:37:06 yes, it is like -50%, +800% percent Apr 26 02:37:11 RTC draws too much current Apr 26 02:37:25 that's not "broken" as such Apr 26 02:37:36 depends on use Apr 26 02:37:51 that's broken enough to add an external one Apr 26 02:37:54 also, if used with the tps65217 then you can't poweroff without the rtc Apr 26 02:38:18 doh.. that is a nastier detail I forgotten about Apr 26 02:38:36 'k the xtal will stay (trying to strip the BOM) Apr 26 02:38:38 maybe see if the tps65218 is of any interest Apr 26 02:39:16 ti even lets you program that one, if you sign a waiver Apr 26 02:39:58 that's a bigger change then I want at this stage Apr 26 02:41:47 ok :) I'm not even claiming suitability for any particular purpose, I just felt like making you aware of its existence (in case you weren't already) Apr 26 02:43:29 *nod* Apr 26 02:43:35 oh, keep in mind that if you want a pmic event to be able to wake the system up from deepsleep, you should connect its irq to some gpio0 pin instead of "nmi" Apr 26 02:44:10 (afaik) Apr 26 02:44:19 besides EXTINT? Apr 26 02:44:31 extint, nmi, whatever they called it Apr 26 02:44:38 (different things in different places) Apr 26 02:44:51 ah Apr 26 02:45:23 not sure though, I don't remember immediately whether the intc remains powered in the lowest sleep states Apr 26 02:56:21 Yes...zmatt! You were right. All those files are located in /lib/firmware. Apr 26 02:56:23 Cool! Apr 26 02:56:39 Now...how can I utilize them? Apr 26 02:57:54 04:19 < zmatt> in the same way as you already have used overlays previously Apr 26 02:58:06 I have never used an overlay. Apr 26 02:58:10 I think. Apr 26 02:58:12 BB-ADC Apr 26 02:59:12 Right...but, but, but. Can I have multiple lines of capmgr.enable_partno= ? Apr 26 02:59:28 I have three wires that need to be read. Apr 26 02:59:44 ... Apr 26 02:59:47 if I had to guess I think you probably need to list multiple overlays comma-separated **** ENDING LOGGING AT Wed Apr 26 03:00:00 2017