**** BEGIN LOGGING AT Mon Jun 20 02:59:59 2016 Jun 20 12:53:27 ZeekHuge: All going well? Jun 20 12:54:00 Not to worry if you are busy - I'm just eating lunch and bored ;) Jun 20 12:56:35 jic23: Hi ! ahh, struggling with PRU code Jun 20 12:56:37 and Jun 20 12:57:08 trying to understand the new ways that TI has introduced Jun 20 12:57:31 Sadly not an area I know anything much about... Jun 20 12:58:10 Out of curiosity has anyone done an effective bandwidth test on rpmesg? Jun 20 12:58:11 I have started to make posts about it, though I am slow at it (also, my father came here to meet me, and it was fathers day here yesterday, so was with him almost all the time ) Jun 20 12:58:39 Sure, was fathers day here yesterday too. Did my kind notice? Nope... Hmph. Jun 20 12:58:41 Ahh.. I was going to do that ... but Abhishek_ suggested me to use rpmsg anyway Jun 20 12:58:54 Definitely use it 'first'. Jun 20 12:59:11 and suggested that we would work to improve it later Jun 20 12:59:40 rpmsg as it would be the way with the standards Jun 20 12:59:46 If it doesn't work for bulk transfers then that is fine. However, we should figure standard ways of setting up bulk channels as this isn't exactly an unusual problem. Jun 20 13:00:13 rpmsg could be used as configuration interface for say dma configuration. Jun 20 13:01:24 Guess see how far you get with rpmsg first... Jun 20 13:02:26 okay so for, I should go with what is available, right Jun 20 13:02:27 ? Jun 20 13:02:42 *for now Jun 20 13:03:18 absolutely, but when you hit the boundaries the trick is how to move the boundaries in a way useful to you and everyone else hitting the same issue. Jun 20 13:03:19 jic23: zeekhuge.github.io Jun 20 13:03:58 https://zeekhuge.github.io Jun 20 13:05:02 have to add some more commands and comments section there .. Jun 20 13:06:14 so, instead of starting with rpmsg itself, I have started from basics, in the posts. this way, It will help to organize all that in my mind too .. Jun 20 13:06:24 was about to say the font was hideous then noticed something changed all my default fonts. Jun 20 13:06:26 :) Jun 20 13:06:35 So the whole internet is hideous today. Jun 20 13:06:58 Makes a lot of sense. Definitely a good way to clarify things in your mind. Jun 20 13:06:58 another browser ? Jun 20 13:07:45 And regarding your code review mail, I will first make the corrections and then reply back Jun 20 13:08:37 cool. Jun 20 13:08:54 Yeah, can't be bothered to figure what is wrong with fonts. Will probably clear up on a restart of the browser. Jun 20 13:10:03 I will soon add a comment section there, but if you find a mistake please let me know . Jun 20 13:11:01 oh ! and I had a question .. Jun 20 13:11:48 jic23: you asked me to use a better approach than using bools for locks. so I guess you were suggesting to use mutex right ? Jun 20 13:11:55 yup Jun 20 13:12:24 Cool ! will do that . but this PRU code first ... Jun 20 14:03:51 Hey bradfa there? Jun 20 14:03:59 mdp ^^ Jun 20 14:19:47 chanakya_vc: hi! Jun 20 14:20:09 chanakya_vc: ZeekHuge seems to also be wresling with rpmsg implementation, might be worth having you two discuss together some about what you're finding Jun 20 14:20:24 could be good resources for each other Jun 20 14:23:50 bradfa, I pushed some code for the driver.But it was based on a character device implementation.Right now I am following this:http://invo-tronics.com/spi-driver-for-linux-based-embedded-system/ Jun 20 14:25:14 bradfa, I will. At the moment I want to just get the basic framework of the SPI driver up.Get it to send data via spi_tansfer_message() Jun 20 14:25:23 chanakya_vc: ok Jun 20 14:29:18 chanakya_vc: I'm replying to your weekend email, again, I believe you are correct in your 2nd point. Jun 20 14:31:23 bradfa: hi, now I'm testing slave driver in pio mode. Maximum transmit length is 32 bytes; the driver has no limit for receiving. Jun 20 14:31:38 chanakya_vc: that link you just posted here, looks more like a tutorial on how to write a protocol driver Jun 20 14:31:51 pmezydlo: awesome! :) Jun 20 14:31:59 I think This is a good result Jun 20 14:32:00 pmezydlo: are you using the fifo inside mcspi? Jun 20 14:32:05 yeah Jun 20 14:32:23 pmezydlo: can you send a link to your current code? Jun 20 14:32:29 bradfa, Okay. As it is I have realized it is not making much sense to me :P Jun 20 14:32:33 the driver must load 32 bytes before transfer Jun 20 14:32:43 pmezydlo: for MISO? Jun 20 14:35:42 pls wait a few minutes, i'm uploading the code Jun 20 14:35:48 pmezydlo: no worries :) Jun 20 14:39:28 bradfa: https://github.com/pmezydlo/SPI_slave_driver_implementation Jun 20 14:40:16 pmezydlo: awesome! :) Jun 20 14:40:16 bradfa: My next goal is basic communiaction with user. After that DMA Jun 20 14:40:29 pmezydlo: sounds like you're making very good progress :) Jun 20 14:41:12 that's great work, I'm very glad. Jun 20 14:42:17 bradfa: I hope that, DMA solve the problem of the maximum transfer Jun 20 14:42:41 slave->master max 32 bytes Jun 20 14:43:24 pmezydlo: it will likely help, although you still need to have a reasonable thing to do if the master clocks more than you expect, PIO or DMA Jun 20 14:45:13 bradfa, Okay received your mail.I am clear on how the PRU will access the shared memory. Jun 20 14:45:58 bradfa: Thanks, I'm going back to work. Jun 20 14:45:58 chanakya_vc: the PRU can also reach DDR, if you wanted to have one PRU core read/write DDR and copy data betwen the 12kiB shared memory while the other PRU core does the bitbanging Jun 20 14:46:15 chanakya_vc: I'm not sure which is a better solution, performance wise, but just pick one to start with Jun 20 14:46:38 But what Abhishek_ pointed to me was the address over here:https://github.com/beagleboard/linux/blob/4.4/arch/arm/boot/dts/am33xx.dtsi#L946 Jun 20 14:46:42 bradfa, ^^ Jun 20 14:46:43 chanakya_vc: probably the way you are going, with linux writing into the 12 kib Shared memory will be less complicated Jun 20 14:47:35 bradfa, This is the address ARM would probably use to write to that shared mem. Jun 20 14:47:38 chanakya_vc: that's a good example from Abhishek_ Jun 20 14:48:09 Yes I think I get the whole idea about addresses I am going to be using. Jun 20 14:48:14 chanakya_vc: :) Jun 20 14:51:42 bradfa, Now I am currently stuck with the driver bit.I know that a struct spi_master() along with spi_transfer_one message has to be declared. Jun 20 14:52:24 chanakya_vc: if you take your char driver idea and just create a hack for now to make sure that your pru firmware does the right things, I think that'll be the easiest way to start Jun 20 14:52:47 chanakya_vc: then after you have that working, start trying to make a driver which is a spi master Jun 20 14:53:02 bradfa, Okay.So let me work on the char driver first. Jun 20 14:53:48 bradfa, There also I have a few doubts:Now I will have define a function that I will bind with .read in file operations structure right? Jun 20 14:54:04 To read data coming in from the userland? Jun 20 14:55:24 chanakya_vc: yes Jun 20 14:55:33 chanakya_vc: in lddv3 there should be a skull driver example, iirc Jun 20 14:55:50 chanakya_vc: it should give you a good overview of read/write interface for a char driver Jun 20 14:55:56 bradfa, Something of /dev driver given here:http://www.linuxdevcenter.com/pub/a/linux/2007/07/05/devhelloworld-a-simple-introduction-to-device-drivers-under-linux.html?page=2 Jun 20 14:56:36 http://www.linuxdevcenter.com/pub/a/linux/2007/07/05/devhelloworld-a-simple-introduction-to-device-drivers-under-linux.html?page=3 Jun 20 14:56:47 The next pg bradfa ^^ Something like this? Jun 20 14:58:00 chanakya_vc: like this https://lwn.net/images/pdf/LDD3/ch03.pdf Jun 20 14:58:13 * bradfa misspelled "scull" before, sorry Jun 20 15:01:58 bradfa, Okay let me go through this.Are you free today? Jun 20 15:03:33 chanakya_vc: I'll be around, yes Jun 20 15:03:58 Okay. I will read this and clear all my doubts. bradfa Jun 20 15:04:37 bradfa, I am sorry for my slow progress. But once I get done with SPI, I2C won't take so much time Jun 20 15:06:27 chanakya_vc: don't worry, your progress is not slow, this is not simple Jun 20 15:06:45 chanakya_vc: you are correct that i2c should go faster, though, you'll be able to reuse a ton of knowledge and code :) Jun 20 15:07:03 chanakya_vc: I'm learning a lot working along with you on this Jun 20 15:12:34 bradfa, : ) Jun 20 15:13:34 bradfa, I will get back to you after reading up on this.I am really motivated to finish this now : ) Thanks. Jun 20 16:05:10 Haha ! I got PRU1 -> PRU0 -> ARM communication ! Jun 20 16:05:47 ZeekHuge: excellent work Jun 20 16:06:54 :) Thank you. Well, there is just one part in the code, I am bit confused about .. so diving in more deep now / Jun 20 16:06:55 . Jun 20 16:08:31 and its using C, need to port PRU1 code to assembly. Jun 20 16:09:17 C not efficient enough? Jun 20 16:16:38 yeah, ds2 said that it should be in assembly, I was able to generate about 16MHz using C . But that was it, it was doing nothing else, so I think that it wont be efficient enough. Jun 20 16:22:31 ZeekHuge: is inline assembly possible to just drop into your inefficient C code sections? Jun 20 16:26:22 Yeah, I was thinking about that too. And I think that it will work. Jun 20 16:26:28 bradfa: ^ Jun 20 16:34:56 alexhiam: there? Jun 20 17:26:19 m_w: hi, Should char driver and slave driver be together in the same file, as one driver? Jun 20 17:28:05 pmezydlo: if the intent is making a framework, I would use a separate driver so that other processors can use it Jun 20 17:28:51 if you want a standalone driver then the same file is fine Jun 20 17:30:12 I think that standalone driver should be better. Jun 20 17:30:45 it would certainly be easier and we can look into restructuring for a framework later Jun 20 17:37:04 m_w:I will make framework standalone char driver and communication with slave driver. so it should be faster and easier Jun 20 17:40:58 okay Jun 20 17:43:40 hi kiran4399 Jun 20 17:47:24 alexhaim: so.. I am in the middle of completing the following stuff which I am ready to show in the mid-eval.. Jun 20 17:50:36 1. IMU, PWM, Baro, ADC APIs Jun 20 17:51:03 2. Full documentation on the readme.md on my github repo Jun 20 17:51:25 3. Patched MPU-9250 kernel driver Jun 20 17:54:10 4. Details of each kernel driver on the github wiki page. Jun 20 17:54:11 kiran4399: cool. what's the status of the drivers? do you have both sensors working? Jun 20 17:54:31 alexhiam: both sensors? Jun 20 17:54:40 imu and pressure Jun 20 17:55:04 or are you still having trouble with the bmp driver? Jun 20 17:55:19 alexhiam: yeah.. thanks to your hacks!! ;) Jun 20 17:55:45 yeah they are both working? Jun 20 17:56:29 alexhiam: btw.. for the APIs I tested the kernel driver for mpu6050.. it is working perfectly.. I am assuming that mpu9250 also would work.. Jun 20 17:56:37 alexhiam: though I did not test.. Jun 20 17:57:15 yeah, I think the only difference will be the extra directory for the mag Jun 20 17:57:38 did you make a note of the additional sysfs entries for mag?? What are they? Jun 20 17:57:42 alexhiam: ^^^ Jun 20 17:57:43 kiran4399: so you can get mpu9250.c switched over to using the sysfs entries then? Jun 20 17:57:56 no.. I thought you had patched the driver as well? Jun 20 17:57:58 alexhiam: yeah.. Jun 20 17:58:22 plus separate out the bmp280 stuff to its own file and do the same Jun 20 17:58:49 alexhiam: oh.. no not yet.. I patched the kernel and compiled it.. but I don't understand how to load it into the debian 8 image? Jun 20 17:59:12 https://gist.github.com/alexanderhiam/29fcf814f731dd94f8850961f1a61ae3 Jun 20 17:59:18 just build debs Jun 20 17:59:36 https://gist.github.com/alexanderhiam/29fcf814f731dd94f8850961f1a61ae3#file-beaglebone-kernel-dev-sh-L10-L17 Jun 20 18:03:25 alexhiam: directly install the deb file on the board? Jun 20 18:03:27 so easy?? Jun 20 18:03:31 yup Jun 20 18:19:50 hi amragaey... haven't seen any BBUI patches lately. what's going on? Jun 20 18:20:53 kiran4399: and I'd like to see the travis-ci build passing again. If you make sure it's all building every time you make a change it'll save you debugging time later on Jun 20 18:21:26 alexhiam: alright.. I'll do that.. Jun 20 18:21:45 alexhiam: anything else you want me to do? Jun 20 18:22:58 kiran4399: it would be ideal if you were also writing unit tests for each component of the APIs as you work on them Jun 20 18:24:17 alexhiam: yeah.. I wanted to ask you.. since I am building the apis differently.. should I make the unit tests? Jun 20 18:24:24 hi jkridner, yes I haven't pushed anything yet Jun 20 18:25:12 kiran4399: well anything that they have test scripts for can be adapted, which should hopefully just be a matter of changing the include Jun 20 18:25:41 alexhiam: I am sorry.. I did'nt get that.. Jun 20 18:25:50 I'm went this week on Events, trying to get how it works, and I understood it.. currently I'm working in the events and UI for the action after dragging buttons into graph Jun 20 18:26:01 I went* Jun 20 18:27:20 I'll try to get some output and push today, jkridner Jun 20 18:33:42 jkridner av500 _av500_ : what should I do about the ADC EVM thing ? Jun 20 18:35:37 h Jun 20 18:43:34 kiran4399: I just mean if there's already strawson test programs you should be able to use them, since the APIs aren't changing, just how they're implemented Jun 20 18:45:39 jkridner, isn't 192.168.7.2:3000 the url of bb c9 ? Jun 20 18:46:44 (window.location.host) gives the localhost ip 127.0.0.1 Jun 20 18:48:26 jkridner, can you give example for another socket connection url ? Jun 20 19:04:51 nerdboy: you didn't hear back from visaoni yet did you? Jun 20 19:09:10 nope Jun 20 19:16:18 bradfa, mdp I am writing the code now for the driver(have understood the ch bradfa told me read). Should be done by tomorrow. Jun 20 19:17:13 bradfa, Will push the code by tomorrow evening. Jun 20 19:21:26 ZeekHuge: aren't they going to collect the taxes from you when they deliver the package to you? Jun 20 19:22:37 Abhishek_: Yes, that is what I said in the first mail. Jun 20 19:22:46 Then? Jun 20 19:23:09 but, I will still need the invoice details to get fill in form 50 Jun 20 19:23:47 Did you speak to a customer care representative yet? Jun 20 19:24:26 3 times ... to get the status ... Jun 20 19:24:58 Call the Mumbai FedEx office where the shipment is held. Jun 20 19:25:13 Customer care offices can only do so much. You need to escalate. Jun 20 19:32:15 Abhishek_: Does he need to escalate? Sounded like he just needs some info from jkridner to complete the form, and then all will be well Jun 20 19:33:32 Wormo: usually in India, shipments for individuals may not require as much processing a commercial shipment to a company Jun 20 19:33:41 *as a commercial Jun 20 19:34:55 Abhishek_: okay, I will try that tomorrow morning as the number seems to be busy. Jun 20 19:36:28 Call them during regular office hours, probably 9-5 Jun 20 19:42:54 9-9 as stated on their website. Yeah, I was just trying now ... was not expecting that they will attend the call. Jun 20 19:44:01 Well good that you know something about it Abhishek_, all I know is that customs can cause long delays Jun 20 19:46:53 <_av500_> jkridner: ping Jun 20 19:47:31 chanakya_vc: ok, sounds good! :) Jun 20 20:12:58 I don't think it's even customs that's causing the delay (they will collect it on delivery), it's just some state Sales Tax formalities. Jun 20 20:16:05 hmmmm Jun 20 20:19:37 _av500_: pong Jun 20 20:21:10 jkridner: it was about ZeekHuge's form, what to put on it, see email Jun 20 20:21:19 [jadonk] k Jun 20 20:25:58 I didnt understand the point that pru code needs a different compiler ... are they talking about clpru ? and clpru not being a gcc compiler ? Jun 20 20:26:04 https://groups.google.com/forum/#!topic/beagleboard/cYHCN3GWw_E Jun 20 20:40:44 ZeekHuge: yes **** ENDING LOGGING AT Tue Jun 21 02:59:58 2016