**** BEGIN LOGGING AT Sat May 10 03:00:00 2014
May 10 13:21:56 <karki> Abhishek_ : what name have you given to your project?
May 10 13:22:22 <Abhishek_> BeagleLogic
May 10 13:22:47 <Abhishek_> karki: did you just install CLPRU separately or as a part of the CCS?
May 10 13:26:37 <karki> separately
May 10 13:26:58 <karki> Abhishek_ : can you think of a good name I could keep for my project?
May 10 13:34:44 <Abhishek_> Is there a link for downloading CLPRU sans CCS?
May 10 13:37:17 <karki> ask jkridner for the link. there seems to be a new one going about town
May 10 13:38:05 <karki> sid_ : ping
May 10 13:38:17 <Abhishek_> I asked him, he said to download via CCS, but I can't find only CLPRU it seems, I've mailed him again, let's see
May 10 13:40:10 <karki> PRUSpeak, how does it sound?
May 10 13:40:29 <Abhishek_> interesting, I too thought of that
May 10 13:41:12 <karki> PRUFirmata was another one I had
May 10 13:42:19 <karki> Abhishek_ : sid_ is working with the clpru, on mranostay 's and panto 's code. you should check with him!
May 10 13:46:59 <Abhishek_> hmm, I guess I'm downloading CCS anyway
May 10 13:48:09 <karki> what is CSS normally used for (other than debugging and stuff)
May 10 13:48:32 <karki> I personally don't like IDEs
May 10 13:48:32 <Abhishek_> It's an Eclipse based IDE
May 10 13:49:50 <karki> Can't you cover the functionality which CCS provides, with eclipse plugins?
May 10 14:42:33 * Abhishek_ just installed the CLPRU compiler *sans* CCS
May 10 15:00:13 <sid_> karki: pong
May 10 15:02:16 <Abhishek_> sid_: does your PRU application require vrings?
May 10 15:02:31 <sid_> nope
May 10 15:02:48 <sid_> as of now, can't say abt future
May 10 15:03:02 <Abhishek_> are you using CCS?
May 10 15:03:28 <sid_> no, i haven't tried CCS with pru yet
May 10 15:03:54 <Abhishek_> which CLPRU version do you have?
May 10 15:04:42 <sid_> i'm compiling using 1.0.0B1, i've tried 2.0.0B1 for blinking some LEDs but i'm not able to make panto's and mranostay's code compatible with it
May 10 15:04:55 <Abhishek_> oh
May 10 15:04:57 <sid_> too much changed between these two versions
May 10 15:05:47 <Abhishek_> I just installed 2.0.0B2
May 10 15:06:04 <sid_> it comes along with CCS
May 10 15:06:19 <sid_> or jkridner gave it to you
May 10 15:06:30 <sid_> *came
May 10 15:06:39 <Abhishek_> yep, I somehow managed to get it without installing CCS
May 10 15:07:33 <sid_> can you place its README on pastebin
May 10 15:10:02 <Abhishek_> hey the readme still reads 2.0B1
May 10 15:10:06 <Abhishek_> Feb 2014
May 10 15:10:13 <Abhishek_> *Feb 2013
May 10 15:10:48 <sid_> haha
May 10 15:11:13 <sid_> let me check it out, place it  on pastebin
May 10 15:12:39 <Abhishek_> https://gist.github.com/abhishek-kakkar/9b5f6bc58f1d0c86b7cb
May 10 15:13:55 <sid_> haha, its exactly same as 2.0.0B1
May 10 15:14:06 <sid_> README
May 10 15:14:50 <Abhishek_> so, what's the problem that you get with panto's or mranostay's code?
May 10 15:14:53 <sid_> is there any documentation for the PRU compiler?
May 10 15:15:39 <sid_> the Constant Table Registers
May 10 15:17:10 <sid_> it's access is straightforward extern cregister void *C0; in 1.0.0B1
May 10 15:17:50 <sid_> but not that straightforward in newer version check out the Constant Table Registers part inside the README
May 10 15:19:10 <sid_> I got little bit what they are trying to convey and got some LEDs blink and nothing more with newer compiler
May 10 15:20:16 <sid_> check this: https://github.com/BeaglePilot/PRUSS-C/blob/master/PRUSS_LIB/example/blinkled.c
May 10 15:22:11 <Abhishek_> yes, I found the CTR part. So that breaks compilation of those demos, correct?]
May 10 15:22:21 <sid_> yep
May 10 15:34:05 <Abhishek_> prudefs.h would be the source of the error, isn't it?
May 10 15:35:36 <sid_> yes
May 10 15:37:52 <sid_> all you need to do is declare mem portions in lnk file, use attribute method inside the pru_defs.h to access the Cregisters and finally change the offsets (the part where i'm stuck)
May 10 15:39:12 <Abhishek_> which dev platform are you on?
May 10 15:39:35 <sid_> e.g. if you see my example code i use (*(&C4+0x01)) to read SYSCFG while in panto's code its done using (*(volatile u32 *)((char *)C4 + (0x04)))
May 10 15:40:14 <sid_> on beaglebone its debian and linux mint on pc
May 10 15:40:32 <Abhishek_> where is CLPRU installed?
May 10 15:41:06 <sid_> on pc or bbb
May 10 15:41:12 <Abhishek_> pc
May 10 15:42:08 <sid_> its your choice the installer asks you on my pc its in /home/sid/ti/TI_CGT_PRU_1.0.0B1/bin
May 10 15:42:37 <Abhishek_> hmm, did you install it as root?
May 10 15:42:57 <Abhishek_> mine doesn't seem to find its include files.
May 10 15:42:58 <sid_> i don't remember it was a long time ago :)
May 10 15:43:03 <sid_> ahh
May 10 15:43:05 <sid_> simple
May 10 15:43:25 <sid_> PRU_C_DIR="/path/to/prulib"
May 10 15:43:37 <sid_> PRU_C_DIR="/path/to/prucomp/lib"
May 10 15:43:50 <sid_> export this
May 10 15:44:14 <sid_> or include this inside your .bash
May 10 15:49:41 <Abhishek_> yep, got it
May 10 15:57:32 <karki> Abhishek_ : I thought you were not working with the CLPRU
May 10 16:01:00 <Abhishek_> I'm evaluating CLPRU, though
May 10 16:03:55 <Abhishek_> Just started off
May 10 16:06:22 <karki> sid_ : the code of yours in github.... after compiling, how did you get it on the PRU?
May 10 16:06:34 <Abhishek_> it goes using the device tree
May 10 16:07:12 <sid_> it can go both ways uio and rproc
May 10 16:07:32 <Abhishek_> sid_: Using rproc, you use the device tree, correct?
May 10 16:07:38 <sid_> yeah
May 10 16:09:25 <karki> but you would need a driver for that......
May 10 16:09:34 <karki> rproc
May 10 16:09:37 <karki> I mean
May 10 16:09:48 <sid_> the driver is already there in 3.8 kernel
May 10 16:10:10 <karki> src?
May 10 16:10:30 <sid_> of the driver
May 10 16:10:34 <karki> yes
May 10 16:11:38 <sid_> git /beagleboard/linux/drivers/rproc/pru_rproc.c
May 10 16:11:43 <sid_> something like that
May 10 16:12:56 <sid_> its written by panto
May 10 16:13:05 <karki> thats for his specific firmware
May 10 16:13:19 <karki> the multi channel PRU one
May 10 16:13:41 <karki> yeah, but it would load any piece of code
May 10 16:13:58 <sid_> hehe, if you want your firmware on the PRU you just chnge the name of the firmware in the device tree
May 10 16:14:15 <sid_> or simply change the name of your binary
May 10 16:14:22 <sid_> to testpru0
May 10 16:14:28 <sid_> or testpru1
May 10 16:14:51 <karki> yeah, I know that :p (or rather realized! that it will remain same for any exec)
May 10 16:15:32 <karki> sid_ : what plans for summer?
May 10 16:15:40 <sid_> beaglepilot
May 10 16:16:40 <karki> which college are you in?
May 10 16:17:01 <sid_> Nirma University
May 10 16:17:32 <karki> Gujrat, right?
May 10 16:17:40 <sid_> yeah
May 10 16:17:44 <karki> exams done?
May 10 16:17:51 <sid_> yep
May 10 16:18:34 <karki> Ah! free bird ;) so going into which year now?
May 10 16:18:59 <sid_> college is over for me
May 10 16:19:04 <karki> :D
May 10 16:19:32 <karki> nice :)
May 10 16:36:08 <karki> sid__ : which DTO did you use in K 3.8?
May 10 16:36:25 <karki> for the remote proc....
May 10 16:36:27 <sid__> BB-PRU-04
May 10 16:44:25 <karki> sid__ : Thanks!
May 10 16:44:31 <sid__> np
May 10 16:46:54 <karki> I had a few things to discuss regarding DTO's and remote proc. You seem to have done your homework ;) So if you don't mind I'll bug you tomorrow. (I'm too busy with my exams to take my own sweet time for this! So I'll need help! )
May 10 16:51:12 <sid__> ok
**** ENDING LOGGING AT Sun May 11 03:00:00 2014