**** BEGIN LOGGING AT Wed Jun 08 02:59:59 2016 Jun 08 04:46:29 hmmmmm Jun 08 05:24:50 jic23 jic23_ jic23b alexhiam: there? Jun 08 06:23:22 ZeekHuge: What's up? Jun 08 06:25:19 Hey ! Sorry I am late Jun 08 06:25:22 Abhishek_, ^^ Jun 08 06:25:34 Just completing the report Jun 08 06:25:43 will be done in 20 minutes Jun 08 07:05:28 Hi Abhishek_ ! Jun 08 07:05:31 you there ? Jun 08 07:18:27 Hey Wormo ! you there ? Jun 08 07:31:18 hi Jun 08 07:31:33 I'm here ZeekHuge, read your report Jun 08 07:31:47 And ? Jun 08 07:32:09 what do you think about the project's progress ? Jun 08 07:32:18 I believe it too slow .. :( Jun 08 07:32:27 any suggestions please .. Jun 08 07:32:39 report itself is finne, and you made progress on non-sick days; I think you will gain momentum Jun 08 07:33:11 keep asking questions when you get stuck Jun 08 07:33:20 yeah but its 3rd report and :( no kernel module yet Jun 08 07:33:22 :( Jun 08 07:33:25 okay. Jun 08 07:34:13 this should be your first real full week, since you had school then illness Jun 08 07:34:51 thus things should go better without those distractions Jun 08 07:35:51 yeah. I will get the project back in pace ! Jun 08 07:36:01 Okay so, with ctags Jun 08 07:36:20 still not cooperating for you? Jun 08 07:36:49 They are a cool thing. yes, but how do i navigate to a declaration rather than definition ? of a function ? Jun 08 07:37:02 so far working cool ! Jun 08 07:37:46 and, also, there was no ~./.vimrc so I added those tag locations in /etc/vim/vimrc Jun 08 07:38:15 and then, can I add tags to different repositories ? how will vim differentiate ? Jun 08 07:38:15 hmm do you need to see declaration? normally definition is what I want to see, declaration is just boring boilerplate in comparison... Jun 08 07:38:58 ~/.vimrc is a thing you would create with settings like that Jun 08 07:39:16 yeah but, you see, I was navigating through the pru-software support package but didnt reach this page : http://git.ti.com/pru-software-support-package/pru-software-support-package/blobs/master/include/pru_rpmsg.h#line133 Jun 08 07:39:22 and the comments there ! Jun 08 07:39:40 you can add tags to different repositories, create them at the toplevel and vim will find according to which directory you are editing in Jun 08 07:39:41 becoz ctags took me to definition Jun 08 07:40:43 yes I can see that would be useful to turn up Jun 08 07:40:51 so it can be useful sometimes to go to the declaration .. Jun 08 07:46:57 Well I think it's the ctags side only indexing certain things by default Jun 08 07:47:16 if it adds more to index, vim should find them Jun 08 07:47:19 http://stackoverflow.com/questions/3655743/when-using-exuberant-ctags-what-options-to-you-use Jun 08 07:47:58 something like --c-kinds=+px Jun 08 07:49:28 okay .. trying .. Jun 08 07:54:54 yep ! got it working ! :) Jun 08 07:55:17 and to navigate along the tags use command ptnext ? right ? Jun 08 07:55:46 any other easy shortcut ? like Ctrl+] ? Jun 08 08:05:07 There's also a plugin for navigating tags you might like Jun 08 08:05:16 http://vim-taglist.sourceforge.net/images/taglist_perl.gif Jun 08 08:05:36 http://vim-taglist.sourceforge.net/ Jun 08 08:13:11 Hi Kiran4399 - in and out as ever, but kind of here. Jun 08 08:13:35 Fighting with trying to get part of chrome to build as a dll (well actually the unit tests - the dll builds fine) Jun 08 08:18:09 Kiran4399 - for reference I'm on UK time so tend to be around from about an hour ago but not always online. Jun 08 08:21:37 Kiran4399 - perhaps a quick summary of where things stand? Sounded yesterday like you need to dive in a bit in the kernel source to figure out what is kicking those errors out. Jun 08 08:21:59 Sometimes it's easier to be dumb and play chase through the source (with printks) than figure it out by staring at it. Jun 08 08:28:37 Kiran4399 - feel free to email me on jic23@jic23.retrosnub.co.uk for any longish questions. I only get to it a few times a day, but sometimes easier than IRC! Jun 08 08:29:08 jic23: Tough luck with the sensors.. Jun 08 08:29:22 uhuh. Jun 08 08:29:31 jic23: No luck for 4.4.9.. even by overlay and instantiating.. Jun 08 08:29:40 no luck even with 4.1 Jun 08 08:30:05 jic23: no surer if the capes sensors are really functioning?? Jun 08 08:30:38 jic23: anyway.... alexhiam: asked me to make the wiki and things first.. Jun 08 08:31:02 jic23: btw do you know how to boot bb black direclty from the sd card without flashing it? Jun 08 08:33:33 kiran4399: just dont use a flasher image ? Jun 08 08:34:09 ZeekHuge: well.. I am testing kernels so.. I need to have different sd cards.. Jun 08 08:35:16 oh ! then probably tftp boot will be useful I guess, never tried though ... :) Jun 08 08:36:35 err, yes - I have done it but can I remember... different question.. hohum. Jun 08 08:36:58 Quick google suggests it will default to a correctly configured sd card if there is one present. Jun 08 08:37:07 Grab a random standard image. Jun 08 08:37:17 Anyhow you did get something with i2c detect? Jun 08 08:37:40 If so, then it's unlikely things would be entirely dead. Jun 08 08:37:57 Do you have a logic analyser or scope? Jun 08 08:38:14 (they cheap ones others are using are great tool to have!) Jun 08 08:38:47 Then we need to play chase through the kernel - guessing by now you are set up to build your own kernels? Jun 08 08:41:50 Don't worry about this stuff - it's tedious but straight forward and a good learning experience! Jun 08 08:42:10 (kernel devs end up doing this all the time for probing bugs) Jun 08 08:43:17 jic23: what I am doing to test the strawson board is the robotics cape installer. Jun 08 08:43:44 jic23: I am seeing if I can run these sensors with userspace drivers.. Jun 08 08:49:00 back in 10 Jun 08 09:01:45 back - sorry - boss on a ramble around the office ;) Jun 08 09:02:22 Sure - userspace drivers not a bad idea - though I'd still get a scope of logic analyser available if possible... Jun 08 09:02:25 jic23: this is strage.. Jun 08 09:02:28 *strange.. Jun 08 09:02:54 jic23: I tested different sensors on the cape.. seems to be working.. Jun 08 09:02:59 jic23: but the imu.. not working? Jun 08 09:03:07 hmm. Jun 08 09:03:22 definitely sounds like probing time.. Jun 08 09:03:29 Had it working at any point? Jun 08 09:04:25 http://pastebin.com/HJCq7FgD Jun 08 09:04:41 http://pastebin.com/VugBg2Hq Jun 08 09:05:45 Got to be scope time... Jun 08 09:05:59 Would explain a lot if it's fried! Jun 08 09:06:24 Though could be the i2c bus that is having trouble in which case depending on your rework soldering skills, could patch to another bus. Jun 08 09:06:58 just to check, you hard powered board down before this? (can sometimes get such sensors wedged) Jun 08 09:12:21 jic23: not sure what you mean to say.. but I am currently booting the 3.8 kernel from the sdcard.. Jun 08 09:12:59 Sure - just worth making sure the board is completely powered down if you have previously been poking a sensor and it has stopped responding. Jun 08 09:13:09 Lot of state in these imus. Jun 08 09:13:22 Plus it's not unheard of for them to have bugs! Jun 08 09:13:51 Basically the classic computer support response 'Have you tried turning it off and on again?' Jun 08 09:13:53 :) Jun 08 09:16:24 jic23: ok.. will rebot it again.. Jun 08 09:16:49 always good to run tests like this a couple of times. Make sure you completely unpower it (i.e. unplug the Usb cable) Jun 08 09:26:27 jic23: segmentation fault now? Jun 08 09:26:47 huh? doing what? Jun 08 09:27:01 jic23: ran the ./test_imu Jun 08 09:27:13 hmm did the i2c-detect work? Jun 08 09:27:33 would imagine the error handling in test_imu may not be perfect... Jun 08 09:27:43 jic23: 34 is still there.. but 70 is gone.. Jun 08 09:27:52 but mpu is 0x68 right? Jun 08 09:27:52 what was 70? Jun 08 09:28:06 jic23: I think I must go and buy couple of mpu sensors.. Jun 08 09:28:14 i2c-detect is a little 'interesting' as it relies on pinging fairly random addresses. Jun 08 09:28:49 May be worth doing anyway - but do some ground work and check the i2c bus is working first. Jun 08 09:29:05 side job is to fix that seg fault in test_imu and send the fix upstream! Jun 08 09:29:37 No idea how good quality control is on the strawson capes - might just be a dead solder joint somewhere. Jun 08 09:29:40 jic23: tough life!! :-| Jun 08 09:30:31 *fun* :) Jun 08 09:30:59 Do make sure you documentation of the various steps you are going through is clear though. Jun 08 09:33:41 Also, sounds like other sensors are fine so need to get them working with current drivers. Jun 08 11:23:19 Right then.. I am purchasing a bunch of mpu6050 and bmp280 incase something fails... Jun 08 11:53:57 kiran4399 - on suitable breakouts? Jun 08 11:55:45 yeah.. those chips.. Jun 08 11:55:49 jic23: Jun 08 11:55:59 on boards. Jun 08 11:56:04 cool, just checking ;) Jun 08 11:56:21 dx.com do them cheap but take a while to actually show up.. Jun 08 11:57:24 jic23: I think I am sure that the sensor is not responding.. Jun 08 11:57:34 got a scope on it? Jun 08 11:57:45 no.. how to check? Jun 08 11:58:02 but I put the cape on beaglebone and it is not coming out.. Jun 08 11:58:03 :-( Jun 08 11:58:05 what test equipment do you have? i2c is slow. Jun 08 11:58:11 out? Jun 08 11:58:13 I am in the lab.. Jun 08 11:58:17 I got everything. Jun 08 11:58:30 cool. Jun 08 11:58:51 Then just get probes on the i2c-2 clk and data. Jun 08 11:58:58 This stuff is slow, so easy to see. Jun 08 11:59:32 First of all do it at the beaglebone connectors (or on the back of the shield if it passes through). Jun 08 11:59:46 + make sure good earth etc (no idea how much electronics you have done ;) Jun 08 12:00:22 Then with the help of wikipedia, should be able to work out what transfers are going on... Jun 08 12:00:33 (or more likely whether any at all are) Jun 08 12:01:36 remember to grab pictures of traces for reporting what you've been up to as well. Jun 08 12:06:25 jic23: Ok.. so what should the probe show if it is working correctly? Jun 08 12:08:19 Clock should be pulsing up and down during message and data should correspond to the standard i2c format - google it or read the datasheet for the part. Jun 08 12:10:06 actually datasheet in this case doesn't contain much info. Jun 08 12:10:56 http://pdfserv.maximintegrated.com/en/ds/MAX1363-MAX1364.pdf or similar have more details and protocol is much the same. Jun 08 12:13:04 Basically start condition, address, read/write , ack, register address, ack data (may be read back) ack stop Jun 08 12:13:17 Usually easy enough to eyeball. Jun 08 12:16:35 alexhiam, Abhishek_,: When is our meeting? After the weekly meeting or before? Jun 08 14:01:42 kiran4399: isn't the bmp280 also on i2c2? Jun 08 14:02:14 your overlay is using i2c1 Jun 08 14:03:38 no.. I don't think so.. Jun 08 14:03:53 alexhiam: I am not sure.. Jun 08 14:03:55 according to the schematics it is.. Jun 08 14:04:07 alexhiam: I have strange feeling that the imu is not working.. Jun 08 14:04:30 alexhiam: because today I got the 3.8 7.9 debian on bbb and checked the robotics_cape installer.. Jun 08 14:04:40 alexhiam: all of them are working but imu.. Jun 08 14:05:11 http://pastebin.com/VugBg2Hq Jun 08 14:05:27 yeah, I saw the logs Jun 08 14:05:34 btw.. posted the weekly report.. Jun 08 14:06:11 kiran4399: you did try the full poweroff, unplug power completely from the beaglebone (count to 5 even), then plug back in and try? It's quite possible for i2c devices (esp. complicated ones like that) to get into a weird state then not respond Jun 08 14:06:18 alexhiam: luckily some of my friends were going to the store.. so asked them mpu 6050.. got 3 of them.. in case 1 of them does not work. Jun 08 14:06:29 saw the report, thanks Jun 08 14:06:43 alexhiam: tried about 5 times.. no luck. Jun 08 14:06:48 on breakout boards, I assume? Jun 08 14:07:06 alexhiam: obviously.. :-P Jun 08 14:07:39 alexhiam: seriously.. this week was a little painful ;,-( Jun 08 14:07:58 definitely possible there's a QC issue with the cape, especially with such a fine pitch part Jun 08 14:08:20 but you're learning so much more because of it ;) Jun 08 14:09:28 alexhiam: I am a little scared of failing if I don't meet the week's requirements according to the proposal..:-| Jun 08 14:09:52 alexhiam: anyway.. you are right.. I am learning a lot.. thanks a lot!!! Jun 08 14:11:00 kiran4399: issues like this come up, and projects can deviate from the timeline. Just make sure you're producing the required amount of content and it'll be alright Jun 08 14:11:12 yeah.. sure.. Jun 08 14:11:25 alexhiam: when shall we have the meeting? after or before? Jun 08 14:12:02 which is why I keep poking you for detailed logs of all the testing and debugging you're doing Jun 08 14:13:08 kiran4399: well, what do you feel like you need to discuss? I was thinking we'd nail down the APIs, but it might make sense to just keep focusing on the drivers until it's all working Jun 08 14:14:33 alexhiam: what about pru driver.. since you got it working on 4.4.. shall we start with the pru api and at the same side get the kernel drivers for mpu and bmp working? Jun 08 14:21:28 kiran4399: right. You could start in on the PRU stuff if you need a break from the sensors, though the PRU stuff does have much more kernel driver dev involved ;) Jun 08 14:39:50 ZeekHuge: nice pru notes! Jun 08 14:40:30 I had yet to dive too deep into the client driver stuff, glad you beat me to it :P Jun 08 14:41:33 :) Jun 08 14:41:37 Thank you :) Jun 08 14:42:24 we really need to compile all this stuff into some tutorials somewhere Jun 08 14:42:34 and then hope ti doesn't completely change it all again Jun 08 14:42:35 Yes .. Jun 08 14:43:37 I have more in my head to add to the notes, but its bit un-organized (even in my head) Jun 08 14:43:52 I have been reading the code ... so .. Jun 08 14:44:22 and I dont usually make notes so ... I am just developing with the habit. Jun 08 14:44:47 ZeekHuge: it's a good habit to have. My notes have saved me many times Jun 08 14:47:03 yeah .. I agree Jun 08 15:41:06 looks like we have all 7 progress reports! They're still not all coming in the day before the meeting, but we're getting closer... Jun 08 15:41:37 hey alexhiam I have pushed a modified test code over here:https://github.com/chanakya-vc/BBB-Gsoctry/blob/master/updated_spi/pru_spi0.c Jun 08 15:41:54 Can you test it? Jun 08 15:42:14 I think this should work.I incorporated your changes Jun 08 15:42:24 that you suggeted Jun 08 15:44:52 chanakya_vc: sure. One issue I see: (mosi>>7-i) - you want parens around the (7-i) as well to make sure that's happening before the bitshift Jun 08 15:46:32 alexhiam, Okay I will change that. Maybe you could change that locally and see if its working? Jun 08 15:46:38 <_av500_> 7 reports, I must play the lottery this week! Jun 08 15:47:08 chanakya_vc: you also still have the mosi<<=P8_11; Jun 08 15:48:00 alexhiam: The bb_blue api looks like this.. https://github.com/kiran4399/bb_blue_api/blob/master/libraries/bb_blue.c what do you th Jun 08 15:48:04 what do you think? Jun 08 15:48:09 will we have some copyright issues? Jun 08 15:48:09 Silly error on my part Jun 08 15:48:17 alexhiam, ^^ Jun 08 15:48:39 chanakya_vc: oh, also you don't generally want to do variable names like CLOCK_POL_PHA. All caps is typically used only for preprocessor defines Jun 08 15:49:13 kiran4399: no, we just need to make sure those conditions are met Jun 08 15:49:58 okay alexhiam. Is it compiling? Jun 08 15:50:08 yup Jun 08 15:51:31 alexhiam, Okay. I so hope that mosi works Jun 08 15:52:53 alexhiam: btw, I read your pruss notes.. what was the exact issue? Jun 08 15:54:01 kiran4399: what do you mean? Jun 08 15:54:22 alexhiam: https://groups.google.com/forum/#!topic/beagleboard-gsoc/amMNLt4EoHM Jun 08 15:54:46 chanakya_vc: hmm, for some reason I'm not seeing either pin change now... that doesn't seem right, I'm gonna reboot and try again... Jun 08 15:55:38 kiran4399: oh, you used to be able to do this: https://github.com/abhishek-kakkar/BeagleLogic/blob/master/beaglelogic-kernel-driver/BB-BEAGLELOGIC-00A0.dts#L232 Jun 08 15:56:19 but now it seems like pru_rproc will only load am335x-pru0-fw and am335x-pru1-fw Jun 08 15:57:21 alexhiam, one more error i spotted cpol and cpha Jun 08 15:57:29 both should be 0 Jun 08 15:57:38 yeah, I caught that Jun 08 15:57:47 I am so sorry for this alexhiam Jun 08 15:58:40 no worries Jun 08 15:59:18 <_av500_> countdown started... Jun 08 15:59:43 hmmm Jun 08 16:00:56 still not working alexhiam ? :( Jun 08 16:01:09 chanakya_vc: weird, yeah, clk and mosi are both stuck at 0. Tried different firmware and the pins toggle, so they are muxed right... Jun 08 16:01:19 hi Jun 08 16:02:18 hi Jun 08 16:02:47 alexhiam, hmmn will work on this after the meeting :( Jun 08 16:02:50 aloha Jun 08 16:03:03 Namastey everyone Jun 08 16:03:29 helo Jun 08 16:04:28 chanakya_vc: just noticed another issue: https://github.com/chanakya-vc/BBB-Gsoctry/blob/master/updated_spi/pru_spi0.c#L83 Jun 08 16:04:33 Cool ! It came just a hour ago ! https://github.com/RobertCNelson/linux-stable-rcn-ee/releases/tag/4.4.12-ti-r30 Jun 08 16:04:42 4.4.12 ! Jun 08 16:05:00 chanakya_vc: you're already shifting based on i, so you don't want that second shift Jun 08 16:05:40 Yes. But still clock would run alexhiam ? Jun 08 16:05:55 and we have the rproc drivers there https://github.com/RobertCNelson/linux-stable-rcn-ee/commit/96307ed7058e5ecc7832d7d9bd34e377f8ce25cf#diff-1afa4b0a9bb73fd62cdab192828284bcR2024 Jun 08 16:05:56 yeah, that's unrelated Jun 08 16:06:24 GM all Jun 08 16:06:25 <_av500_> oops Jun 08 16:06:28 <_av500_> hi Jun 08 16:06:32 <_av500_> dog ate my interwebs Jun 08 16:06:33 howdy Jun 08 16:06:40 <_av500_> 0) Hello Everybody! Jun 08 16:06:45 hi all Jun 08 16:06:50 hi Jun 08 16:07:07 <_av500_> 1) raise your hands if you are a GSOC student for BB.org Jun 08 16:07:12 hi Jun 08 16:07:17 hi Jun 08 16:07:21 i am Jun 08 16:07:27 ^ Jun 08 16:07:43 Good evening everyone Jun 08 16:08:36 <_av500_> 4... Jun 08 16:09:06 I am!! Jun 08 16:09:09 6 Jun 08 16:09:31 hi Jun 08 16:09:39 7 Jun 08 16:09:42 <_av500_> 7!! Jun 08 16:09:51 <_av500_> perfect Jun 08 16:10:01 <_av500_> Helo students, hello mentors Jun 08 16:10:08 <_av500_> welcome to another weekly meeting :) Jun 08 16:10:21 <_av500_> 2) reports Jun 08 16:10:29 <_av500_> of which I see also seven Jun 08 16:10:46 <_av500_> thanks for that Jun 08 16:10:55 <_av500_> please repeat all subsequent weeks Jun 08 16:11:24 Mm Jun 08 16:12:14 <_av500_> I assume that all the (minor) issues you reported have been raised with your mentors and are being worked on Jun 08 16:12:28 Sorry, that was Sebastian Jun 08 16:12:40 <_av500_> :) Jun 08 16:12:50 <_av500_> jkridner_: get him his own nick Jun 08 16:13:00 :) Jun 08 16:13:10 <_av500_> 3) hardware shipments Jun 08 16:13:25 <_av500_> I see that all of it has been almost taken care of Jun 08 16:13:36 <_av500_> any urgent HW issue still unresolved? Jun 08 16:13:57 ADC .. Jun 08 16:14:02 not urgent Jun 08 16:14:05 <_av500_> is that on its way? Jun 08 16:14:14 all good here Jun 08 16:14:36 <_av500_> ZeekHuge: not urgent turns into urgent quickly Jun 08 16:14:47 yes. Jun 08 16:14:49 <_av500_> ZeekHuge: so when will that be resolved Jun 08 16:14:52 _av500_: My robotics cape imu is not responding.. Jun 08 16:14:53 <_av500_> and what needs to be done? Jun 08 16:15:13 <_av500_> kiran4399: not good. Jun 08 16:15:22 <_av500_> sure its not SW related? Jun 08 16:15:30 <_av500_> anybody with the same cape that can test your SW? Jun 08 16:15:35 I will probably need it after a a week Jun 08 16:15:43 <_av500_> ZeekHuge: so is it being shipped? Jun 08 16:15:53 Dont know .. ? Jun 08 16:16:06 Not according to me .. Jun 08 16:16:22 _av500_: I think so.. I checked the sensor with the userspace driver(robotics_cape installer) and tested all the components... everything is perfectly working except IMU.. Jun 08 16:16:29 jkridner_, ^^ Jun 08 16:16:37 kiran4399, _av500_: I just ordered a breakout for that imu so I can test soon. kiran4399 also got some breakouts for it, so we should be fine if it is a hardware issue Jun 08 16:16:54 <_av500_> alexhiam: ok, I see you are on it Jun 08 16:17:12 Cape will be for sale real soon now. Jun 08 16:17:19 alexhiam: what IMU is it? Jun 08 16:17:28 9150 Jun 08 16:17:31 MPU9150 Jun 08 16:17:34 jkridner_: great, I was wondering Jun 08 16:17:40 MPU-9250 I think Jun 08 16:17:45 according to the rev D schematics Jun 08 16:17:59 9150 isn't available anymore Jun 08 16:18:04 <_av500_> ZeekHuge: please tell me about the ADC, where does it ship from? Jun 08 16:18:04 9250 Jun 08 16:18:25 alexhiam: is it 9250?? are you sure?? but the strawson website says 9150? Jun 08 16:18:47 _av500_, http://www.digikey.com/product-detail/en/linear-technology/DC782A-P/DC782A-P-ND/4766042 Jun 08 16:19:06 kiran4399: rev C had the 9150. you should be able to check by the markings on it Jun 08 16:19:12 <_av500_> jkridner_: are you shipping that ADC? Jun 08 16:19:27 wowsers, that's a serious ADC Jun 08 16:19:36 I shipped an ADC to nerdboy Jun 08 16:20:06 kiran4399: any of the 9 axis respond? the mag is largely independant of the accel/gyro Jun 08 16:20:08 alexhiam: then how can 6500(mpu-9250) work with 6050 driver? Jun 08 16:20:24 alexhiam: I thought it was 9150.. my bad. Jun 08 16:20:24 I think it might have been for a different project. Jun 08 16:20:40 ds2: I don't see anything on the i2c bus Jun 08 16:20:43 probally visaoni's? Jun 08 16:20:50 probe is failing with the error code -121 Jun 08 16:20:58 kiran4399: oooooh, is it a 6500 in there?? If that's the case it's got a different whoami value, and you'll need to put 6500 in the DT instead of 6050 Jun 08 16:21:04 kiran4399: oh my... do you see the I2C ROM on the cape? Jun 08 16:21:08 <_av500_> jkridner_: the one to nerdboy is for Visaoni, no? Jun 08 16:21:08 iscdetect is not to be trusted Jun 08 16:21:24 alexhiam: Noooooooooooooooooooooooooo!! Jun 08 16:21:28 that should be correct av500_ Jun 08 16:21:35 the 6500 can work with a 6050 driver Jun 08 16:21:41 alexhiam: anyway.. I think I can again test it.. Jun 08 16:21:48 ds2: are you sure? Jun 08 16:21:51 9xxx is 6500 + Mag Jun 08 16:22:02 kiran4399: yes unless you are using the extra features Jun 08 16:22:08 yup, should work fine, just need to change that in the dt Jun 08 16:22:16 basic gyro/accel should work fine in the 6050 and 6500 Jun 08 16:22:27 I'm sure the whoami reg is being checked in the probe Jun 08 16:22:27 <_av500_> ds2: m_w: Abhishek_: who is taking care about this ADC for ZeekHuge? Jun 08 16:22:51 <_av500_> alexhiam: can you postpone that until after the meeting? Jun 08 16:22:55 not sure Jun 08 16:22:57 <_av500_> kiran4399: ^^ Jun 08 16:23:08 _av500_: Not me. I was scrubing the docs Jun 08 16:23:11 yeah, sorry _av500_ Jun 08 16:23:32 <_av500_> ds2: m_w: Abhishek_: can you please after the meeting sort out that ADC? Jun 08 16:23:34 Do I need to send another ADC board? Jun 08 16:23:39 I thought ZeekHuge pasted the link last week and someone (was it jkridner) was to take care of the order Jun 08 16:23:44 jkridner: I think so Jun 08 16:24:07 <_av500_> please sort this out today Jun 08 16:24:14 *nod* Jun 08 16:24:33 is visaoni using the same ADC? Jun 08 16:24:40 I ordered what nerdboy put in the spreadsheet. Jun 08 16:24:55 Who else is giving me an order? Jun 08 16:25:04 <_av500_> ADC EVM (DC782A-P) Jun 08 16:25:08 jkridner_: I thought you got a d/k link for ZeekHuge's? Jun 08 16:25:08 <_av500_> it says in the sheet Jun 08 16:25:15 (per last week) Jun 08 16:25:56 <_av500_> time is flying, can you please sit down after the meeting and sort it out? Jun 08 16:25:59 <_av500_> I want to move on Jun 08 16:26:07 http://www.digikey.com/product-detail/en/linear-technology/DC782A-P/DC782A-P-ND/4766042 Jun 08 16:26:10 jkridner_, ^^ Jun 08 16:26:12 okay Jun 08 16:26:14 <_av500_> ok Jun 08 16:26:22 <_av500_> who was on the list for this week reporting here? Jun 08 16:26:42 me ! Jun 08 16:26:47 I am expecting to hear from mentors on this. Jun 08 16:26:48 and chanakya_vc . Jun 08 16:26:52 <_av500_> then go on Jun 08 16:26:54 Yes me too Jun 08 16:27:00 Can I go first? Jun 08 16:27:01 <_av500_> jkridner_: yes, me too Jun 08 16:27:03 <_av500_> sure Jun 08 16:27:10 <_av500_> you have the stage Jun 08 16:27:36 Namstey everyone,my project progress is as follows: Jun 08 16:28:16 I have successfully written the basic frame work for SPI and compiled the code using the makefile Jun 08 16:28:39 given in the examples in of the PRU software support package Jun 08 16:29:39 However,the code isnot producing the expected result Jun 08 16:30:29 So I am still working on the mosi bit of the code.Although the code has compiled correctly and I have been able to load it to the PRU's Jun 08 16:30:52 Next the problems that I foresee: Jun 08 16:31:30 I have to still come up with a method that allows the PRU's to talk to the shared DDR mem Jun 08 16:32:13 <_av500_> chanakya_vc: but pru talking to DDR is a common thing, no? Jun 08 16:32:17 As pointed out to me by mentors earlier there was a method of upcalls and downcalls Jun 08 16:32:20 <_av500_> there should be exmaples Jun 08 16:32:36 _av500_: not with the new pru_rproc :/ Jun 08 16:32:49 But it no longer exists in the present in the latest kernel Jun 08 16:32:56 _av500_, ^^ Jun 08 16:33:29 So the only way I can see so far is using RPMsg which may not be the most ideal way of doing it Jun 08 16:33:56 Anyone look for TI release examples? Jun 08 16:34:09 <_av500_> bradfa: mdp ^^^ Jun 08 16:34:34 jkridner_: yeah, only an example for the 12kB shared PRU-ICSS RAM, no examples of going through the L3 at all Jun 08 16:34:36 _av500_: yes, we are aware of this issues Jun 08 16:34:59 I am still researching on it.Until and unless I can find a way to do it,there would no way to store miso and also receive commands from userland Jun 08 16:35:18 or go with a A8 pull from PRU strategy Jun 08 16:35:32 PRU interrupts A8, A8 does a burst read Jun 08 16:35:38 <_av500_> bradfa: ok Jun 08 16:35:44 that was good enough for video capture Jun 08 16:35:51 Alexhiam: does that change? Jun 08 16:36:06 jkridner_, _av500_ Even I can't find any examples anywhere.So still researching on a way Jun 08 16:36:17 *that Jun 08 16:36:24 <_av500_> chanakya_vc: so you have to write the example :) Jun 08 16:36:29 <_av500_> lead the way Jun 08 16:36:42 jkridner_: you mean is it different going through the L3? yeah, it's not memory mapped in the PRU-ICSS Jun 08 16:37:04 _av500_, I surely will :) I am just mentioning the problems that I see so far : ) Jun 08 16:38:08 <_av500_> ok Jun 08 16:38:09 <_av500_> yes Jun 08 16:38:14 looks like there is API for the A8 to read from PRU RAM: https://github.com/ZeekHuge/BeagleScope/blob/master/docs/current_remoteproc_drivers.notes#L119 Jun 08 16:38:27 Apart from this, I will post the pictures of the capture from logic analyzer in a day or two,when I get the code to produce the correct waveforms. Jun 08 16:38:39 <_av500_> good, looking forward to that Jun 08 16:39:23 Apart from this,I have created a website vaibhavchoudhary.com Jun 08 16:39:32 alexhiam: IIRC - the PRU RAM is mapped in already...just donno if the rproc stuff expose that properly Jun 08 16:39:48 I am going to be adding a blog section to this and posting stuff there too Jun 08 16:40:07 <_av500_> chanakya_vc: good. Jun 08 16:40:13 <_av500_> thanks for the progress report Jun 08 16:40:22 Anything else? Jun 08 16:40:29 chanakya_vc: keep up the good work! :) Jun 08 16:40:37 <_av500_> chanakya_vc: no :) Jun 08 16:40:46 <_av500_> ZeekHuge: you are on! Jun 08 16:40:56 stupid isp... Jun 08 16:40:56 yep ! Jun 08 16:41:20 * nerdboy sneaks into the back of the room... Jun 08 16:41:24 okay so now the 4.4.11-ti-r29 is up and going good with the rproc drivers there Jun 08 16:41:43 * Wormo snuck already, hi nerdboy Jun 08 16:41:57 before that i was trying to port the drivers to the kernel but there were significant changes that changed the versioning number Jun 08 16:42:13 Then I was waiting for 11-ti-r30 Jun 08 16:42:23 as rcn told it will be out soon Jun 08 16:42:36 and I fell ill and in a loss of 2-3 days Jun 08 16:42:51 After that I started with the current remoteproc drivers Jun 08 16:42:58 in 4.4.11-ti-r29 Jun 08 16:43:15 thanks to alexhiam for details on getting started Jun 08 16:43:28 and I have made some exmaples Jun 08 16:43:43 to do I/O and communication with the userland Jun 08 16:43:49 using rpmsg Jun 08 16:44:05 Then there are some notes for a client driver Jun 08 16:44:29 As I will have to do in-kernel communication .. I guess these notes will help a lot Jun 08 16:44:53 Further .. I have been reading the source and Jun 08 16:45:10 I have some understanding but its a bit messed up in my head Jun 08 16:45:23 and I will try to put it on paper and get to the mentors Jun 08 16:45:43 Okay so as of now ... I think that Jun 08 16:46:06 the rpmsg communicates with a virtual device that is itself on mpu Jun 08 16:46:29 and that virtual device is having the virtual buffers Jun 08 16:46:38 where the pru writes into Jun 08 16:46:56 So I guess it is same as making pru write into a location in DDR Jun 08 16:47:25 The instruction in the fw that opens up the OCP port for prus is what suggests this to me Jun 08 16:48:12 So, what we need to do is just use the standard APIs already in the kernel defined by the current rproc drivers Jun 08 16:48:27 and get handle of the various devices Jun 08 16:48:54 Then we will ultimately have and handle of the the mailbox Jun 08 16:49:10 and we can communicate further with the PRUs Jun 08 16:49:26 So. for the next week ... Jun 08 16:49:49 this will be my priority to get inkernel communication with the PRUs Jun 08 16:50:00 and for the fw side Jun 08 16:50:04 where does the mailbox come in? Jun 08 16:50:24 nm, i can wait... Jun 08 16:50:37 okay so ... for the fw side Jun 08 16:50:53 I think I will be going with the beaglelogic approach Jun 08 16:51:11 acquiring data using one pru and communication using the other Jun 08 16:51:48 And I guess, since lot have changed now in the kernel, there will be significant changes in the fw too Jun 08 16:51:55 oh yes ... and Jun 08 16:52:06 while playing with the PRUs Jun 08 16:52:23 I fried up a few p8 pins Jun 08 16:52:41 so a resistor greater than 470 ohms ! Jun 08 16:52:50 caution for others ! Jun 08 16:53:04 and probably enough sleep. Jun 08 16:53:09 ZeekHuge: ah, driving an led? Jun 08 16:53:27 you guessed it Jun 08 16:53:30 with the current drivers .. there are some error, not sure what they are ... Jun 08 16:53:37 <_av500_> good thing jkridner_ put so many pins on P8.... Jun 08 16:53:52 and i am unable to reproduce them on will .... but there are Jun 08 16:54:01 ahh ... yeah .. thats it ! Jun 08 16:54:11 the pins are only rated for ~4mA I believe, really should just drive the gate of an NPN or something like that Jun 08 16:54:21 lol, base that is Jun 08 16:54:52 <_av500_> use tubes... Jun 08 16:55:00 yeah .. i thought 20mA will be tolerable. Jun 08 16:55:11 but then read that 4mA - 6mA Jun 08 16:55:39 ZeekHuge:if you have parts, put in a 74xxx24x chip to buffer things Jun 08 16:56:15