**** BEGIN LOGGING AT Thu Jul 10 02:59:58 2014 Jul 10 03:17:13 alexanderhiam : I was thinking it would make sense to the keep original 'IF (a b ) GOTO c' syntax of the IF statement. (anyway I use only 48 bits in a 64 bit inst, so the goto can be added and the size still remains 64 bit) Jul 10 03:18:27 are you sure it all fits? remember both a and b could be elements in an array Jul 10 03:25:27 anujdeshpande: did you get the output working? Jul 10 03:25:51 Abhishek_: dozed off last night. working on it now :) Jul 10 03:30:49 alexanderhiam : yeah. all of them fit! I have 8 bytes. one for opcode, one for various cases (i.e.) 'a' may be an array, or 'b' or 'c' or all three. then 6 bytes for (arr, index) for a, b, c if all three happen to be arrays! Jul 10 03:31:08 fits in perfectly! Jul 10 03:32:38 nice Jul 10 13:27:48 * karki_ likes the nick EatSleepCode :') Jul 10 13:28:39 if it were me it would be CodeEatSleep (assuming position counts ;) ) Jul 10 13:29:57 karki_: sleep is for the weak Jul 10 13:30:41 48 hrs was my longest non sleep coding period :/ Jul 10 13:30:50 karki_: sounds like hackathon style Jul 10 13:30:55 yeah Jul 10 13:31:01 was it hackathon ? Jul 10 13:31:08 one tablets at the end of the day :D Jul 10 13:31:13 *end of 2 days Jul 10 13:31:26 ;) Jul 10 13:31:39 yeah, hackathon! Jul 10 13:32:05 i did at angelhack barcelona 24h hacking on beer power :) Jul 10 13:33:17 :) registration for angelhack was costly in b'lore :'( Jul 10 13:33:55 i dunno how much i paid, 20 euros i think or so Jul 10 13:33:57 really low here Jul 10 13:35:28 * vvu really does not like to write documentation :( Jul 10 13:35:39 * karki_ knows that feel Jul 10 13:36:09 writing documentation is bad but writing documentation in M$ W0rd is super bad :) Jul 10 13:36:41 but frankly vvu, the code I'm writing is so convoluted, I'd prefer documentation! Jul 10 13:36:49 *writing now Jul 10 13:37:58 mhmhm Jul 10 16:50:23 alexanderhiam, are you meeting on skype or hangout? Jul 10 16:50:48 oh it's that time isn't it... let's do skype Jul 10 16:51:09 ok, logging in now.thx! Jul 10 16:52:17 hi Abhishek_, you around? Jul 10 16:59:52 Hi jkridner Jul 10 17:00:00 trying to run BeagleLogic now. Jul 10 17:00:12 got the firmware, devicetree and kernel module loaded. Jul 10 17:00:44 built the test app using: gcc -o beaglelogic beaglelogic.c beaglelogictestapp.c -lm -lrt Jul 10 17:00:49 ./beaglelogic gives me... Jul 10 17:00:56 jkridner: modinfo beaglelogic gives you? Jul 10 17:01:04 BeagleLogic open failed! Jul 10 17:01:57 http://pastebin.com/jxBL3JrH Jul 10 17:02:34 jkridner: https://github.com/abhishek-kakkar/BeagleLogic/wiki/Getting-Started Jul 10 17:03:47 k, allocated memory Jul 10 17:04:04 do I need to run the test app? Jul 10 17:04:33 Yeah, it should give a speed close to the sample rate Jul 10 17:05:25 For doing a capture, instructions are in the wiki Jul 10 17:05:37 I just see the 'dd' example. Jul 10 17:05:59 The sigrok sections have to be added Jul 10 17:06:00 ls -al Jul 10 17:06:05 wrong window. :-) Jul 10 17:06:47 will the pins float high by default? Jul 10 17:07:02 I seem to have a 34MB array of the value '3c'. Jul 10 17:07:36 That's expected, there are pullups and pulldowns on the boot pins Jul 10 17:07:53 On the BBW, it's 0x17 Jul 10 17:08:09 k. by default is it one byte per capture? Jul 10 17:08:15 Yes Jul 10 17:08:21 if so, I can do a lot with just 'hexdump' :) Jul 10 17:08:27 cool. Jul 10 17:08:37 * jkridner will start to have fun. Jul 10 17:08:46 That's how I designed it :) Jul 10 17:08:48 not sure if I want to spend time on sigrok right now. Jul 10 17:09:09 You can see sysfs attrs page too on the wiki Jul 10 17:09:29 does adding the beaglelogic driver to sigrok require rebuilding all of sigrok or can I just build a module and use sigrok from the Debian repos? Jul 10 17:09:49 jkridner: sigrok needs everything compiled in Jul 10 17:09:55 :( Jul 10 17:10:26 If you want, you can pull from gh and compile it on the BBB Jul 10 17:11:07 Lemme check if my dev branch is in sync with my local version Jul 10 17:15:58 jkridner: https://github.com/abhishek-kakkar/libsigrok/commits/beaglelogic-dev Jul 10 17:44:35 jkridner: How would you rate your experience of compiling and running BeagleLogic on a scale of 1(cumbersome) to 5(easily followed) ? Jul 10 17:44:50 4 Jul 10 17:44:54 well... Jul 10 17:45:00 at least for this phase of development... Jul 10 17:45:08 it needs to be much simpler.... Jul 10 17:45:28 but that depends on getting it pushed up and making some improvements to the default .dtb. Jul 10 17:46:36 there should be a 'beaglelogic' shell script to manage enabling/disabling/etc. (including the allocation and pin-muxing stuff) Jul 10 17:46:43 config-pin is a reasonable template. Jul 10 17:47:09 but I really liked it so far. Jul 10 17:48:12 Yup, and also to start the node frontend as well (I saw the bone101 and cloud9 scripts in systemctl...) Jul 10 17:49:57 jkridner: Is it possible to check the HDMI port and autodisable the HDMI cape if no monitor is connected at boot time, or maybe monitor a GPIO? Jul 10 17:50:50 I plan to try a run-time software disable through the same mechanism as config-pin.... Jul 10 17:50:59 let the LCD controller run, but switch the pin muxes... Jul 10 17:51:07 no reason the LCD controller should even need to know... Jul 10 17:51:26 monitor detection could be used to trigger the enable such that it comes up disabled by default. Jul 10 17:51:46 if you have spare time, I'd encourage you to try it. Jul 10 17:52:13 I started to work on it and posted a pastebin to linux-omap... at least I think that is where I posted it... might have been the beagleboard google group. Jul 10 18:35:09 Abhishek_: you around ? Jul 10 18:37:10 Almost :) Jul 10 18:38:32 Abhishek_: quick question then:) i have to absolutely make no changes when i add 2 pins to and existing overlay right ? considering the fact that all other pins are output pins, and these 2 pins are inputs Jul 10 18:38:56 I mean, do i have to make any changes in the pru configration fragment Jul 10 18:40:27 You just have to touch the pimux fragment then. PRU fragment is not to be touched for pinmux purposes Jul 10 18:40:56 Abhishek_: https://github.com/BeaglePilot/ardupilot/commit/293410ba37e7ba4cc6af224ef27d9522967c7b0b this should work right ? Jul 10 18:41:06 in that case Jul 10 18:42:39 Seems fine to me Jul 10 18:43:23 You might try and whip up a quick-and-dirty firmware to see if the configs are correctly Jul 10 18:43:35 *correct Jul 10 18:43:50 Error: BB-BONE-PRU-05-00A0.dts:78.14-15 syntax error Jul 10 18:43:50 FATAL ERROR: Unable to parse input tree Jul 10 18:43:51 make: *** [BB-BONE-PRU-05-00A0.dtbo] Error 1 Jul 10 18:44:06 that’s what i get when i compile. don’t reach the firmware check stage :) Jul 10 18:44:49 Abhishek_: damn Jul 10 18:44:58 Abhishek_: forget that i ever asked this question Jul 10 20:58:12 /q praveendath92 Jul 10 21:05:05 vvu: /r :) Jul 10 23:13:59 * Abhishek_ yawns Jul 11 00:20:09 jkridner: what time are the HaD people coming tomorrow? Jul 11 00:20:35 they fly in sometime tonight and we go to Ann Arbor in the morning. Jul 11 00:20:49 BeagleLogic has been very helpful today... Jul 11 00:21:00 but, I still have the hardest time understanding LEDscape. Jul 11 00:23:06 mranostay did develop firmware for high-speed LED stuff using remoteproc Jul 11 00:23:16 this one seems to be based off libprussdrv Jul 11 00:25:17 * mranostay pokes in **** ENDING LOGGING AT Fri Jul 11 02:59:58 2014