**** BEGIN LOGGING AT Tue May 30 03:00:05 2017 May 30 16:00:25 jic23: hi my yesterday's problem consist of compatible to driver issues in old kernel in dts was "compatible = "linux,spidev";" and now should be "compatible = "spidev";" May 30 16:26:22 Well tracked down. May 30 16:26:58 Can you add a note to the page you got the DTS fragment from? May 30 16:27:25 http://elinux.org/BeagleBone_Black_Enable_SPIDEV May 30 16:28:40 jic23: Could you give me your email? May 30 16:29:48 I don't have permission to edit this page May 30 16:30:04 Sure jic23@kernel.org May 30 16:31:19 I will add your address to my progress reports May 30 16:33:26 Weird. I do have permission. Tested by adding a useless note about this. I wonder how I got permission? May 30 16:36:10 If you email me a suitable bit of text with references I will put it up later. Also we should chase down getting relevant permissions for you. May 30 16:36:40 hi ravikp7[m].... how is coding going? May 30 16:39:39 ravikp7[m]: fyi, I'm very happy with your intro video! May 30 16:40:29 jkridner|pd: I tested binary-parser npm package for binary parsing, which seemed to work good. But, I could not find a suitable serializer, all the ones that I found implemented their own protocol, which can't work in our case May 30 16:40:44 jkridner|pd: Thanks! May 30 16:41:12 jic23: weird is this that elinux page about spidev was edited 2 months ago May 30 16:41:15 ravikp7[m]: will you just do manual packetization? does more need to be written at the C level? May 30 16:41:45 ravikp7[m]: how did the serial cable acquisition work? May 30 16:42:13 jkridner|pd: I'm now looking to check older version of packet, if that doesn't work, wil surely go with manual May 30 16:44:50 all, fyi, http://bbb.io/gsoc has a playlist for all the intro videos. May 30 16:47:32 ravikp7[m]: serial cable? May 30 16:48:06 jkridner|pd: I could check all the commands running through serial. The SPL that I build, couldn't run. I didn't get enough time to debug it due to exams, only one left on 1st june. May 30 16:48:54 jkridner|pd: I want to give enough time to debug it first by myself then if I get any problems, will discuss it with you. May 30 16:57:41 jkridner: Should I make two repos for the code, one for the nodejs server and other for the complete tool ? May 30 17:14:37 ravikp7[m]: yeah, I think the pure node thing should probably be it's own thing that can be installed via npm. May 30 17:15:23 ravikp7[m]: but, it should specify how to build the SPL/u-boot if it doesn't do it itself. May 30 17:15:40 can just point to an overall project that uses the server. May 30 17:15:41 pmezydlo: editted to add a note about enabling at boot... Guess they were running an older kernel. May 30 17:17:00 jic23: thanks, This should help others May 30 17:17:42 m_w, jic23: my first progress report is ready May 30 17:17:53 Cool May 30 17:19:00 first day in work, I missed that whole year May 30 17:21:05 Interesting that it is listing uenv.txt as if it were in the root... May 30 17:22:05 Was that different for 4.4? May 30 17:23:00 pmezydlo: report looks fine to me. May 30 17:24:07 jkridner: Should I make a different branch for the nodejs server in the main repo and push code initially to it ? May 30 17:25:24 ravikp7[m]: no, just create a dependency in the main repo for the nodejs server using package.json. use 'npm publish' to publish the server. May 30 17:26:04 jic23: 4.12 is prepared by me, for the beginning, I compiled kernel and add a few drivers May 30 17:26:22 ravikp7[m]: so, the server would be its own project. May 30 17:27:13 jkridner: So, add link to both repos to elinux wiki for review purpose? May 30 17:27:44 pmezydlo: just checked yesterday's paste bin. It was /boot/uenv.txt. I would guess you have two uenv.txt files in your image. May 30 17:29:31 yeah I know but this is correct, Instructions which I used during prepare custom kernel is here: https://eewiki.net/display/linuxonarm/BeagleBone+Black 4.12 kernel isn't properly patched. May 30 17:31:09 first uEnv you have to use If you don't want to clear out the old Bootloader in eMMC May 30 17:34:33 Hmm. That's a horrible dance. So issue is that it isn't picking up the other file. May 30 17:35:19 Uboot is old enough to need that? May 30 17:36:59 I'm no sure but is the same uEnv file in my both images (4.4 and 4.12) May 30 17:39:36 But your original dump didn't do the dance... May 30 17:40:04 Try removing the extra uenv.txt and see what happens? May 30 17:42:42 Actually original might have done. Dropping characters near the start... May 30 17:42:57 uuuu very interesting May 30 17:44:22 jic23: here is ftdi output May 30 17:44:22 https://pastebin.com/W5ixYJKu May 30 17:44:55 oh here is wrong dtb May 30 17:44:59 take a minut May 30 17:49:37 jic23: it works well May 30 17:50:34 ok spi works in 4.12 now I will try with ice40-mgr May 30 17:54:32 Cool! May 30 17:57:08 jic23: when I loaded ice40-mgr something broke May 30 17:57:16 https://pastebin.com/VQ6ysBiR May 30 18:09:05 in my opinion DTS isn't correct, May 30 18:15:41 jkridner: did you have a look at the gist that I shared ? May 30 18:17:22 ravikp7[m]: where? May 30 18:17:43 jkridner: shared here on irc May 30 18:17:44 https://gist.github.com/ravikp7/37e954e2975de5b1c0ed220b7add7490 May 30 18:17:59 https://gist.github.com/ravikp7/6ed9581124ec3c6abdbb2847ede20c08 May 30 18:18:17 used this npm package https://www.npmjs.com/package/binary-parser May 30 18:19:45 it works good for parsing May 30 18:20:04 For serialization, I've settled on this https://www.npmjs.com/package/schemapack May 30 18:20:54 ravikp7[m]: feel good about it then? May 30 18:21:14 But there's a catch, it inserts array size in the serialization when array is used which is not required, I'll remove it manually. May 30 18:21:41 jkridner: Yeah, pretty well May 30 18:31:55 Like for an array [1, 2, 3] it gives <03 01 02 03> instead of <01 02 03> as the array size is not defineable in the packet definition for this serializer May 30 18:36:48 ravikp7[m]: looks pretty good to me. May 30 18:37:24 ravikp7[m]: do you have all OS variants for testing? will you be able to enlist many testers to get different OS variants early in the process? May 30 18:38:59 jkridner: I can test it for Windows and Linux. Not sure about OSX May 30 18:39:57 ravikp7[m]: k. I can try to test that frequently, but good if you can push little tests out to the mailing list frequently to try to encourage people to test the basics. you might specifically reach out to folks on the resin.io gitter as well. May 30 18:40:37 jkridner: surely May 30 18:47:25 jkridner: I'll be pushing code to this repo https://github.com/ravikp7/node-beagle-boot for the server, adding it to elinux wiki page May 30 18:49:23 ravikp7[m]: the resin.io folks seem interested in supporting, so please engage them on gitter.im. May 30 18:49:48 ravikp7[m]: make sure to use an open LICENSE. May 30 18:50:00 MIT should be good. May 30 18:50:32 jkridner: Yeah, I've had chat with them earlier, they are very helpful :) May 30 18:50:53 Yeah, I'll use MIT May 31 00:50:47 hi nerdboy: May 31 00:51:06 yo May 31 00:52:01 did you saw the pin diagram for epwm and ecap on git wiki May 31 00:53:22 I am building dto, so should I assign all required pin as a device cape, or is there any other method May 31 00:53:56 like on this page https://github.com/beagleboard/devicetree-source/tree/master/arch/arm/boot/dts May 31 00:54:35 and I have still not received bbb... May 31 00:58:36 and as in technical reference manual for am335x on PAGE 2324 these figures are provided May 31 00:58:59 * thetransformerr[ uploaded an image: Screen Shot 2017-05-31 at 6.27.24 AM.png (174KB) May 31 00:59:04 * thetransformerr[ uploaded an image: Screen Shot 2017-05-31 at 6.27.46 AM.png (228KB) May 31 01:01:01 in 15.1, they have shown that we can control it using PRUSS May 31 01:01:57 and in fig 15.2 they have used sync_in pins, which pin should go here?? means if are doing with pru, should we use some clock generated by pru?? **** ENDING LOGGING AT Wed May 31 03:00:02 2017