**** BEGIN LOGGING AT Mon Aug 15 02:59:58 2016
Aug 15 13:21:51 <chanakya_vc> bradfa, Been trying for the multibyte transfer. Program freezes on testing. I will let you know, when I have a successful transaction done.
Aug 15 13:22:10 <chanakya_vc> Earlier there had been a stack error. I have rectified that.
Aug 15 13:22:49 <chanakya_vc> I am really sorry for this. I will get it to work
Aug 15 14:02:48 <bradfa> chanakya_vc: ok, keep at it
Aug 15 14:03:22 <chanakya_vc> Okay bradfa .Will keep you updated
Aug 15 14:30:04 <chanakya_vc> bradfa, I have a doubt. If I take a uint8_t pointer and make it point to an address held by the tx_buf(void pointer), it will point to the first 8 bits of the buffer right(starting from the MSB )?
Aug 15 14:30:52 <chanakya_vc> And on incrementing the pointer it will then point to the next 8 bits right?
Aug 15 14:30:59 <chanakya_vc> foreverska_, ^^
Aug 15 14:41:49 <foreverska_> Yes and yes if I'm reading that right
Aug 15 14:44:37 <chanakya_vc> foreverska_, I am stuck with multibyte transfer in SPI. So I am trying out this idea. struct spi_transfer gives the length of the buffer that the protocol driver is demanding along with the tx_buf and rx_buf
Aug 15 14:46:12 <chanakya_vc> So I am running a loop with i<len and incrementing a uint8_t pointer. I write the values stored at the address pointed to by this in the hope that I can transfer 8 bits to the firmware in order for it to bibang
Aug 15 14:47:04 <chanakya_vc> But don't seem to be getting the right results. Or I am not able to interpret them correctly .
Aug 15 14:50:26 <foreverska_> What is on the other side of the SPI line to verify correctness?
Aug 15 14:52:11 <chanakya_vc> foreverska_, Well m_w had written a program to verify spi. I think I am confused as to how it is handling multibyte transfers. here is the link:https://github.com/mwelling/spi-test
Aug 15 14:52:25 <chanakya_vc> I have looped back mosi to miso in my firmware
Aug 15 14:54:45 <foreverska_> Gotcha, and it's not coming back garbled, it's just out of order when it arrives?
Aug 15 14:55:19 <chanakya_vc> And these are the results I am getting. Don't seem to make sense to me:http://pastebin.com/LgbPSXym
Aug 15 14:56:08 <chanakya_vc> foreverska_, Have a look
Aug 15 14:57:28 <chanakya_vc> I will push my code if you want to look at the driver. I am still at a loss as to why this is not working. There doesn't seem to be any error :(
Aug 15 15:00:46 <foreverska_> It is kinda odd because you're never picking up the first byte and the rest tend to be fairly random.  Is your driver running at the same Hz?
Aug 15 15:02:00 <chanakya_vc> foreverska_, The confusion I have is whether in a multibyte transfer the protocol driver simply writes the entire data in the buffer or it sends stuff byte by byte?
Aug 15 15:03:04 <chanakya_vc> That may be a problem. Let me verify. I think it was around 6.5 Mhz the last time(atleast the clock frequency was this)
Aug 15 16:29:09 <ZeekHuge> hahahaha ! https://github.com/torvalds/linux/blob/d158fc7f36a25e19791d25a55da5623399a2644f/fs/ext4/resize.c#L698
Aug 15 16:29:37 <ZeekHuge> I always knew mathematics has got it wrong ..
Aug 15 16:34:14 <pmezydlo> You can make the patch :)
Aug 15 16:39:21 <ZeekHuge> to the math community ;)
Aug 15 16:39:40 <ZeekHuge> should rather focus on my work :D
Aug 15 16:39:58 <pmezydlo> linux-math mailing list:)
Aug 15 16:40:14 <ZeekHuge> just came around that on other channel.
Aug 15 16:40:55 <pmezydlo> unfortunatelly it is not available http://vger.kernel.org/vger-lists.html
Aug 15 16:51:37 <m_w> https://github.com/torvalds/linux/blob/d158fc7f36a25e19791d25a55da5623399a2644f/fs/ext4/resize.c#L652
Aug 15 16:53:10 <m_w> still funny
Aug 15 16:54:48 <pmezydlo> hi m_w, how are you?
Aug 15 16:55:10 <m_w> another day another dollar
Aug 15 16:55:18 <m_w> same old same old
Aug 15 16:55:38 <m_w> good
Aug 15 16:55:41 <pmezydlo> I still clean up code
Aug 15 16:55:56 <pmezydlo> looks better
Aug 15 16:56:17 <m_w> greg's review was probably a big eye opener
Aug 15 16:56:53 <m_w> did you understand all of his comments?
Aug 15 16:57:15 <chanakya_vc> m_w, Ah been trying to get this thing to work. Am getting this result, doesn't make sense to me at all:http://pastebin.com/LgbPSXym
Aug 15 16:57:32 <pmezydlo> I have only a few doubts
Aug 15 16:57:48 <chanakya_vc> I got to program to "unfreeze" though.  Please do check it out when free
Aug 15 16:58:01 <chanakya_vc> I will just push the code
Aug 15 16:58:31 <m_w> chanakya_vc: what are you connecting to MISO?
Aug 15 16:58:47 <chanakya_vc> Looping back mosi to miso
Aug 15 16:58:59 <chanakya_vc> But even MOSI doesn;t add up
Aug 15 16:59:10 <pmezydlo> m_w: few amendments, push code and We will talk about doubts
Aug 15 16:59:46 <m_w> yeah respond inline to questions he had
Aug 15 17:00:13 <m_w> pmezydlo: you have your mail client setup?
Aug 15 17:00:24 <pmezydlo> yes
Aug 15 17:00:53 <pmezydlo> mutt running
Aug 15 17:00:53 <m_w> chanakya_vc: what do you mean MOSI doesn't add up?
Aug 15 17:01:48 <chanakya_vc> Ah sending 06 as MOSI two bytes, I am not able to understand why is the second byte FF M
Aug 15 17:01:49 <chanakya_vc> mw
Aug 15 17:01:52 <chanakya_vc> m_w,
Aug 15 17:02:13 <chanakya_vc> Just a moment, let me update the code
Aug 15 17:02:22 <m_w> no it is not two bytes
Aug 15 17:02:30 <m_w> it is two nibbles
Aug 15 17:02:49 <m_w> 4 bits per hex digit
Aug 15 17:02:53 <m_w> ;)
Aug 15 17:03:52 <chanakya_vc> Ohh
Aug 15 17:03:57 <chanakya_vc> hmmn
Aug 15 17:04:06 <m_w> last week, you guys getting nervous yet?
Aug 15 17:04:11 <chanakya_vc> me yes
Aug 15 17:04:26 <chanakya_vc> especially when I have run into problems m_w
Aug 15 17:04:57 <chanakya_vc> And college has reopened, so classes are also a problem
Aug 15 17:05:31 <m_w> you really need to engage with your mentors when issues arise, I can't always be on irc to save you
Aug 15 17:05:44 <m_w> but I can try
Aug 15 17:07:20 <chanakya_vc> Yes I understand that m_w .
Aug 15 17:07:43 <chanakya_vc> But at the moment you are the only one who can save me :P I have pushed the code..
Aug 15 17:07:52 <m_w> ha
Aug 15 17:08:27 <m_w> you guys need to remember to complete your final report for tomorrow, this is important
Aug 15 17:08:28 <chanakya_vc> I have removed lsb_first_transfer just for the sake of testing my logic
Aug 15 17:08:42 <m_w> link?
Aug 15 17:08:48 <chanakya_vc> Yes that is also due :(  :(
Aug 15 17:09:09 <chanakya_vc> https://github.com/chanakya-vc/PRU-I2C_SPI_master/blob/wip_on_spi/SPI_Driver/pru0_spi-subsystem.c
Aug 15 17:09:10 <chanakya_vc> m_w,
Aug 15 17:10:34 <m_w> I think this would sort of work
Aug 15 17:11:01 <chanakya_vc> I can't see any flaw in the logic..yet it's not m_w  :(
Aug 15 17:11:02 <m_w> but the chip select will toggle after each word of the transaction
Aug 15 17:11:47 <m_w> which is not desired on most devices and will trash the transaction
Aug 15 17:13:21 <chanakya_vc> okay m_w . But your code should work right?
Aug 15 17:13:21 <m_w> also the delay between words may be longer than expected because we are feeding a word at a time
Aug 15 17:13:39 <chanakya_vc> hmmn...that may also be an issue
Aug 15 17:14:27 <m_w> I used an active feedback (FPGA) to test the IP previously
Aug 15 17:14:46 <chanakya_vc> The CS problem I can fix easily by telling the firmware the length of the word beforehand
Aug 15 17:15:04 <chanakya_vc> okay so it is not necessary that the code is not working
Aug 15 17:15:06 <chanakya_vc>  m_w ?
Aug 15 17:15:09 <m_w> sure that could work
Aug 15 17:17:30 <chanakya_vc> Hmmn so I also need to probably get an FPGA and learn how to program one.
Aug 15 17:17:44 <chanakya_vc> m_w, I don't see any other way
Aug 15 17:20:02 <chanakya_vc> Also just one clarification, when you say that 2 bytes to transfer in your spi-test program m_w , it is basically calling spidev which is calling spi-core to write those two bytes together in the tx_buf right?
Aug 15 17:20:16 <chanakya_vc> I mean it sends the two bytes together right?
Aug 15 17:20:57 <chanakya_vc> Because on running when I transfer 2 bytes, MOSI appears twice. So I was confused
Aug 15 17:23:57 <m_w> 1 byte per line
Aug 15 17:24:58 <m_w> they are sent together via a buffer through the spidev interface, yes
Aug 15 17:26:45 <chanakya_vc> Okay m_w . So you think it  just a problem of mismatch of speed?
Aug 15 17:28:33 <m_w> did you change the firmware at all while do this update?
Aug 15 17:31:07 <chanakya_vc> Ah no, just changed the last line where I looped mosi back to miso
Aug 15 17:31:41 <m_w> the problem with a simple loopback it timing of transition of data and clock are not right
Aug 15 17:32:09 <chanakya_vc> Ah okay, so I need to actually test it.
Aug 15 17:32:21 <chanakya_vc> with a device or FPGA
Aug 15 17:32:34 <chanakya_vc> But the logic seems to be correct right m_w ?
Aug 15 17:33:06 <m_w> as long as you add proper chip select handling sure
Aug 15 17:33:39 <chanakya_vc> Okay m_w . I was so worried as to where am I going wrong
Aug 15 17:34:49 <chanakya_vc> Any advice as to how should I go about testing I2C?
Aug 15 17:34:55 <chanakya_vc> FPGA again?
Aug 15 17:34:55 <m_w> well the simple loopback should work in theory, I found that it was not working as expected
Aug 15 17:35:02 <m_w> possibly
Aug 15 17:35:37 <m_w> it would be good to test on actual I2C devices
Aug 15 17:35:53 <m_w> same with SPI
Aug 15 17:36:25 <chanakya_vc> Ohkay, regarding the dtc file m_w , I just removed the spidev registration part and all the rest is same
Aug 15 17:36:27 <m_w> FPGA can be considered an actual device with proper IP loaded
Aug 15 17:36:43 <chanakya_vc> for I2C
Aug 15 17:36:51 <chanakya_vc> Ohkay m_w
Aug 15 17:36:51 <m_w> yeah you need to post the dts files to your repository
Aug 15 17:37:15 <chanakya_vc> Yeah I will. I have been so caught up with this multibyte transfer
Aug 15 17:37:35 <chanakya_vc> I also need to start documentation
Aug 15 17:39:26 <m_w> since your report is due tomorrow I would focus on that
Aug 15 17:41:15 <chanakya_vc> So documentation first
Aug 15 17:42:11 <m_w> well it is up to you
Aug 15 17:42:33 <m_w> but if you miss the last report you may be in for some trouble upon review
Aug 15 17:42:52 <m_w> remember it is a comprehensive report
Aug 15 17:44:19 <chanakya_vc> Techinically I can finish up all the code and documentation tonight itself m_w , you know if I work through the night. In my report I can write that the single byte transfer in SPI has been thoroughly tested. Also I did get some results for looping back I2C .
Aug 15 17:44:50 <chanakya_vc> Perhaps then I can say that I would dedicate the rest of the week to just testing on actual devices.
Aug 15 17:45:04 <chanakya_vc> m_w, Would that be acceptable?
Aug 15 17:45:32 <m_w> okay hopefully you have the wits to write a good report on little sleep
Aug 15 17:46:09 <chanakya_vc> Don't count on that m_w . I have classes in the morning. Probably gonna sleep in those :P
Aug 15 17:46:16 <chanakya_vc> m_w, :P
Aug 15 17:46:19 <m_w> ha
Aug 15 17:48:03 <chanakya_vc> Okay to work on documentation. I will probably push the code. Thanks for verifying the logic m_w . I was so worried about that.
Aug 15 18:08:00 <bradfa> chanakya_vc: please ensure you have your report written for tomorrow, that is priority number 1 since this week is inteded to be for documentation and cleanup.  If you get the report done, then you can go back to validating your firmware/driver interface and doing more testing/debugging.
Aug 15 18:17:53 <chanakya_vc> Yes bradfa I am working on the documentation right now. Ah can you give me an idea as to what you would expect in the report?
Aug 15 18:19:44 <chanakya_vc> Just what has been achieved, how it was achieved and scope for improvement  would do right bradfa ?
Aug 15 18:21:10 <chanakya_vc> I will work through the night and possibly post the report+ documentation before tomorrow morning. I will also organize the code on the repo so that it is easier to follow bradfa .
Aug 15 18:22:33 <chanakya_vc> And then as you suggested I will focus on more testing/debugging throughout the week till Sunday.
Aug 15 18:47:33 <bradfa> chanakya_vc: what you have accomplished, what you haven't accomplished, why you haven't accomplished things, lessons learned and things you'd do differently, etc
Aug 15 18:48:01 <bradfa> chanakya_vc: as per last week's meeting guidelines
Aug 15 18:48:07 <chanakya_vc> Yeah got a lot of those bradfa :P
Aug 15 18:48:33 <chanakya_vc> I will send it on time bradfa , I am working on it right now only
Aug 15 18:48:36 <bradfa> chanakya_vc: also, what work can be done in the future on the code bases to make them better
Aug 15 18:49:00 <chanakya_vc> Okay got it bradfa
Aug 15 19:20:10 <amragaey> hi jkridner|work
Aug 15 19:21:55 <amragaey> I'll finish python runner today
Aug 15 20:03:49 <ZeekHuge> :D jic23 !
Aug 15 20:03:54 <ZeekHuge> Hi !
Aug 15 20:06:11 <ZeekHuge> m_w: there ?
Aug 15 20:06:36 <m_w> of course
Aug 15 20:06:45 <ZeekHuge> :)
Aug 15 20:06:57 <ZeekHuge> so these file :
Aug 15 20:07:05 <ZeekHuge> https://github.com/ZeekHuge/BeagleScope/blob/wip_parallel_interface_take2/driver/pi_bus.c
Aug 15 20:07:13 <ZeekHuge> its the platform_driver
Aug 15 20:07:26 <ZeekHuge> and https://github.com/ZeekHuge/BeagleScope/blob/wip_parallel_interface_take2/driver/parallel_interface.c
Aug 15 20:07:30 <ZeekHuge> is the core driver
Aug 15 20:07:56 <ZeekHuge> Now they are loading and detecting all the child nodes perfectly ..
Aug 15 20:08:14 <ZeekHuge> and declaring devices associated with those nodes
Aug 15 20:08:17 <ZeekHuge> but !
Aug 15 20:08:27 <ZeekHuge> when I am rebooting the PRUs ...
Aug 15 20:08:33 <ZeekHuge> a big big big ... oops
Aug 15 20:08:33 <m_w> awe there is a but
Aug 15 20:08:45 <m_w> pastebin it
Aug 15 20:08:50 <ZeekHuge> so I am not freeing up the resources ...
Aug 15 20:09:08 <ZeekHuge> let me try ... last time it just freezed with no output.
Aug 15 20:09:32 <m_w> you have a serial console?
Aug 15 20:09:50 <m_w> you could get the logs there possibly
Aug 15 20:10:08 <m_w> if the system tanks
Aug 15 20:10:30 <ZeekHuge> serial console.. not here .
Aug 15 20:10:51 <ZeekHuge> and I am now unable to connect through usb
Aug 15 20:11:01 * ZeekHuge is looking for eth cable
Aug 15 20:13:14 <ZeekHuge> into the BBB through eth
Aug 15 20:13:46 <ZeekHuge> again that crazy condition... no kernel module got loaded.
Aug 15 20:13:54 <ZeekHuge> running depmod -a
Aug 15 20:15:01 <ZeekHuge> now, back to normal
Aug 15 20:15:08 <ZeekHuge> loading beaglescope modules
Aug 15 20:17:48 <ZeekHuge> m_w: no message after [pi_bus] pi_bus_platform_remove and just freezes up.
Aug 15 20:18:06 <ZeekHuge> *pibus_platform_remove
Aug 15 20:18:39 <m_w> :(
Aug 15 20:19:02 <ZeekHuge> I can probably fix this freezing up .. let me try
Aug 15 20:20:12 <ds2> hmmm
Aug 15 20:21:35 <ZeekHuge> m_w: freezing up - fixed
Aug 15 20:23:04 <m_w> ha that was fast
Aug 15 20:23:16 <m_w> forgot some essential clean up?
Aug 15 20:24:56 <ZeekHuge> the oops is still there .. just that I can now see it and the board does not freezes up
Aug 15 20:25:08 <ZeekHuge> 385 lines of oops
Aug 15 20:25:17 <ZeekHuge> http://paste.debian.net/789749/
Aug 15 20:25:19 <ZeekHuge> m_w: ^
Aug 15 20:26:37 <ZeekHuge> I am not understanding slot #4 and slot #5 when I am just loading one overlay
Aug 15 20:31:33 <ZeekHuge> or this one ... http://paste.debian.net/789751/
Aug 15 20:31:47 <ZeekHuge> the 2nd one do not have that #5 slot
Aug 15 20:31:59 <m_w> yikes
Aug 15 20:32:06 <ZeekHuge> dont know why..
Aug 15 20:35:16 <ZeekHuge> m_w: what I see in the dmesg is that none of the release methods from the parallal_interface.c  are being called
Aug 15 20:35:26 <ZeekHuge> but only from pi
Aug 15 20:35:30 <m_w> yeah
Aug 15 20:35:31 <ZeekHuge> *pi_bus
Aug 15 20:35:36 <ZeekHuge> line number 26 and 27
Aug 15 20:36:06 <ZeekHuge> So I am not able to understand the object destruction sequence
Aug 15 20:37:11 <ZeekHuge> https://github.com/ZeekHuge/BeagleScope/blob/wip_parallel_interface_take2/driver/parallel_interface.c#L63
Aug 15 20:37:18 <ZeekHuge> since its devm_*
Aug 15 20:37:44 <ZeekHuge> it should be destructed when the parent goes down
Aug 15 20:38:02 <ZeekHuge> and parent == pdev->dev from pi_bus
Aug 15 20:38:31 <ZeekHuge> shouldnt that what happen ?
Aug 15 20:38:39 <m_w> https://github.com/ZeekHuge/BeagleScope/blob/wip_parallel_interface_take2/driver/pi_bus.c#L50
Aug 15 20:38:50 <m_w> try removing this line
Aug 15 20:39:48 <ZeekHuge> okay ... rebooting bbb
Aug 15 20:40:17 <ZeekHuge> that makes sense ... as we are never actually registering the device .
Aug 15 20:40:24 <ZeekHuge> so os should manage that
Aug 15 20:40:40 <m_w> not sure
Aug 15 20:41:08 <m_w> try to trace through your code in a web browser :)
Aug 15 20:45:19 <m_w> any luck?
Aug 15 20:45:33 <ZeekHuge> m_w: new oops :)
Aug 15 20:45:34 <ZeekHuge> http://paste.debian.net/789754/
Aug 15 20:45:41 <ZeekHuge> just a bit different
Aug 15 20:46:09 <ZeekHuge> and that is just a random delay I guess
Aug 15 20:47:45 <ZeekHuge> m_w: message is different now !
Aug 15 20:47:56 <m_w> so we got rid of the first warning
Aug 15 20:47:56 <ZeekHuge> oops message
Aug 15 20:48:04 <m_w> what does it say?
Aug 15 20:48:29 <ZeekHuge> sysfs: cannot create duplicate filename '/devices/platform/ocp/ocp:pi0@f00/pi-0'
Aug 15 20:48:35 <m_w> exactly
Aug 15 20:48:54 <m_w> this was happening before, but after another warning
Aug 15 20:49:59 <ZeekHuge> yeah ..
Aug 15 20:50:36 <m_w> missing an unregister somewhere perhaps
Aug 15 20:51:46 <ZeekHuge> m_w: unregister is there but the parent function is not being called.
Aug 15 20:51:48 <ZeekHuge> https://github.com/ZeekHuge/BeagleScope/blob/wip_parallel_interface_take2/driver/parallel_interface.c#L45
Aug 15 20:53:48 <ZeekHuge> oh ! probably I need to call unregister separately for all the devices
Aug 15 20:54:24 <m_w> let see
Aug 15 20:56:04 <m_w> yeah you have to
Aug 15 20:56:18 <m_w> device_for_each_child
Aug 15 21:00:10 <amragaey> I'm using child_process to execute python scripts on beaglebone
Aug 15 21:00:37 <amragaey> I found two methods that do that, spawn and exec
Aug 15 21:01:20 <amragaey> spawn spawns the child asynch without blocking NodeJS, and doesn't take a callback
Aug 15 21:01:56 <amragaey> exec executes commands in a shell and accepts a callback
Aug 15 21:02:27 <amragaey> I tried both, they both do the same job.
Aug 15 21:02:47 <amragaey> but exec is friendly in working with stdin than spawn
Aug 15 21:03:12 <amragaey> I had to use stdin.write() to pass any user input to that running process
Aug 15 21:03:39 <amragaey> but in exec, I ran a command that can take the input from user as a text file
Aug 15 21:04:12 <amragaey> as example, "python script.py -< amr.text  2>&1 | tee -a out.text"
Aug 15 21:04:30 <amragaey> amr.text is a textfile file that contains user inputs.
Aug 15 21:05:22 <amragaey> and stdout is returned to out.text, if there's an error the stderr is returned to out.text
Aug 15 21:06:13 <amragaey> this is my final solution for now, and that I found smart than spawn event listeners
Aug 15 21:06:54 <amragaey> the output file, could be read by the function b.readTextfile() and returned to the user page.
Aug 15 21:07:39 <amragaey> this is my progress till now
Aug 15 21:07:56 <amragaey> I'm working hard to get the full python runner and add it to bonescript
Aug 15 21:08:21 <amragaey> I'm currently test it with simple requests in Express NodeJS framework
Aug 15 21:09:37 <amragaey> there was an issue with my beaglebone, that I can't run/test new functions.
Aug 15 21:12:53 <amragaey> I sent more than an email to my mentors, and on mailing list and IRC, and not getting a response.
Aug 15 21:13:00 <amragaey> : (
Aug 15 21:14:50 <m_w> amragaey: what is the problem?
Aug 15 21:17:02 <amragaey> I'm into a new phase in my project, and haven't get a support. I have no information about the branch or files I have to add my code to. I created my own branch and going through every single file to check where I have to put my code.
Aug 15 21:17:57 <amragaey> I found most of code on index.js, but when adding a new function the beaglebone fails to load the web server.
Aug 15 21:18:35 <jkridner|work> amragaey: do you have the exact patch?
Aug 15 21:19:17 <amragaey> I added my file 'python-runner' into bonescript/src
Aug 15 21:19:26 <amragaey> and contributing to it now.
Aug 15 21:20:01 <amragaey> branch 'python-int'
Aug 15 21:20:08 <jkridner|work> link?
Aug 15 21:21:01 <amragaey> https://github.com/amragaey/bonescript/blob/python-runner/src/python_runner.js
Aug 15 21:25:43 <ZeekHuge> m_w: what are the flags of struct device_node
Aug 15 21:25:57 <jkridner|work> amragaey: I don't see that you exposed those functions.
Aug 15 21:26:14 <ZeekHuge> and I am not able to find the source of struct device_node
Aug 15 21:26:45 <jkridner|work> amragaey: are you running this locally or over the web page?
Aug 15 21:27:25 <ZeekHuge> it looks like its defined everywhere
Aug 15 21:27:44 <m_w> http://lxr.free-electrons.com/source/include/linux/of.h#L49
Aug 15 21:27:47 <amragaey> I'm running local NodeJS web server using Express framework to test the code, jkridner|work
Aug 15 21:28:28 <amragaey> I'm not able to write in index.js (if it's the right file)
Aug 15 21:29:09 <amragaey> so will use this file as a module, and expose it to bonescript if possible
Aug 15 21:29:41 <ZeekHuge> uhm..
Aug 15 21:29:57 <m_w> http://events.linuxfoundation.org/sites/events/files/slides/dt_internals.pdf
Aug 15 21:31:01 <m_w> http://lxr.free-electrons.com/source/include/linux/of.h#L140
Aug 15 21:31:23 <m_w> here are the flag descriptions ^^
Aug 15 21:42:18 <jkridner|work> amragaey: exposing to bonescript web server is fairly simple, but you need to follow some argument conventions a bit... last argument always has to be a callback.
Aug 15 21:43:48 <amragaey> jkridner|work, yes I see it and used it on my python-runner
Aug 15 21:43:51 <amragaey> Am i going right till now ?
Aug 15 21:50:02 <amragaey> when I added a simple function on index.js, the server terminate I think for some error.. and i'm not able to access 192.168.7.2 anymore!
Aug 15 21:54:36 <jkridner|playdoh> my network is really acting up.
Aug 15 22:00:29 <jkridner> amragaey: to add a RPC, see https://github.com/amragaey/bonescript/blob/python-runner/src/index.js#L557-L581... and is exposed for remote calling by https://github.com/amragaey/bonescript/blob/python-runner/src/socket_handlers.js#L95-L111
Aug 15 22:01:10 <ZeekHuge> m_w: after a few more tweaks, working perfectly fine now
Aug 15 22:04:08 <m_w> phew
Aug 15 22:04:35 <m_w> ZeekHuge: you post the changes?
Aug 15 22:04:53 <ZeekHuge> yep .. pushed them up
Aug 15 22:06:10 <ZeekHuge> https://github.com/ZeekHuge/BeagleScope/commits/wip_parallel_interface_take2
Aug 15 22:06:15 <ZeekHuge> last 4 commits
Aug 15 22:07:48 <amragaey> jkridner, what is modmsg? and how will I use my object methods like pythonRunner.run()?
Aug 15 22:12:04 <jkridner> yeah, you need to make unique function names, not member names like simply 'run'....
Aug 15 22:12:29 <jkridner> the methods get exposed over the RPC.... you should see simple examples like writeTextFile().
Aug 15 22:13:05 <jkridner> https://github.com/amragaey/bonescript/blob/python-runner/src/index.js#L488-L503
Aug 15 22:13:17 <jkridner> see that an 'args' array is required.
Aug 15 22:14:12 <jkridner> all of the functions that are members of what bonescript exports and has an 'args' member that is an array of argument names will be exposed to be accessed.
Aug 15 22:24:15 <amragaey> jkridner, check how I expose it now http://i.imgur.com/BKJkI0d.png
Aug 15 22:24:38 <amragaey> could I do the same in bonescript
Aug 15 22:25:34 <amragaey> or the functions should be seaparated?
Aug 15 22:27:36 <jkridner> yuck!!!!!
Aug 15 22:27:43 <jkridner> why are you making a new web server?
Aug 15 22:28:14 <amragaey> this is locally outside bonescript
Aug 15 22:28:18 <jkridner> why?
Aug 15 22:28:40 <amragaey> just to test my pythonRunner, because i'm not able to test it in bonescript
Aug 15 22:30:25 <amragaey> when I edit in index.js, the bone web server terminate and I can't access 192.168.7.2! I had to create another sd image : (
Aug 15 22:33:05 <jkridner> you must have put in a syntax error.
Aug 15 22:33:50 <amragaey> sure
Aug 15 22:34:42 <jkridner> so, why didn't you share what you did?
Aug 15 22:35:04 <jkridner> doesn't make any sense to me to create a new web server.
Aug 15 22:35:12 <jkridner> I'm not interested in reading it.
Aug 15 22:35:51 <amragaey> I sent many emails the past few days and didn't get a response.
Aug 15 22:36:05 <amragaey> I just wanted to save time
Aug 15 22:36:56 <amragaey> we will use the module only, which is "pythonRunner" in bonescript.
Aug 15 22:37:00 <jkridner> k, that's fine as some parallel thing, but I'm not interested in trying to debug it.
Aug 15 22:38:47 <amragaey> what do you think now ?
Aug 15 22:40:03 <jkridner> I still think you could have started with b.writeTextFile(), but I get that a 'runner' will make attaching to the stdout/stderr/stdin more simple.
Aug 15 22:40:15 <jkridner> what I don't get is how you plan to call your runner at all.
Aug 15 22:40:28 <jkridner> if you could describe that somehow, I think things would be easier.
Aug 15 22:40:56 <jkridner> adding functions to the RPC should have been simple.... I'm hopeful you understand it a bit better after I showed you the example of how b.writeTextFile() works.
Aug 15 22:43:45 <amragaey> I added this page : https://github.com/amragaey/bone101/blob/python-integration/Support/bone101/python/index.html
Aug 15 22:43:59 <amragaey> the user will write the code, and stdin (if exists)
Aug 15 22:44:34 <amragaey> after clicking on 'run', I'll create instance of pythonRunner with the input data
Aug 15 22:44:49 <amragaey> run the python code, return stdout & stderr to a file.
Aug 15 22:45:01 <amragaey> and return the file output back to the user.
Aug 15 22:45:29 <amragaey> pythonRunner is almost finished
Aug 15 22:46:27 <amragaey> I'm figuring out now how I could include this runner into bonescript, to expose this functions when user click 'run' or 'reset'
Aug 15 22:48:10 <amragaey> I read the implementation of b.writeTextFile() but it's not enough for the runner, I'll have to add more functions and ends up creating a module.
Aug 15 22:51:02 <jkridner> you'd just need some kind of pythonRunnerInit() function to create the runner.  I think you are just making the API more complex than it need to be.
Aug 15 22:54:09 <amragaey> I will write a detailed document tomorrow for everything I wrote in the runner.
Aug 15 22:54:36 <amragaey> I think it'll make changes easier later.
Aug 15 22:55:37 <amragaey> If you simply change the file attribute from 'script.py' to 'script.rb' you can run ruby examples also : )
Aug 15 23:01:44 <jkridner|playdoh> The autorun service also does that.
Aug 15 23:04:44 <amragaey> how does autorun work? alex told me that autorun is just a directory to put programs you want run automatically when the board boots up
Aug 15 23:10:52 <amragaey> I checked it
Aug 15 23:11:23 <amragaey> well, this could be in web page too
Aug 15 23:23:43 <jkridner> amragaey: not when it boots, but when files are put there. and stopped again when they are removed.
Aug 15 23:24:07 <jkridner> amragaey: the service is: https://github.com/jadonk/bonescript/blob/master/src/autorun.js
Aug 15 23:24:57 <jkridner> seems to me the thing to do would be to add some way to attach to the stdin/stdout/stderr of the individual streams from that service.... but, it is run in a different process than bonescript's web server.
Aug 15 23:26:13 <jkridner> amragaey: right now, all the stderr/stdout is just fed to system logs.
Aug 15 23:33:21 <amragaey> jkridner, I'm not getting how exactly i'm getting to use it
Aug 15 23:33:35 <amragaey> jkridner, just two mins and will push my code.. it's much simple
Aug 15 23:39:42 <amragaey> jkridner, https://github.com/amragaey/bonescript/blob/python-runner/src/python_runner.js
Aug 15 23:40:00 <jkridner> is that changed?
Aug 15 23:40:34 <amragaey> yes
Aug 15 23:40:46 <amragaey> I added two new functions
Aug 15 23:40:56 <jkridner> the 'pythonRunner' function has sub-functions, which won't work with the bonescript RPC.
Aug 15 23:41:55 <jkridner> you'd have to make some kind if 'init' function to call it and create a method for referencing it.
Aug 15 23:41:56 <amragaey> then, I have to make each one a separate function
Aug 15 23:42:34 <amragaey> jkridner, is there an example ?
Aug 15 23:42:59 <jkridner> the reason is that the RPC is meant for running things remotely and doesn't have a way to create objects within the page itself.
Aug 15 23:44:00 <jkridner> https://github.com/amragaey/bonescript/blob/python-runner/src/my.js#L355-L396 is a fairly complex example of creating a wrapper for a remotely created instance.
Aug 15 23:44:32 <jkridner> it maintains an array of open ports.
Aug 15 23:45:00 <jkridner> https://github.com/amragaey/bonescript/blob/python-runner/src/iic.js is an example of how it is used.
Aug 15 23:45:22 <jkridner> https://github.com/amragaey/bonescript/blob/python-runner/src/serial.js is similar.
Aug 15 23:46:26 <jkridner> this is the way I get to modules remotely that require an object to be created/opened.
Aug 15 23:47:10 <jkridner> the 'port' is a required argument and is what uniquifies the instance.
Aug 15 23:52:24 <amragaey> it doesn't look simple
Aug 15 23:54:47 <amragaey> jkridner, so the other solution is to make the functions separate and call each other ?
Aug 15 23:55:17 <jkridner> yeah.
Aug 15 23:56:16 <jkridner> the whole issue is not being able to make real objects on the browser/client side without writing a separate browser-side library.
Aug 15 23:56:44 <jkridner> I don't actually copy the bonescript library to the browser, I just create stub functions to pass messages.
Aug 15 23:59:02 <amragaey> aha
Aug 16 00:00:30 <amragaey> Is it possible to continue coding in the final week of documentation ?
Aug 16 00:05:01 <amragaey> how could I debug my code in bonescript, as not to install new image for every syntax error : ( ?
Aug 16 00:12:35 <amragaey> jkridner, and what do you like me to do for the final week ?
**** ENDING LOGGING AT Tue Aug 16 02:59:58 2016