**** BEGIN LOGGING AT Wed Jul 03 02:59:58 2013 Jul 03 09:48:54 what does usr2 indicate on the BBB? Jul 03 09:52:58 I see.. the CPU activity Jul 03 09:57:04 panto: is it advisable to pause a process for a while if running an infinite for loop? I'm getting a constant usr2, otherwise Jul 03 09:58:01 hatguy, err, why is it running an infinite for loop without ever sleeping? Jul 03 09:58:28 panto, it's just an implementation of the arduino loop() and it doesn't have anything in it yet Jul 03 09:58:44 ugh Jul 03 09:58:50 for(;;) loop(); Jul 03 09:58:57 look, the system will work Jul 03 09:59:16 very sluggishly I think? Jul 03 09:59:17 but the scheduler will pick up this process as a hog Jul 03 09:59:22 hatguy, no, not at all Jul 03 09:59:35 and it will drop it's priority (dynamically) Jul 03 10:00:01 panto... ah i see... and what can be the consequences? Jul 03 10:00:09 so if you don't care about having a bit of a higher latency you'll be fine Jul 03 10:00:22 but, it's not fit for a system service to do that Jul 03 10:00:40 arduino isn't event driver I gather? Jul 03 10:00:52 hmmm.... nope.... Jul 03 10:01:02 pos Jul 03 10:01:12 oh well, if you can live with it you'll be fine Jul 03 10:01:17 hehe Jul 03 10:01:29 you can always lower your process priority Jul 03 10:02:02 linux/unix is built to handle that kind of workloads well, just don't expect not to have latency problems Jul 03 10:02:20 Hmmm... I just don't want people thinking that the BBBs slow cause they didn't put anything inside the loop. I guess that won't be a problem Jul 03 10:03:08 power draw will be higher of course Jul 03 10:03:18 I find it hard to believe that arduino works like that Jul 03 10:03:34 I mean really? there's no wait for interrupt/event or somethin? Jul 03 10:03:37 *something Jul 03 10:04:00 Well it's a uC.... AFAIK, there is no such thing in software at least... there could be some hardcoded stuff... Jul 03 10:04:28 let me check Jul 03 10:05:27 https://github.com/arduino/Arduino/blob/master/hardware/arduino/cores/arduino/main.cpp looks like they have added an extra line Jul 03 10:05:54 oh boy, it's retarded Jul 03 10:07:12 hehe... and some interrupts are enabled for some housekeeping but otherwise, that's it Jul 03 10:07:47 hatguy, just carry on as it is Jul 03 10:08:05 let's sync a bit later if we can move the same code to run on the PRUs Jul 03 10:08:25 that environment would be much better suited for stuff like that Jul 03 10:08:56 I would try to sneak in some kind of logic just before calling loop() for waiting for events Jul 03 10:09:30 I don't know about the details of your implementation, but a select/poll call would help Jul 03 10:09:39 panto, yeah... looks fine except when someone wants to turn that LED off... yeah will talk to prpplague about the PRUs... don't have much knowledge about them atm :( Jul 03 10:10:10 RPU support is just not ready yet, so carry on as it is Jul 03 10:10:22 we'll see what we can do about the busy loop Jul 03 10:10:57 I'll carry on with it right now... I don't know about select/poll though... I'll look it up Jul 03 10:10:59 thanks Jul 03 11:30:31 * vvu greets all the people here! Jul 03 11:34:24 * anujdeshpande greets vvu in return ! Jul 03 11:36:05 how is coding going ? Jul 03 11:41:15 vvu: greetings! code is behaving atm... how's yours? Jul 03 11:48:55 hacking all the thinks i can. Jul 03 11:51:15 jj2baile, sorry, I meant to get to your pru stuff this morning but found I should probably get an updated bbb image first, thus I've found the emmc flasher is slow as an old dog on a hot day Jul 03 11:51:27 I have meetings this morning but I'll try to fit in pru playing Jul 03 11:56:54 hi everybody Jul 03 11:58:14 hello! Jul 03 12:00:49 2day we have meeting right ? Jul 03 12:01:01 uh oh yes Jul 03 12:01:46 vvu: one question Jul 03 12:01:50 yep Jul 03 12:01:50 this rndis setup Jul 03 12:02:04 where it sends something on the INT endpoint Jul 03 12:02:10 does the reply go via that too? Jul 03 12:03:11 i don`t really know how it works. read a bit the micro$**t documentation but did not have info about how it goes the direction. Jul 03 12:03:20 when i`ll go home i will see the direction of the endpoint Jul 03 12:20:08 I'm the one working in the beagle-ros project. jkridner asked me to join you today so i'll be around Jul 03 12:20:29 Please feel free to share any comment, tips or critics regarding the project Jul 03 13:21:38 av500: direction is IN for that endpoint Jul 03 13:21:49 device to host Jul 03 13:23:16 so Jul 03 13:23:21 even if we dont get that INT Jul 03 13:23:26 we could send the reply Jul 03 13:23:33 maybe Jul 03 13:24:14 the reply needs to be sent on the bulk EP ? Jul 03 13:24:25 I guess so Jul 03 13:25:07 now some hexdumps from the usb analyzer would be great, just hardcode them in my app and send them over if there is nothing specific there to be modified Jul 03 13:26:01 I have it here now Jul 03 13:26:04 I can try tomorrow Jul 03 13:26:41 perfect Jul 03 13:27:05 I'd like to share an issue that i've been fighting with lately, maybe somebody has encounter something like this before and can share some thoughts Jul 03 13:27:09 https://github.com/bmwcarit/meta-ros/issues/99 Jul 03 13:27:34 I believe it's cmake related Jul 03 13:27:52 i'm using the Angstrom with the last cmake ipk Jul 03 13:28:04 the 2.8.8 Jul 03 13:28:18 i guess it would be nice to test the communication in a non-rdis driver environemnt if possible on a nexus10*you have one if i recall right*. then with rndis support in the kernel. and compare the dumps Jul 03 13:28:35 yes Jul 03 13:29:09 ok i`m off the radar until the meeting, doing kernel+initrd combination. Jul 03 14:05:50 panto: ping. ka6sox recommended to speak with you about booting a kernel with initramfs and dts in u-boot. i am tftping stuff there and having some trouble with the u-boot bootm command. i need to mkimage all the files *initramfs and dts*? Jul 03 14:06:12 why do you need an initramfs? Jul 03 14:06:41 to have a small shell after i boot from usb Jul 03 14:06:48 i am doing the android boot project Jul 03 14:07:00 send all the things from android over usb to u-boot Jul 03 14:15:17 i`m curious if i need to mkimage the dtbs Jul 03 14:15:47 i am doing bootm kernelAddr initramfsAddr dtbsAddr Jul 03 14:16:31 vvu|Mobile: did you try to append the DTB? Jul 03 14:16:42 during the kernel biuld? Jul 03 14:16:42 trying now but u-boot does not recognize it Jul 03 14:16:52 uboot does not know about it Jul 03 14:16:53 during kernel build no, trying in u-boot Jul 03 14:16:53 at all Jul 03 14:16:59 no Jul 03 14:17:02 not the same Jul 03 14:17:11 if the DTB is appended its part of uimage Jul 03 14:17:16 and uboot does nothing Jul 03 14:17:25 * vvu|Mobile is lost Jul 03 14:17:29 sorry, was otp Jul 03 14:17:48 I haven't done initramfs for quite a long time Jul 03 14:17:54 mhmh so how should i append it ? Jul 03 14:18:02 but has there been a problem on the usual way? Jul 03 14:18:19 i don`t really know the usual way of booting using dtb Jul 03 14:18:41 now i have kernel and initramfs separate both mkimage'd Jul 03 14:19:43 vvu|Mobile, are you using u-boot? Jul 03 14:19:48 yep Jul 03 14:20:08 if you're using it, then you need to supply the address of both the kernel and the dtb Jul 03 14:20:34 yep, kernel gets recognisied but u-boot does not recognize dtb Jul 03 14:20:38 http://pastebin.com/1hbMtgD7 Jul 03 14:21:08 does that make things clear? Jul 03 14:21:09 vvu|Mobile: maybe pastebin your boot log Jul 03 14:21:14 one sec Jul 03 14:21:19 [16:15:47] i am doing bootm kernelAddr initramfsAddr dtbsAddr Jul 03 14:22:47 http://pastebin.com/bRtrJQZq Jul 03 14:23:29 my dtb is taken directly form arch/arm/boot/dts Jul 03 14:23:39 did you load a dtb at 0x81000000 Jul 03 14:23:55 and are you sure it's not overlapping? Jul 03 14:24:06 yep i`m tftping one Jul 03 14:24:29 no, after full tftp checked again the initramfs with iminfo and was ok so no overlap Jul 03 14:24:32 before you boot, dump the first few bytes at the indicated addresses Jul 03 14:25:19 what command is for dumping? Jul 03 14:25:48 md Jul 03 14:26:33 md .b 0x81000000 20 ? Jul 03 14:27:05 md.b Jul 03 14:27:38 http://pastebin.com/yii4g4Fs Jul 03 14:29:22 http://pastebin.com/59QSmWeC Jul 03 14:29:30 use the fdt command to try and debug it Jul 03 14:31:43 libfdt fdt_check_header(): FDT_ERR_BADMAGIC Jul 03 14:31:46 mhmh bad magic number? Jul 03 14:32:26 there you go Jul 03 14:32:39 so either you tftp a bad dtb file Jul 03 14:32:50 or you're overwriting it Jul 03 14:53:17 mhmh the dtb is the last one tftped so no overwrite Jul 03 14:57:49 what is the console for 335x? ttyO0 ? Jul 03 15:00:46 yes Jul 03 15:05:58 now root=/dev/ram ? in the bootargs? Jul 03 15:06:31 I think so for initrd Jul 03 15:14:27 ok at least kernel loaded but somehting tried to kill init Jul 03 15:14:43 what did you change? Jul 03 15:14:47 to make it load? Jul 03 15:15:25 in the am335x_evm.h config from u-boot the fdt has a specific address Jul 03 15:15:30 i was tftping in another place Jul 03 15:15:38 and when i did fdt header told me nothing was there Jul 03 15:15:51 so i just changed the address with fdt addr $address Jul 03 15:15:54 then it worked Jul 03 15:16:01 and the bootargs, console and other stuff Jul 03 15:16:07 ah Jul 03 15:16:59 meeting today in about 44 minutes, right? Jul 03 15:17:04 right Jul 03 15:17:09 k, thanks, av500 Jul 03 15:17:11 reminds me to cycle home :) Jul 03 15:17:27 * bradfa wishes he could cycle home Jul 03 15:24:24 av500: http://pastebin.com/EwXbt38x some hint ? Jul 03 15:24:53 truncated log is truncated Jul 03 15:25:34 yeah. i cant`t scroll in Screen to copy everything Jul 03 15:27:32 av500: http://pastebin.com/KjPAYxpK did it Jul 03 15:28:20 bradfa, yes Jul 03 15:28:39 ctrl-a+esc to scroll Jul 03 15:28:43 yep Jul 03 15:43:11 morning koen Jul 03 15:43:59 * ka6sox goes to get coffee prior to meeting Jul 03 15:44:07 gm, will get a quick bite, mgiht be a little after 6 before I am back Jul 03 15:45:30 howdy eFfeM Jul 03 15:47:03 jj2baile, you here? Jul 03 15:47:49 ka6sox: any hint why i get this nice panic http://pastebin.com/KjPAYxpK ? Jul 03 15:48:46 hey ka6sox Jul 03 15:50:29 vvu|Mobile, not enough coffee yet...slow start today. Jul 03 15:50:36 okidokie Jul 03 15:50:38 10 minute warning Jul 03 15:57:48 hi Jul 03 15:58:04 theres supposed to be a meeting right now ? Jul 03 15:58:14 *awfully quiet here* Jul 03 15:58:20 *crickets* Jul 03 15:58:28 in 2 minutes I think Jul 03 15:58:47 koen: ping.. Jul 03 15:59:18 ka6sox: yep Jul 03 16:01:28 ZubairLK: pong Jul 03 16:01:40 I guess, someone should commence the meeting? Jul 03 16:01:41 what do i do with the patches for the 3.8 kernel Jul 03 16:02:05 koen: I read correctly via /sys/bus/iio/iiodevice/in_voltage*raw Jul 03 16:02:14 jkridner *was* here... Jul 03 16:02:21 I read correctly via in_voltage*_scale Which is scaled at 1.8V for the BBB Jul 03 16:02:37 ZubairLK: email them to panto and me and we'll have a look at them Jul 03 16:02:40 I added a patch to keep the bone-helper as is as well. And corrected. Jul 03 16:02:56 should I email the github link? or the patches directly Jul 03 16:03:13 ZubairLK, git send-email works Jul 03 16:03:23 we'll need to review them a bit too Jul 03 16:03:25 k Jul 03 16:03:46 I'll refine the descriptions a bit then :) Jul 03 16:03:50 and send them Jul 03 16:03:59 i'll cc gregkh as well Jul 03 16:04:57 sorry... got an untimely call Jul 03 16:05:07 let's kick things off! Jul 03 16:05:32 let's start with folks i haven't gotten blog posts from.... Jul 03 16:05:46 ZubairLK: can you change the project entry to point to a blog? Jul 03 16:05:55 So anyway, in terms of my progress, I know i should be doing more blog posts, but i've figured it out now, so should be doing them more frequently henceforth. Jul 03 16:05:56 pointing to the github is great, but it doesn't give me an overview. Jul 03 16:06:09 jkridner: sure. its in the description. but it doesnt go blue for a hyperlink Jul 03 16:06:15 I'll switch places Jul 03 16:06:46 a lot of the current stage is planning, so myself and ka6sox shall be having a discussion aout the external interface through his cape a little later today Jul 03 16:07:47 jkridner: As well, currently what i'm trying to code up, is a simple feasibility test of can the PRU handle doing JTAG fast enough without need for the cape necessarily. Jul 03 16:08:39 ZubairLK: thanks. Guess I'll look for it after the meeting. Jul 03 16:08:51 ZubairLK: any other updates? Jul 03 16:09:07 jkridner: changed the project description. Jul 03 16:09:18 jkridner: 3.8 ADC one-shot reading via sysfs working :) Jul 03 16:09:55 k. Have you seen that the existing ADC driver gives old, stale values? Jul 03 16:10:07 jkridner: yup. thats patched. Jul 03 16:10:07 have you also seen that reading it too fast causes an error return? Jul 03 16:10:24 jkridner: via sysfs reading too fast giving busy? Jul 03 16:10:31 jkridner: that too is fixed.. Jul 03 16:10:34 yeah... Jul 03 16:10:35 sweet. Jul 03 16:10:40 this is for 3.8 Jul 03 16:10:52 i managed to keep the bone-helper ok as it is as well Jul 03 16:11:06 jkridner: the major modification that ppl on the outside will see is that DT changed slightly Jul 03 16:11:35 jkridner: previously used to be ti,adc-channels <8>, Now you have to say which channels. ti,adc-channels <0 1 2 3 4 5 6 7> Jul 03 16:11:57 k, any mentor for ZubairLK have any questions? Jul 03 16:12:12 and you get 1.8V scaled values via sys/bus/iio entries along with raw values Jul 03 16:12:33 jj2baile: thank you for planning to provide additional blog posts to help everyone keep track of your progress. Jul 03 16:14:33 all: so far, only tcort and vmayoral have provided videos introducing their projects. don't want to prioritize it over coding, but the videos are helpful to get folks tracking/helping on the projects. Jul 03 16:15:14 * vvu|Mobile completely forgot about the video. Jul 03 16:15:15 jj2baile: are you confident you can move beyond planning and into coding soon? Jul 03 16:15:48 jkridner, will post a video soon enough. Jul 03 16:15:58 jkridner: Yeah. I've already started coding some things. it can kind of happen concurrently at this stage Jul 03 16:16:16 vvu|Mobile: have you been able to move beyond where you were stuck with the USB drivers on Android? Jul 03 16:16:27 <_av500_> yes and no Jul 03 16:16:49 yep yes and no. still need to modify the kernel in order to get my app to talk with the board Jul 03 16:17:08 <_av500_> jkridner: we have a huge doubt that it would ever work on an unpatched android kernel Jul 03 16:17:16 jkridner: I asked gregkh and koen about freezing work for 3.8 in one-shot mode only and moving to 3.11. They were ok with it. Jul 03 16:17:21 /dev/iio is meant for continuous reading. It wont work for 3.8 because the driver doesn't support it. Adding support can take up a significant time as all the buffers change and irqs are added to the code. Patches exist in arago 3.2. But forward porting is a mess. Jul 03 16:17:25 so now I'm trying to get the adc working on 3.11.. And then i'll try to get /dev/iio working for 3.11. Jul 03 16:17:48 ZubairLK: makes sense. Jul 03 16:18:04 :) Jul 03 16:18:08 ZubairLK: I've seen panto has done a lot of work to rebase patches against mainline. Jul 03 16:18:23 jkridner: thats what i'm using as a base to get BBB to boot Jul 03 16:18:50 i'll add adc patches to it. Jul 03 16:18:55 jj2baile, I'll see you about midnight GMT Jul 03 16:18:58 vvu|Mobile, _av500_: are you happy you can come up with some alternative plan that produces useful code? Jul 03 16:19:10 <_av500_> jkridner: well, we can load Jul 03 16:19:15 <_av500_> jkridner: well, we can load MLO from android Jul 03 16:19:17 ka6sox: ok. Jul 03 16:19:19 <_av500_> so we can control the BBB Jul 03 16:19:24 vvu|Mobile, _av500_: would folks have to alter code on specific phones to perform "remote bootload"? Jul 03 16:19:30 <_av500_> but it needs patches so it is not for "millions of phones" Jul 03 16:19:36 _av500_: that's a nice milestone! Jul 03 16:19:39 <_av500_> yes Jul 03 16:20:00 <_av500_> jkridner: pointing peopple to "pls root your phone" Jul 03 16:20:10 <_av500_> would not be a great advertising message Jul 03 16:20:27 <_av500_> jkridner: probably on all phones Jul 03 16:20:33 av500, I'm sure google wouldn't mind Jul 03 16:20:37 would they? Jul 03 16:20:44 <_av500_> they dont care Jul 03 16:20:55 carriers? media? Jul 03 16:21:01 <_av500_> but its not an easy out of the box epxerience Jul 03 16:21:07 <_av500_> panto: that is not my concern Jul 03 16:21:15 <_av500_> its more that it will prevent a lot of use Jul 03 16:21:22 <_av500_> and I dont like to promote rooting Jul 03 16:21:28 <_av500_> will all the security risks Jul 03 16:21:32 rooting leads to kanging Jul 03 16:23:14 anujdeshpande, hatguy: thank you for the blog post. Jul 03 16:23:39 * jkridner also got good updates in blog posts from tcort and vmayoralv Jul 03 16:23:43 jkridner: Are you aware of our individual blogs? Jul 03 16:24:02 jkridner, sure ! we are blogging individually as well Jul 03 16:25:10 no, are those listed on the project page? you should probably mention them on the shared blog as well. Jul 03 16:25:32 * jkridner will eventually make a BeagleBoard.org GSoC planet of some kind. Jul 03 16:25:42 will do Jul 03 16:26:01 my posts to the BeagleBoard.org G+ community GSoC category have been a bit slow, sorry for that. Jul 03 16:26:17 http://meanbot.wordpress.com/ and http://anujdeshpande.wordpress.com/ Jul 03 16:26:22 hatguy: thanks Jul 03 16:26:28 np Jul 03 16:26:52 anyone blocked on hardware? Jul 03 16:27:13 jkridner: evtest works. but i'd still like a tsc to play around with :p Jul 03 16:27:16 <_av500_> I still dont have that yacht Jul 03 16:28:06 still waiting for the Mansion Jul 03 16:28:06 anujdeshpande: I have a Seeed tiny scope too (forgot the name of it). Love it. Jul 03 16:28:44 ZubairLK: k, I'll try to make sure an LCD is on its way to you. Were you able to follow how I suggested creating a test bench that would use PWMs to create a touch event? Jul 03 16:29:19 jkridner, I love it too ! the gdb for h/w :D . mines called a DSO nano v2 BTW Jul 03 16:29:48 anujdeshpande: ah, right. I have a DSO Nano (pre-v2) Jul 03 16:29:52 jkridner: i was able to follow. just a tad bit preoccupied to get it done. Jul 03 16:30:53 * jkridner is happy that anujdeshpande, hatguy, jj2baile, ZubairLK, tcort, vmayoral and vvu|Mobile are all engaged with the #beagle community and making progress in coding Jul 03 16:31:07 :) Jul 03 16:31:11 :D Jul 03 16:31:19 [x] tcort Jul 03 16:31:27 :) Jul 03 16:31:56 +1, like, retweet to what jkridner said Jul 03 16:31:57 any doubts to share? will everyone have blog posts for next week such that our check-in can go really fast and we can just focus on blocking items? Jul 03 16:32:11 jkridner: sure Jul 03 16:32:23 i think i need to update my blog with some new stuff. Jul 03 16:32:23 jkridner: sure. Jul 03 16:33:09 wrapping up official meeting in 3... Jul 03 16:33:13 jkridner, sure think ! Jul 03 16:33:22 wow fast Jul 03 16:33:26 :-) Jul 03 16:33:28 vvu where is your blog? Jul 03 16:33:32 2... Jul 03 16:33:36 beagleboot.vdev.ro Jul 03 16:33:39 tx Jul 03 16:34:09 * beng-nl has nothing to add, just here in case our case came up Jul 03 16:34:10 yeah need to update that thingie with some new info Jul 03 16:34:11 jkridner: FYI, we have a wiki too http://elinux.org/Userspace_Arduino Jul 03 16:34:24 1... Jul 03 16:34:34 jj2baile: what's the URL of ur blog? Jul 03 16:34:36 hatguy, is the plan to provide a redirect to that from the misspelled one? Jul 03 16:34:43 hatguy: if you have links to the blogs and everything else there, then having the project page point there is probably best. Jul 03 16:34:48 panto: here? Jul 03 16:34:53 ds2: http://zecozephyr.github.io/ Jul 03 16:35:00 yes Jul 03 16:35:01 thanks Jul 03 16:35:04 bradfa: no, prpplague has removed the redirect Jul 03 16:35:12 * prpplague is late due to doing some fcc testing Jul 03 16:35:13 ds2: will add more content soon Jul 03 16:35:15 *not provided Jul 03 16:35:21 there is a link though Jul 03 16:35:33 prpplague: your guys seemed to be in-sync and making progress, so you are excused. ;-) Jul 03 16:35:47 thoughts on adding the DT to 3.11. I simple added the following at the end of the BBB dt file Jul 03 16:35:50 <_av500_> prpplague: did you test out ok? Jul 03 16:35:50 jkridner: ahh.. ok... that makes sense Jul 03 16:35:51 jj2baile: okay.. think you mean some content :D Jul 03 16:35:58 ds2: :D Jul 03 16:36:00 _av500_: i failed, but the board passed Jul 03 16:36:06 consider the official part of the meeting over and feel free to continue discussions. Jul 03 16:36:19 &tscadc { Jul 03 16:36:21 status = "okay"; Jul 03 16:36:23 tsc { Jul 03 16:36:25 ti,wires = <4>; Jul 03 16:36:27 ti,x-plate-resistance = <200>; Jul 03 16:36:29 ti,coordiante-readouts = <5>; Jul 03 16:36:29 jkridner: ok we've been working hard on the basics, the other items should start falling into place quickly Jul 03 16:36:31 ti,wire-config = <0x00 0x11 0x22 0x33>; Jul 03 16:36:33 }; Jul 03 16:36:37 adc { Jul 03 16:36:39 ti,adc-channels = <4 5 6 7>; Jul 03 16:36:41 }; Jul 03 16:36:43 }; Jul 03 16:36:49 vvu: what part of it is requiring you to root? Jul 03 16:36:51 panto: couldn't find the old overlay things. so this should get me up and running to test the actual driver right? Jul 03 16:36:52 * vvu|Mobile needs to grab himself a bigger screen. eyes are going out of range with a 19" lcd Jul 03 16:36:54 ZubairLK: pastebin is your friend. :-) Jul 03 16:37:03 switching the kernel Jul 03 16:37:12 ZubairLK, the mainline tracking branch doesn't have the capes yet Jul 03 16:37:18 not root but still Jul 03 16:37:21 strictly speaking switching the kernel != rooting Jul 03 16:37:23 exactly Jul 03 16:37:24 yep Jul 03 16:37:30 vvu|Mobile: and this is just for the OTG stuff? Jul 03 16:37:32 or more? Jul 03 16:37:35 <_av500_> rndis Jul 03 16:37:39 more, rndis host driver Jul 03 16:37:41 it's going to be a slow process of cleaning up, and committing to the appropriate topic branch Jul 03 16:37:54 <_av500_> ds2: we do not see the RNDIS INT endpoint in android Jul 03 16:37:55 but, the capemgr does work Jul 03 16:38:04 if you compile your cape manually it should load Jul 03 16:38:10 <_av500_> so we cannot reply to INT requests Jul 03 16:38:27 panto: compile cape files manually? Jul 03 16:38:29 what happens if there is no kernel RNDIS driver? Jul 03 16:38:31 in android i have 2 interfaces int0 with one INT IN endpoint, interface 1 with 2 bulk endpoints Jul 03 16:38:34 <_av500_> ds2: nothing Jul 03 16:38:38 ZubairLK, just use dtc Jul 03 16:38:39 <_av500_> thats the problem Jul 03 16:38:41 i see nothing Jul 03 16:38:44 <_av500_> MLO waits for INT reply Jul 03 16:38:48 panto: But i used to do echo BB-ADC > /sys/devices/bone-cape etc.. Jul 03 16:38:48 <_av500_> er, ROM code Jul 03 16:38:49 the INT ep never appears? Jul 03 16:38:53 <_av500_> MLO we can patch Jul 03 16:38:54 panto: that file isn't there Jul 03 16:39:14 it is now Jul 03 16:39:15 same, interface 0 only INT IN endpoint Jul 03 16:39:16 workaround Jul 03 16:39:18 update your tree Jul 03 16:39:20 aha Jul 03 16:39:24 thanks! Jul 03 16:39:31 also, is it no int ep0 just in android or is that also in libusb? Jul 03 16:39:34 as I said, things go in incrementally Jul 03 16:39:44 did not test in libusb stuff Jul 03 16:39:45 panto: yup. dont worry about the adc patches. I'll handle them :) Jul 03 16:39:46 <_av500_> vvu|Mobile: ? Jul 03 16:40:23 trying to figure out if it is a kernel misfeature to not expose the INT ep or if it is just an android thing Jul 03 16:40:29 morning mluckham Jul 03 16:40:30 maybe i am doing something really stupid from the start Jul 03 16:40:35 <_av500_> I think we see the EP Jul 03 16:40:41 <_av500_> but we dont get any data Jul 03 16:40:50 <_av500_> trusting vvu|Mobile that he did that correctly Jul 03 16:40:51 oh Jul 03 16:41:05 and this is the enumeration ep? Jul 03 16:41:10 or a different INT ep? Jul 03 16:41:13 <_av500_> hmm Jul 03 16:41:16 <_av500_> good question Jul 03 16:41:30 the enumeration endpoint should be control type ? Jul 03 16:41:43 ka6soc - good morning (I am va3lkm) Jul 03 16:41:44 n/m, it should be control Jul 03 16:42:04 this doesn't make sense Jul 03 16:42:06 android does not expose enumeration EP in host API Jul 03 16:42:18 there are devices that just use INT ep's Jul 03 16:42:31 HID I think is one example Jul 03 16:42:41 <_av500_> hmm Jul 03 16:42:46 <_av500_> vvu|Mobile: connect a mouse :) Jul 03 16:42:52 2day and 2morrow will try to finish getting a shell with these patches in the kernel. after that i will look more into what is wront there Jul 03 16:42:54 mouse works Jul 03 16:42:56 tested Jul 03 16:43:11 mouse via kernel HID driver or? Jul 03 16:43:50 mouse on stock android kernel nexus 7 Jul 03 16:43:53 ka6soc: I've been playing with the Launchpad, waiting for BBB to come Jul 03 16:43:55 mluckham, can you join us about 0000Z? Jul 03 16:43:57 so via kernel HID driver Jul 03 16:44:25 <_av500_> vvu|Mobile: question is, does it work over java usb/libusb Jul 03 16:44:26 in the chat here? Jul 03 16:44:29 yes Jul 03 16:44:46 ah.mhmhm need to see Jul 03 16:45:06 1st need to charge all my devices :) Jul 03 16:45:26 hehehe Jul 03 16:46:09 ka6soc - I will try Jul 03 16:46:11 but as stated above. 1st i would want to have a working shell with all these patches and things. then come back and take the bugs one at a time Jul 03 16:46:22 at least *to have something than nothing* Jul 03 16:48:03 <_av500_> right Jul 03 16:48:05 cu then...I must head out for work. Jul 03 16:50:04 wonder if there is a missing permission Jul 03 16:50:37 nop, have all permissions Jul 03 16:51:11 declared them in a device_filter xml file and when i connect the bbb android asks if i want to grant permission Jul 03 16:51:22 and also tested via code if i have permissions over device Jul 03 16:54:08 no, permissions in your app Jul 03 16:54:24 android has this notion of permissions on a per app basis Jul 03 16:54:29 yep Jul 03 16:54:36 tested via code Jul 03 16:54:43 if the usbManager has permissions over the device Jul 03 16:55:04 I was thinking more of permissions on types of endpoints? Jul 03 16:55:18 mhmh no such thing as far as i know Jul 03 16:55:43 weren't you telling me about ep0? Jul 03 16:56:14 that the control EP is not shown ? Jul 03 16:56:26 something about interfaces Jul 03 16:58:12 ds2: from here i know about the control ep http://stackoverflow.com/questions/13280581/using-android-to-communicate-with-a-usb-hid-device/14167946#14167946 Jul 03 16:58:59 ds2: av500 this text describes my problem http://stackoverflow.com/questions/13280581/using-android-to-communicate-with-a-usb-hid-device/14167946#comment18248220_13327095 Jul 03 17:01:48 that suggests you can get data through an interrupt endpoint Jul 03 17:02:09 can you find the Missle Launcher demo? Jul 03 17:02:17 i have it in the sdk folder Jul 03 17:02:27 it`s a demo from android sdk Jul 03 17:04:01 that is supposely an interrupt endpoint xfer thing Jul 03 17:04:10 <_av500_> i have to leave, bbl Jul 03 17:06:51 me too, need to take some air. brb later to continue debugging stuff! Jul 03 17:15:45 jkridner, can you get any of the pru compiler people to show up on irc Jul 03 17:15:57 panto: not likely. Jul 03 17:16:06 e-mail not good enough? Jul 03 17:16:13 sure, that will do Jul 03 17:16:14 I could probably arrange a phone call. Jul 03 17:16:27 phone calls are intrusive Jul 03 17:16:37 k, send me something, I'll forward on and suggest pulling myself out of the loop to establish a direct connection. Jul 03 17:16:50