**** BEGIN LOGGING AT Tue Jun 28 02:59:58 2016 Jun 28 04:43:28 oh ! Abhishek_ !!! Jun 28 04:43:32 Thank you :) Jun 28 04:44:16 I am really glad that I got your feedback. Jun 28 04:44:26 really ! Thank you :) Jun 28 04:47:05 And anyone used paypal can please tell we what details do I need to send to jkridner ? Jun 28 04:47:24 Wormo: ^ Jun 28 04:47:41 alexhiam: ds2 ^ Jun 28 04:48:18 Hm I did paypal once, the other person had a Paypal account already and I think I just sent via the associated email address Jun 28 04:48:49 maybe you still need to make the account Jun 28 04:49:00 I have made one . Jun 28 04:49:52 so I just need to send the email addr. thats associated with my paypal acc ? Jun 28 04:50:10 I think that's right Jun 28 04:50:13 ZeekHuge: just your email Jun 28 04:50:22 okay. Thank you Jun 28 04:50:43 ZeekHuge: if you have a PP account, use that email. otherwise, you should get an invite to create an account Jun 28 04:50:50 ZeekHuge: is the board in your hands? Jun 28 04:52:40 ds2: Yes . It has already been delivered and is at my relative's place. I will get it on Wednesday. Jun 28 04:52:58 finally an end to that shipping saga :/ Jun 28 04:53:19 indeed Jun 28 04:55:02 yeah. Jun 28 04:59:07 Visaoni: what's your current task? Jun 28 05:01:59 Wormo: getting rpmsg stuff up Jun 28 05:03:08 Flowing fake data to userspace? Jun 28 05:03:43 that's the goal Jun 28 05:04:23 What's the delta between now and the goal :) Jun 28 05:08:25 about... 399 bytes and loop I guess? should be done with it tonight Jun 28 05:08:57 Close, ok Jun 28 05:10:42 * nerdboy assembling bpi m3 Jun 28 05:11:08 new router? Jun 28 05:12:05 no, that's bpi r1 Jun 28 05:12:17 m3 needs the device tree Jun 28 05:12:45 but i do have the r1 antennas finally Jun 28 05:20:45 [A Jun 28 05:20:51 oopsie Jun 28 05:22:22 * nerdboy upgrades Guest57699 to a pdp11 Jun 28 05:23:05 hehe :) Jun 28 05:28:24 @%@$#!#@!#!@#!@#!@#@!$#@$@#$@#$!#@!#@! ethernet driver is buggy Jun 28 05:28:32 no phy and it likes to oops :( Jun 28 05:29:16 what board is this, bringup of new board? Jun 28 05:30:16 *nod* Jun 28 05:32:26 * nerdboy thought for a sec it was the pdp11 upgrade... Jun 28 05:39:01 bringup can be rather challenging, detangling the bugs in new hardware from driver bugs Jun 28 05:40:37 (and software is always guilty until proven innocent, because nobody likes having to respin) Jun 28 05:53:33 m_w: Hi .. yeah, using clpru Jun 28 06:00:31 there has to be a way to do it with clpru Jun 28 06:05:26 the point is we need to place the structure at the exact location it should be, at the same time, allowing rproc drivers to understand that okay this is the the resource table. only then it will load Jun 28 06:05:34 yes there is ofc Jun 28 06:05:54 http://git.ti.com/pru-software-support-package/pru-software-support-package/blobs/master/examples/am335x/PRU_gpioToggle/AM335x_PRU.cmd#line85 Jun 28 06:06:08 the section where resource table need to be placed ^ Jun 28 06:06:15 http://git.ti.com/pru-software-support-package/pru-software-support-package/blobs/master/examples/am335x/PRU_gpioToggle/resource_table_empty.h#line62 Jun 28 06:06:26 the pragma directive that place it there ^ Jun 28 06:06:42 yeah that is in C form Jun 28 06:06:54 I am talking about a way to do it in ASM form Jun 28 06:07:37 i thought you had a dummy data example? Jun 28 06:08:52 yeah so just specify it like .resource_table:my_resource _table Jun 28 06:09:17 and then use it the way gcc example used. Jun 28 06:09:34 I just figured out that now. Jun 28 06:09:45 ahh .. while discussing it with you :) Jun 28 06:09:50 awesome Jun 28 06:10:29 though will try that later, for now will go with declaring it in C way. Jun 28 06:10:38 and then linking the two later. Jun 28 06:11:19 whatever works for you Jun 28 06:11:36 not sure that it matters which way you do it Jun 28 06:17:13 nah.. it depends on which angle you are working Jun 28 06:17:19 helps to be proto hw ;) Jun 28 06:18:09 ZeekHuge: did the current driver drop the elf support? Jun 28 06:18:18 IIRC - it used an ELF symbol Jun 28 06:18:23 nope. Jun 28 06:18:34 It supports only ELF format. Jun 28 06:18:51 yeah so ELF means in the form of blocks right ? Jun 28 06:19:24 and we can map each block to a memory area ? Jun 28 06:19:47 and thats what the .cmd linker file does. Jun 28 06:19:51 isnt it ? Jun 28 06:19:53 ds2: ^ Jun 28 06:20:59 https://en.wikipedia.org/wiki/Executable_and_Linkable_Format Jun 28 06:20:59 [WIKIPEDIA] Executable and Linkable Format | "In computing, the Executable and Linkable Format (ELF, formerly called Extensible Linking Format) is a common standard file format for executables, object code, shared libraries, and core dumps. First published in the System V Release 4 (SVR4) Application Binary Interface (ABI) specification, and later..." Jun 28 06:22:28 yeah . already read that. and that is what I understood out of that. is it correct ? Jun 28 06:25:02 Wormo: how to enable auto suggest in vim ? Jun 28 06:25:33 I searched web, but it seemed to be a bit complicated, so just didnt go into that. Jun 28 06:29:30 Do you mean ctrl-N while in insert mode? Jun 28 06:29:56 Type a couple characters, hit ctrl-N to get possible completions Jun 28 06:32:01 http://vimawesome.com/plugin/youcompleteme Jun 28 06:34:02 might be a little annoying and not sure that it will work for something like the linux kernel Jun 28 06:35:06 Wormo: wow ! i didnt see that option anywhere on the web ! Jun 28 06:35:45 or .. probably didnt search well. Jun 28 06:36:33 I use the vimgitgutter Jun 28 06:36:37 http://vimawesome.com/plugin/vim-gitgutter Jun 28 06:38:07 and airline to make it look cool Jun 28 06:38:15 that is about it Jun 28 06:38:33 that looks pretty nice Jun 28 06:38:34 oh and ctrlp Jun 28 06:38:43 http://vimawesome.com/plugin/vim-airline Jun 28 06:38:50 http://vimawesome.com/plugin/ctrlp-vim-red Jun 28 06:39:01 ZeekHuge: you know about vimdiff yet? Jun 28 06:39:18 that one is also builtin, don't need extra plugin Jun 28 06:41:42 Wormo: nope. So its something like diff ? Jun 28 06:42:08 m_w: so is that thing ^^ about the ELF format correct ? Jun 28 06:42:12 it's multi-file merging technique Jun 28 06:43:07 say you have 2 versions that need manually merged because you only want certain changes Jun 28 06:43:29 can help compare versions when you get merge conflicts Jun 28 06:43:32 that sort of thing Jun 28 06:44:29 oh .. okay. Jun 28 06:44:37 ZeekHuge: sort of Jun 28 06:44:53 ZeekHuge: ELF defines the binary format Jun 28 06:46:28 ZeekHuge: the table is just another section Jun 28 06:53:27 one that is specifically needed for remoteproc Jun 28 06:57:13 qcom_mdt_find_rsc_table() - provide dummy resource table for remoteproc Jun 28 06:57:29 maybe that's another way to do it from the c side Jun 28 06:57:52 https://patchwork.kernel.org/patch/8681931/ qcom loader patch Jun 28 06:59:01 ZeekHuge: no, ELF means symbols Jun 28 06:59:15 you scared him away Jun 28 06:59:21 blah Jun 28 07:08:23 https://e2e.ti.com/support/embedded/linux/f/354/t/274182 <= rproc memory tips in the summary aat the end Jun 28 07:09:26 this too => "resource table needed to be defined as const in order to get an elf section that remoteproc recognizes" Jun 28 07:10:30 although he's workign with da8xx dsps Jun 28 09:43:55 Wormo: there / Jun 28 09:43:56 ? Jun 28 12:08:07 Hi!! anyone who compiled kernel in the last 1 month present? Jun 28 12:21:25 I did Jun 28 12:22:18 kiran4399: ^ Jun 28 12:22:32 dont know will be able to help or not ! Jun 28 12:22:35 :P Jun 28 12:23:08 did you see an error like this: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Jun 28 12:23:08 ? Jun 28 12:23:12 ZeekHuge: ^^ Jun 28 12:23:44 kiran4399: i think you are not pointing to your cross_compiler Jun 28 12:24:00 or something wrong with the command Jun 28 12:24:10 kiran4399: It was in the travis-ci.. Jun 28 12:24:26 kiran4399: of the rcnee kernel repo.. Jun 28 12:24:45 kiran4399: link please ? Jun 28 12:25:00 https://travis-ci.org/beagleboard/linux/builds/140583230 Jun 28 12:27:40 I had that error many times, so quite sure its the cross compiler Jun 28 12:27:58 probably because they are using it from the apt Jun 28 12:28:13 better to download it from linaro website Jun 28 12:28:42 https://github.com/ZeekHuge/BeagleScope/blob/master/.travis.yml#L16 Jun 28 12:28:50 Zeekhuge: I used the version 5 cross compiler.. and it worked good for me.. Jun 28 12:29:13 Zeekhuge: I think the trvis.yml file should be updated.. Jun 28 12:29:39 kiran4399: the one at bb/linux right ? Jun 28 12:29:49 yeah.. Jun 28 12:31:14 sending a pull request. Jun 28 12:31:17 kiran4399: ^ Jun 28 12:31:27 will take a while though Jun 28 12:31:39 that would be right ? isnt it ? Jun 28 12:31:49 kiran4399: ^ Jun 28 12:32:00 yeah. Jun 28 12:38:42 kiran4399: should it be on 4.4 branch ? Jun 28 12:38:54 yeah. Jun 28 13:37:19 kiran4399: there ? Jun 28 13:37:27 yea, Jun 28 13:37:55 it was kind of stuck there at make command .. https://travis-ci.org/ZeekHuge/linux/builds/140801551 Jun 28 13:38:08 GEN just appeared Jun 28 13:38:27 is that system too slow ? Jun 28 13:38:35 or there is some error ? Jun 28 15:00:22 kiran4399: can you fix those compiler warnings in mpu9250? Jun 28 15:00:38 alexhiam: I forgot to tell you.. Jun 28 15:00:57 alexhiam: I got the mpu9250 working!!! :-D Jun 28 15:01:21 mag as well? Jun 28 15:01:22 alexhiam: using the jic23 patchset on the 4.4.12-r30 .. Jun 28 15:01:30 alexhiam: yeaaaaaaaaaaaaaaaaaaaaah!! Jun 28 15:01:33 awesome!! Jun 28 15:01:39 alexhiam: thanks to jic23.. Jun 28 15:01:53 alexhiam: now i see 3 entries.. divice0, device1, trigger0.. Jun 28 15:02:12 alexhiam: device0 is mpu6050. improved version(thanks to the backports) Jun 28 15:02:22 alexhiam: device1 is ak8975.. Jun 28 15:02:26 yipee.. Jun 28 15:02:48 that's great! and how's the data look? Jun 28 15:03:13 alexhiam: just like gyro.. Jun 28 15:03:44 alexhiam: in_magn_x_raw, in_magn_x_offset, in_magn_scale, in_magn_mountmatrix. Jun 28 15:03:44 are you sure your read_raw_data function is right? Jun 28 15:04:05 alexhiam: I don't think so.. I am getting a segfault :( Jun 28 15:04:16 ah. pastebin? Jun 28 15:05:52 oh, and you should also split bb_blue_api.h into separate header files Jun 28 15:07:04 alexhiam: I am getting a simple Segmentation Fault.. Jun 28 15:07:12 on what line? Jun 28 15:07:33 alexhiam: bb_blue_api.h into different header files also?? Jun 28 15:08:30 well, maybe not... I'd like the source to be a bit cleaner, but let me think on how to do that... Jun 28 17:41:30 Abhishek_: Wormo m_w ds2 : I am trying to work on the basic firmware and its assembly and involves looking at the docs again and again so, going on quite slow. And then, all the tasks I mentioned in the last report are .... :( Jun 28 17:46:42 by now, I have something that would have a varying sampling rate. I am trying to work with interrupts and communication btwn the prus. So, will basically pru0 will put 4bytes of data in shared ram and then interrupt pru1. first 16bits will tell the delay value ,next 1 byte will tell the width of the sample and the next byte will be start/stop bit + reserved Jun 28 17:48:05 and then PRU1 on getting interrupted will Load this data from the shared ram into his register and use from there. Jun 28 17:49:40 all this is quite similar to beaglelogic's fw, except the sampling thing. I am able to see what beaglelogic is doing but, to use its fw, i will have to understand exactly what the code is doing. Jun 28 17:50:09 which i think will be more difficult than writing for beaglescope. Jun 28 17:50:36 Abhishek_, Wormo, m_w , ds2 ^^ Jun 28 17:50:47 please some views on it. Jun 28 17:53:53 just keep at it Jun 28 17:54:21 if you find something that does not make sense ask for help Jun 28 18:41:45 okay. Jun 28 22:07:56 hey m_w Jun 28 22:08:01 There? Jun 28 22:08:03 mdp^^ Jun 28 22:08:15 I am "here" Jun 28 22:08:28 Hi m_w :P Jun 28 22:08:44 Just needed some help with cross compiling a driver Jun 28 22:10:10 what is wrong? Jun 28 22:10:29 m_w, Take a look here:https://github.com/chanakya-vc/PRU-I2C_SPI_master/commit/81cb4ebbd0df6fe7b02712be8fd4bd276f0e2ff1?diff=unified Jun 28 22:11:06 So I am trying make -C "path to compiler" M=$PWD Jun 28 22:11:11 m_w, ^^ Jun 28 22:11:21 It has a Kbuild file Jun 28 22:12:17 I think make -C "path to my file" should be the case, but then how do I pass the cross compilers path there? Jun 28 22:12:21 m_w, ^^ Jun 28 22:13:19 CROSS_COMPILE= Jun 28 22:13:32 either set the environment or use a make variable Jun 28 22:13:39 note, you will need to reference the kernel tree Jun 28 22:14:01 make ARCH=arm CROSS_COMPILE=arm-compiler-prefix -C "path to kernel source" M=$PWM Jun 28 22:14:43 just buuild it in the tree Jun 28 22:15:35 less pain Jun 28 22:17:22 just create a Makefile for your module Jun 28 22:19:05 there are plenty of examples Jun 28 22:19:36 I don't get the meaning of the kernel source? m_w it is the place from where the makefile picks up the headers right? so in my case it will be:/lib/modules/'uname-r/build'? Jun 28 22:20:25 ds2, I could do that too. But bradfa suggested to build an out of tree module. Jun 28 22:20:40 okay Jun 28 22:21:04 just want to point out... you got a lot to do and dealing with build issues may not be the best use of time Jun 28 22:21:19 Okay ds2. Got you. Jun 28 22:21:19 kernel source is the path of the kernel source tree that you want to compile against Jun 28 22:22:03 do you have the kernel source of the kernel you are using on the board? Jun 28 22:22:12 m_w, But if I am cross compiling, then the kernel source tree would be of beaglebone right? Jun 28 22:22:24 Hmmn I don't think so. Jun 28 22:22:52 well there is your first problem Jun 28 22:23:13 So how do I get that now?m_w Jun 28 22:23:47 first determine the kernel version that is on your target Jun 28 22:24:09 4.4.9 Jun 28 22:24:14 m_w, Jun 28 22:24:19 got it by uname -r Jun 28 22:24:23 on bbb Jun 28 22:24:24 uname -a Jun 28 22:26:49 Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux Jun 28 22:26:51 m_w, ^^ Jun 28 22:28:14 https://github.com/beagleboard/linux Jun 28 22:30:51 Okay so m_w , I basically download the one for 4.4.9 for arm and then compile it? Jun 28 22:31:02 yup Jun 28 22:31:08 And then give the path for the it? Jun 28 22:31:16 then point to that build directory Jun 28 22:31:25 Okay got you. Jun 28 22:31:28 https://sites.google.com/site/beagleboneblac/home/cross-compiling-linux-kernel-module Jun 28 22:31:54 ^^ here is a nice page that gives basic instructions Jun 28 22:32:02 m_w, One more thing I want to clarify, difference between in tree and out of the tree build? Jun 28 22:33:09 in tree means that the source for the driver you are building is in the kernel repository and usually upstream Jun 28 22:33:37 but out of tree means to is in a separate directory and is not upstream Jun 28 22:33:54 https://www.kernel.org/doc/Documentation/kbuild/modules.txt Jun 28 22:37:23 Okay so in tree, I would not have to worry about the path to the kernel source? Jun 28 22:37:26 m_w, ^^ Jun 28 22:38:44 But in that case too I think I would still have to have the kernel source of what is there on the BBB compiled on my host right? Jun 28 22:38:54 of course Jun 28 22:39:49 Okay so the only difference as far as makefile is concerned is regarding the path right? Jun 28 22:39:58 m_w, ^ Jun 28 22:43:07 the Makefile for an indriver is as simple as - Jun 28 22:43:15 obj-y := dumbdriver.o Jun 28 22:43:26 you can even hitchhike on another Makefile Jun 28 22:44:07 pretty much Jun 28 22:44:15 Okay ds2, but still need to have a the kernel source compiled right. I had not done it for BBB till now on my host so far. Jun 28 22:44:23 yes Jun 28 22:44:30 kernel building should be idiotically simple Jun 28 22:44:39 u are using a released kernel, right? Jun 28 22:44:46 if so, use RCN's build Jun 28 22:44:48 builder Jun 28 22:45:12 ds2 Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux Jun 28 22:45:28 I guess it is. I will look up RCN kernel builder Jun 28 22:46:25 Thanks for your help ds2 , m_w . Would be completely lost without you : ) Jun 28 22:48:42 chanakya_vc: it's the same wiki page for all of the bb kernels: https://eewiki.net/display/linuxonarm/BeagleBone+Black Jun 28 22:49:10 you are already using kernel from TI BSP section Jun 28 22:53:55 nerdboy, Okay the section above it talks about building the kernel on the host I guess? Jun 28 22:53:59 I could use that. Jun 28 22:54:47 ds2 Is this what you were talking about:https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Mainline Jun 28 22:55:54 you can build on the bb but it's a lot sloooooower... Jun 28 22:56:09 just set CROSS_COMPILE="" Jun 28 22:57:47 nerdboy, Okay in the link above I thought it is talking about cross compiling.So it is talking about building on the BBB right?in the Mainline section? Jun 28 22:59:42 no, it is talking about cross-compiling Jun 28 23:00:13 ^^ that is if you choose to build slow and native on beaglebone Jun 28 23:01:20 Okay got you.nerdboy, thanks. Jun 28 23:01:38 Seems to be pretty easy with this. Jun 28 23:02:19 i said you *can* build on beaglebone, not *should* Jun 28 23:04:16 Yes nerdboy . I got it . I got confused as to whether RCN's method was cross compiling or compiling natively. But it is clear now thanks. Jun 29 01:40:55 I hate cape manager **** ENDING LOGGING AT Wed Jun 29 02:59:58 2016