**** BEGIN LOGGING AT Wed Mar 20 02:59:57 2019 Mar 20 04:41:22 gm all Mar 20 05:01:01 Gm Mar 20 05:02:35 Jjkridner i had followed the derek molloy video and i have electronics background Mar 20 05:09:52 Reference Design For A GPIO-based Parallel Bi-Directional Bus Mar 20 05:09:52 I am interested in this project and last time on meeting is said to see the logs as this topic has been discussed earlier and i have seen that also Mar 20 16:34:56 hi all! Mar 20 16:34:58 meeting time! Mar 20 16:35:22 we should all be showing up this time every week. Mar 20 16:35:43 Hi jkridner Mar 20 16:35:54 howdy abhishek_ ! Mar 20 16:37:06 On vacation this week. Mar 20 16:37:35 Any prospective students around? Mar 20 16:44:49 i am currently working on the swift register using pocket beagle that i have Mar 20 16:46:02 i have also seen logs from 26-27 feb Mar 20 16:47:41 http://logs.nslu2-linux.org/livelogs/beagle-gsoc/beagle-gsoc.20190228.txt Mar 20 16:52:26 i want to to ask that i have very less knowledge about kerenel tree as required for it but i have worked on i2c and have knowlege about linux file system Mar 20 16:53:16 can you share any good resources for that Mar 20 16:53:42 what is "Swift register"? Mar 20 16:53:47 jkridner abhishek_ Hi :) I have been trying to add support for Techlab Cape in the makecode target and have finished adding support for the rgb led , buzzer and 7-seg led display in the simulator only mode (ie. does not interact with actual board but works from browser). I am currently setting up a prototype of the cape so as to bring in the board support.. I am having my exams this week that's why the work is Mar 20 16:53:47 hi vaishnav98_ ! Mar 20 16:53:48 progressing very slowly. Mar 20 16:59:02 http://www.ti.com/lit/ds/sdfs071b/sdfs071b.pdf as it was not available here so i buy 74hc595 swift register Mar 20 17:00:51 * hendersa is here. Mar 20 17:00:59 Meeting at work ran long. Mar 20 17:02:31 I am reusing the libraries from the makecode maker repositories for the support (neopixel library there modified to rgb led support , music library modified to support the buzzer).. currently I am modifying the built js files to include the bonescript functions which I believe is not the best method as it makes difficult to make further improvements.can you provide any suggestions for a better implementation. Mar 20 17:04:12 it was mention on the site section the only differece is that i see in the chip 74hc595 is that it have only left shift of bits only instead the chip that os mention that is SN54F299 have both left and right shift but as it was not available to me here is it fine to work on that chip Mar 20 17:05:39 https://github.com/vaishnav98/pxt-beaglebone/blob/27bec389745d8e4c16c50bf36e199dcb81422696/built/common-sim.js#L1242 this is an example of my implementation. Mar 20 17:09:21 vaishnav98_: do you have a live version up? Mar 20 17:09:52 vaishnav98_: I think we need to figure out a way to use kernel drivers for everything possible. Mar 20 17:10:08 and only use stuff like BoneScript for managing that and doing remote file I/O. Mar 20 17:10:26 and tying into things like system events or other tricks needed to talk to the drivers. Mar 20 17:10:35 not trying to ever bitbang with BoneScript. Mar 20 17:11:58 jkridner : live version of the simulator?It is available here : https://e-scape.me/pxt-beaglebone/ Mar 20 17:13:10 but that version does not have the Techlab support reflected, I was planning to push the changes after testing with a prototype set-up Mar 20 17:13:11 * jkridner[m] wishes we had a good userbase to focus a project simply on the issue tracker. Mar 20 17:15:03 do i have send a working prototype for the bi-directional bus project Mar 20 17:16:05 pranav_kumar[m]: The expectation is to have a complete working project with hardware assembly directions and working software at the end. Mar 20 17:16:42 pranav_kumar[m]: Showing a schematic with an assembly diagram using a tool like Fritzing would do for the hardware portion. Mar 20 17:17:22 pranav_kumar[m]: Please keep in mind that this is primarily a software project, so the hardware is assumed to be only about 20% of the effort. Mar 20 17:18:41 yes i can deliver that as i have some working experience harware programing and protocol part so if you have some resources that will be helpful for me regarding leaning kerenel part then that will be very helpful Mar 20 17:19:29 jkridner : sure I'll research more into the approach and report my progress to to you. Mar 20 17:20:54 pranav_kumar[m]: Sample kernel driver using the PRU assembly: https://github.com/abhishek-kakkar/BeagleLogic/blob/master/kernel/beaglelogic.c Mar 20 17:21:19 pranav_kumar[m]: Sample PRU firmware code: https://github.com/abhishek-kakkar/BeagleLogic/tree/master/firmware Mar 20 17:21:50 pranav_kumar[m]: Just look through the BeagleLogic documentation to get some ideas: https://github.com/abhishek-kakkar/BeagleLogic/wiki Mar 20 17:22:39 thanks for the resources i will look into it Mar 20 17:27:42 hi jkridner Mar 20 17:28:06 have you heard from anyone regarding the stepwise project ? Mar 20 17:28:07 hi pac23 ! Mar 20 17:28:15 can i just make the project of visualizing signal getting out of the swift register that is connected through any gpio for now Mar 20 17:28:28 pac23 not since we chatted last. Mar 20 17:28:35 oh,okay Mar 20 17:28:39 maybe there are some messages on the group. Mar 20 17:28:43 and submit status on that Mar 20 17:28:58 for now Mar 20 17:29:29 pranav_kumar[m]: When putting together your proposal, you should pick out a set of GPIOs that you will target for the project. If we can change that to be more generic, then great. Mar 20 17:30:17 i haven't seen any Mar 20 17:30:35 ok i will see for it now Mar 20 17:30:43 pranav_kumar[m]: Since we should be designating the GPIOs to use in a device tree fragment, having flexibility in the GPIOs you use should only impact the PRU firmware complexity (if you end up using the PRU). Mar 20 17:31:37 pranav_kumar[m]: Remember: 1. Get the hardware working, 2. Get the hardware talking from Linux userspace, 3. Get the hardware talking to a kernel driver. Mar 20 17:31:54 i was just asking for making progess in that direction will be good or not Mar 20 17:32:11 i have pocket beagle with me Mar 20 17:33:19 pranav_kumar[m]: Whatever you have to demonstrate with your proposal is fine. We may change direction later, though. Mar 20 17:33:52 hendersa: thanks Mar 20 17:34:09 for the suggestion Mar 20 17:35:53 vaishnav98_: I looked at your repo https://github.com/vaishnav98/pxt-beaglebone seems interesting to me to contribute to. Can you please quickly summarise for me what you've worked on and what are you currently working on? Mar 20 17:48:56 ravikp7 : Hi glad to see your interest in the project:) I started the project from the makecode maker project (https://github.com/Microsoft/pxt-maker) converted it to a simulator only target (previously it was simulate + compile) then removed the common-packages dependency , changed the board definitions to beaglebone boards(currently supports bbb,bbg,pb), then for interacting with the board I took help of : Mar 20 17:48:57 http://beagleboard.org/static/bonescript.js added setTargetaddress() calls in the built simulator.js and corresponding bonescript functions as callback, when a block is activated in the simulator, corresponding functions in simulator.js are invoked (this can be found from the shim notations in the libs directory sources) thus making the system interact with the board in sync with the simulator. I would like to Mar 20 17:48:58 change the implementation of making the bonescript calls from the common-sim.js which is a built file and find a better alternative. looking forward to your suggestions :) Mar 20 17:53:33 I hope my description is clear to you.. I am currently working on bringing in Techlab Cape support to the simulator and has made the board definitions (pins,LEDs,buzzer..) , is working on bringing in simulator only support for the board. I am reusing the libraries from maker makecode for bringing in Techlab support. Mar 20 17:58:58 vaishnav98_: thanks for the info. I'll look into the pxt-maker and then your repo to understand the whole thing, then only I'll be able to give any suggestions :) Mar 20 17:59:07 @pac23 you here? Mar 20 18:00:31 ravikp7: Thank you :) Mar 20 18:02:48 @freenode_pac23:matrix.org: you here? Mar 20 18:03:46 vaishnav98_: I see a lot of other boards at https://maker.makecode.com/#editor which I guess is built from the pxt-maker repo, are you planning to add BB support there? Mar 20 18:16:02 ravikp7 : initially I was planning to add BB support to makecode maker but after having a look at https://maker.makecode.com/boards/add-a-new-board , I felt that it was not directly possible to introduce BB support there that's why I forked the project and implemented a bonescript based approach Mar 20 18:19:01 vaishnav98_: since pxt-maker is still in beta, and they are constantly improving it, I doubt that we'll be able to cover those improvements in the fork Mar 20 18:20:37 vaishnav98_: did you try asking the maintainers of pxt-maker if they can help in getting BB integrated there, I think that'd be better approach for future improvements and maintainence Mar 20 18:23:00 Also, since you've got things working with the fork, it'll help them in better guiding you how to approach the integration there :) Mar 20 18:26:28 ravikp7: I haven't yet contacted the maintainers of pxt-maker regarding adding BB support , sure I'll contact the pxt-maker developers soon regarding adding BB support directly to pxt-maker. :) Mar 20 18:27:53 vaishnav98_: great! I'll also try to look into it, and keep me updated on this :) Mar 20 18:28:51 try having the conversation there by opening an issue on their repo Mar 20 18:32:45 ravikp7 : Sure :) I'll open an issue at their repo and keep you updated regarding my progress Mar 21 02:42:10 @zeek **** ENDING LOGGING AT Thu Mar 21 02:59:57 2019