**** BEGIN LOGGING AT Tue Aug 02 02:59:57 2016 Aug 02 16:01:18 alexhiam: hi!!! Aug 02 16:01:18 alexhiam: there? Aug 02 16:02:04 hi! Aug 02 16:02:35 did you see my report? Aug 02 16:03:22 alexhiam:^ Aug 02 16:08:13 kiran4399: yup, looks good Aug 02 16:08:23 and where are the docs? Aug 02 16:08:42 docs? Aug 02 16:09:01 alexhiam Aug 02 16:10:41 where the table says documentation is done - is that just on the wiki? Aug 02 16:11:29 alexhiam: yeah.... wiki+Readme.md Aug 02 16:11:51 k. just making sure I wasn't missing something Aug 02 16:20:22 hi alexhiam Aug 02 16:20:31 howdy Aug 02 16:21:02 Could you please check my last update on Python Integration thread? Aug 02 16:22:42 alexhiam: is there anything you want me to do except things which I already specified in the report? Aug 02 16:24:12 m_w: hi, are you there? Aug 02 16:30:25 amragaey: looks like you have a good idea of what to do Aug 02 16:30:56 since there's already that python running daemon that jkridner pointed to, I'd say just use that and start right in bone101 Aug 02 16:32:48 you should see in there where it kills the process - the way it does it now (kill the terminal process that's running python) it generates a SIGHUP in the Python program, which you can't really catch and do anything with because the terminal is gone and Python doesn't really work anymore Aug 02 16:33:46 kiran4399: that list looks good to me. I'd say testing the servo code is probably the highest priority Aug 02 16:34:11 alexhiam: ok.. I'll be on it.. Aug 02 16:34:27 alexhiam: btw.. I tested everything using thoses examples for robotics cape.. Aug 02 16:34:29 I am here Aug 02 16:34:39 but out on assignment Aug 02 16:34:54 so only breifly available Aug 02 16:35:44 pmezydlo: I see from the report that you are still suck on the DMA issue Aug 02 16:35:50 m_w: little question, not technical Aug 02 16:36:05 kiran4399: how'd that go? Aug 02 16:36:15 pmezydlo: go ahead Aug 02 16:36:21 alexhiam: there were lot of segfaults and errors.. Aug 02 16:36:22 m_w: I want to open a new branch to work on a generic framework and bus. Aug 02 16:36:22 Sitting on DMA the whole day made me very tired. Aug 02 16:36:22 I divide the work time for DMA and bus. Aug 02 16:36:22 What do you think? Aug 02 16:36:29 alexhiam: but I fixed them!!!!!!!! :-P Aug 02 16:36:36 kiran4399: great! Aug 02 16:36:36 pmezydlo: okay Aug 02 16:36:43 alexhiam: now everything is working!! Aug 02 16:37:44 pmezydlo: it is probably best to work on the framework and come back to the DMA if you have time Aug 02 16:37:46 m_w: We will fill gaps in dma as you will have some time Aug 02 16:37:48 alexhiam, I think JS can handle processes, I think that I could check function callback for whether the process is closed or not. Aug 02 16:37:59 m_w: fine Aug 02 16:38:26 pmezydlo: meanwhile I will continue to look into the DMA issue Aug 02 16:38:28 amragaey: in the node.js python runner, you mean? Aug 02 16:38:41 pmezydlo: did you add chip select support yet? Aug 02 16:39:16 chip seleck is supported Aug 02 16:39:38 alexhiam, yes handling subprocess through nodeJS Aug 02 16:39:39 pmezydlo: okay great Aug 02 16:40:00 amragaey: check out the current code. It sends the SIGHUP because it's killing the terminal process. You would just need to get the pid of the spawned python process (probably already get it in a callback), then send a SIGINT a second or so before killing the terminal Aug 02 16:40:28 you do still want to kill the terminal in case the python process gets stuck Aug 02 16:40:36 pmezydlo: sorry for not being more helpful with the dma issue Aug 02 16:41:14 when I get home from the trip I can put a solid block of time to take a closer look Aug 02 16:41:19 what is SIGHUP :) ? Aug 02 16:41:26 m_w: no problem is ok we have a lot of time Aug 02 16:41:33 HUP = hang up Aug 02 16:41:54 means the terminal 'hung up' on the process Aug 02 16:42:25 by dying before it Aug 02 16:42:46 pmezydlo: I was reading the through the reference manual, what a nightmare Aug 02 16:43:01 aha Aug 02 16:43:57 so you mean that I have to check if the terminal is closed before process terminatioin Aug 02 16:44:07 termination* Aug 02 16:44:08 m_w: About McSPI more here: http://www.ti.com/lit/ug/sprugr0c/sprugr0c.pdf Aug 02 16:44:41 Documentation of am35x ^^ Aug 02 16:45:21 controller spi is the same Aug 02 16:47:40 m_w: We'll talk tomorrow I will try to do something else Aug 02 16:49:46 amragaey: no. The current way it works is: user presses 'stop' button -> node.js runner kills terminal Aug 02 16:50:25 amragaey: you just need to add one more step: user presses 'stop' button -> node.js runner send SIGINT to python process (not terminal process) -> 1sec later kill terminal Aug 02 16:52:41 yes, I got you, but what is the difference between python process and terminal process :D ? Aug 02 16:53:56 the last time I looked at that node.js Python runner (it might also be different now...) it spawned a terminal process which then spawned the Python process Aug 02 16:54:57 amragaey: oh, and the reason the autorun directory isn't working for you is because it currently can only run node.js programs. If you have time it would be cool to get that working with Python Aug 02 16:56:29 okay, got to go Aug 02 16:57:14 No, it's working in autorun and all directories as well :D I dunno what is the reason to make the script run from 'autorun' Aug 02 16:58:04 I haven't look to nodejs python runner by the way, I was thinking of writing the code of running and killing process in JS myself Aug 02 16:58:37 you mean that : https://www.npmjs.com/package/python-runner ? Aug 02 17:02:52 amragaey: the one in cloud9 Aug 02 17:03:22 don't write a new one if it's already there Aug 02 17:04:32 should be in /var/lib/cloud9/ somewhere Aug 02 17:14:14 let me check it Aug 02 17:21:51 alexhiam, autorun isempty Aug 02 17:22:18 nothing found for python runner Aug 02 17:22:21 sure, autorun is just a directory to put programs you want run automatically when the board boots up Aug 02 17:23:36 aha, but the user would run the program for one time, why do we have to write it there? Aug 02 18:10:05 amragaey: you don't have to put anything there.. Aug 02 18:11:04 mmm may I got jason wrong then Aug 02 18:11:06 "There is already a daemon that will run any Python scripts put in /var/lib/cloud9/autorun (with .py extension) if that is of any help. Aug 02 18:11:06 " Aug 02 18:11:31 alexhiam, where I have to put python scripts/files ? Aug 02 18:12:38 mdp, alexhiam I am a bit sick . Will be sending in the weekly report a bit later today or maybe tomorrow. I am done with SPI .Going to finish the I2C firmware soon enough. Aug 02 18:12:48 ah, no, he's just saying there's already a python running daemon. It could be extended to run your bone101 programs Aug 02 18:13:06 I am so very sorry ;/ Aug 02 18:29:21 alexhiam, I'm running scripts using normal cmd line "python blink.py" in terminal, do we have something different here? sorry for questions but I feel that something isn't clear. Aug 02 18:29:58 in cloud9? you can click the run button Aug 02 19:09:30 no. running python programs from bone101 web interface. Aug 02 19:09:45 the code will be written into .py files Aug 02 19:09:59 then files will be executed in cmd line "python file.py" Aug 02 19:10:41 output will go to board direct Aug 02 19:10:56 if there's an error will be written back to user Aug 02 19:10:59 alexhiam, Aug 02 19:11:34 output will go to board direct? not sure what you mean by that Aug 02 19:11:50 what if the program is "print 10"? Aug 02 19:13:20 since PYBBIO file is included in the python script, the board will response.. for example blinking example will lead to LEDs being blinking :D Aug 02 19:14:11 if there's an output like a print statement, that should print the result to the user in the web page. Aug 02 19:15:04 any computational code will print the result noramlly to the user. Aug 02 19:29:19 i.e. stdout, stdin and stderr piped to the browser Aug 02 19:36:36 yes Aug 02 23:32:02 Back to India. Aug 03 01:10:45 stdout piped back to india? Aug 03 01:53:11 Back after finishing my 12-week internship at Google. Aug 03 01:58:12 let the exams begin... :D Aug 03 02:00:13 There's still a month and a half for that, but yeah, have a lot of catching up to do! **** ENDING LOGGING AT Wed Aug 03 02:59:58 2016