**** BEGIN LOGGING AT Fri Jun 24 02:59:58 2016 Jun 24 03:35:58 hmm Jun 24 13:20:56 alexhiam: there? Jun 24 13:21:12 alexhiam: so.. what is the plan about the cape?? Jun 24 13:22:06 alexhiam: looks like it is broken.. so I guess I'll just use the mpu-9250 and bmp-280 on the breakout board.. Jun 24 13:22:35 kiran4399: yeah, good thing you were able to get those! Jun 24 13:23:06 I assume the motor drivers and everything else is working Jun 24 13:24:03 alexhiam: I didn't check motor driver.. yet.. but the apis are done.. right now doing some last minute changes for mpu api.. Jun 24 13:24:36 alexhiam: But I think everything except the mpu and bmp are working.. Jun 24 13:26:07 kiran4399: the apis are done? like they're all switched over to their kernel drivers? Jun 24 13:27:38 alexhiam: yeah.. didn't you go through them?? I mean the button, led, pressure, adc are done and tested.. Jun 24 13:27:45 alexhiam: I've to test pwm and mpu.. Jun 24 13:28:23 yeah, I've gone through them a bit. I don't see the imu though, do you still have stuff to push? Jun 24 13:28:43 ah, it's in the root dir Jun 24 13:28:58 alexhiam: I put it there so that the build does'nt get failed :-P Jun 24 13:30:13 ahh, well it's alright for it to fail if it's on the thing you're currently working on. You can also create a new branch when you're working on something new like that, which is good git practice to get into Jun 24 13:30:45 alexhiam: will there any formal evaluation for me? Jun 24 13:32:35 alexhiam: like should I be there for you to ask questions at any point of time? Jun 24 13:35:28 kiran4399: I just have a form to fill out Jun 24 18:08:47 Visaoni, nerdboy, alexhiam ? Jun 24 18:09:16 * Visaoni is here Jun 24 18:10:55 nerdboy said something on another channel about 10 min ago, probably hasn't gone too far... Jun 24 18:11:35 how about we start the call in case there's any tinkering with google logins at the start Jun 24 18:18:29 Wormo: hey, yeah, I'm ready Jun 24 18:36:21 * nerdboy looking for chromebook... Jun 24 22:37:27 Visaoni: how goes it? Jun 24 22:48:32 Wormo: pretty good. although it just occured to me that I do need to have some control over gpio direction from the pru Jun 24 22:49:08 with a (very brief) google it looks like it's possible using ocp? Jun 24 22:49:44 you're going to need to turn around signals? Jun 24 22:50:06 my guess would have been setting pinmux from the linux side Jun 24 22:50:31 yeah, for the D0-11 bits. write to them for initialization & config stuff, then read data off them Jun 24 22:51:25 I thought the eval board had a workaround to use those other pins to control reset Jun 24 22:51:54 and the default registers might be good enough aside from always needing to control reset Jun 24 22:52:06 default register values, that is Jun 24 22:52:39 I didn't see anything on a cursory review that needed to be changes, e.g. it's in continuous capture Jun 24 22:53:35 but, if you don't have spare pins for the extra-reset-mechanism thingy, then I guess yes you'll need to turn them around Jun 24 22:53:55 I'd document that as TODO and move on though Jun 24 22:57:46 hm, yeah I suppose so. defaults to a few things I might not choose but I don't think it really matters. I guess the only thing is single-ended vs differential Jun 24 22:58:15 I would have to shove the reset off on the other PRU though Jun 24 22:58:28 I'll just leave it as a TODO, I think Jun 24 23:01:08 right Jun 24 23:57:02 Visaoni: around what time tonight are you planning to push work-in-progress? Jun 25 00:07:12 Wormo: no hard plans but (knock on wood) I expect first batch will be soon. moving through the higher level ADC control stuff now which should be pretty quick. just want to make sure things hold together through that then I'll get it up Jun 25 00:07:32 ok I'll come back to take a look tonight I think Jun 25 00:12:51 sounds good Jun 25 00:50:15 beaglebone green doesn't have enough blue blinky lites Jun 25 00:50:33 * nerdboy adds another one Jun 25 00:50:36 but it does have enough green ones? Jun 25 00:51:06 they didn't think of that i guess Jun 25 00:51:46 now it goes to 11 Jun 25 01:33:49 Wormo, nerdboy, alexiam: first batch is up. it's basically just a simple framework for using the PRUs to read batches of series from the ADC and push it over to userspace. all the storage/transfer stuff is just stubs though Jun 25 01:34:29 sounds good, keep un-stubbing and testing... Jun 25 01:34:49 *and push push push Jun 25 01:35:11 * nerdboy wants to see at least a WIP branch Jun 25 01:36:02 some questions first before I can unstub the storage stuff Jun 25 01:36:34 basically, what's the "proper" way to get a bunch of space on both the PRU-specific RAM, and the shared PRU RAM? Jun 25 01:48:58 i see memory map/registers in the *PRU.cmd files Jun 25 01:51:21 http://git.ti.com/pru-software-support-package/pru-software-support-package/blobs/master/examples/am335x/PRU_Hardware_UART/PRU_Hardware_UART.c <= hopefully helpful comments? Jun 25 02:05:09 http://processors.wiki.ti.com/index.php/PRU_Training:_PRU_PID_Motor_Demo Jun 25 02:05:27 http://processors.wiki.ti.com/images/9/9d/PRU_PID_DEMO.tar.gz Jun 25 02:06:04 sets up a shared struct, puts it into the shared memory area Jun 25 02:06:32 /* Shared memory setup */ Jun 25 02:06:41 #pragma DATA_SECTION(share_buff, ".share_buff") Jun 25 02:06:53 volatile far struct shared_mem share_buff; Jun 25 02:08:38 look in .cmd like nerdboy was saying for the linker instructions to put .share_buff into the shared PRU RAM Jun 25 02:09:01 .share_buff > GLB_BUF, PAGE 1 Jun 25 02:21:39 heading out for dinner, ttyl Visaoni **** ENDING LOGGING AT Sat Jun 25 02:59:58 2016