LabConnections.jl issueshttps://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues2019-05-02T10:48:13Zhttps://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/11To-do list from handover meeting2019-05-02T10:48:13ZMarcus Thelander Andrénmarcus.thelander_andren@control.lth.seTo-do list from handover meetingThe following issues were brought up during the handover meeting, which should be fixed:
* [ ] Make sure that the server on the BeagleBone is starting up automatically and is working as intended.
* [ ] Debug the precompile function cal...The following issues were brought up during the handover meeting, which should be fixed:
* [ ] Make sure that the server on the BeagleBone is starting up automatically and is working as intended.
* [ ] Debug the precompile function call
* [ ] Remove time-stamps in communication
* [ ] Check behaviour of applying a single device on multiple streams.https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/10Overview of LabDev2019-05-01T22:37:35ZMattias FältOverview of LabDevJust putting this here, feel free to edit and update. We should probably put this in one of the packages.
![LabInterface](/uploads/d34e8848ee4eba19792311adad982b5b/LabInterface.png)
To edit:
https://www.draw.io/?lightbox=1&highlight=0...Just putting this here, feel free to edit and update. We should probably put this in one of the packages.
![LabInterface](/uploads/d34e8848ee4eba19792311adad982b5b/LabInterface.png)
To edit:
https://www.draw.io/?lightbox=1&highlight=0000ff&edit=_blank&layers=1&nav=1&title=LabInterface.drawio#Uhttps%3A%2F%2Fdrive.google.com%2Fuc%3Fid%3D1igGPYQooaRTjrya-drfUevllbRCzvPyx%26export%3Ddownloadhttps://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/9Device Tree Overlay for BB2018-12-11T14:21:50ZMarcus Thelander Andrénmarcus.thelander_andren@control.lth.seDevice Tree Overlay for BBHow to setup device tree overlay :
If this works (as root), everything is great:
```
cd /lib/firmware
echo cape-universaln > /sys/devices/bone_capemgr.*/slots
```
However, an old version of universaln has a conflict with the HDMI/audio p...How to setup device tree overlay :
If this works (as root), everything is great:
```
cd /lib/firmware
echo cape-universaln > /sys/devices/bone_capemgr.*/slots
```
However, an old version of universaln has a conflict with the HDMI/audio port P9.31
The updated version, should be included in this package as `cape-universallc-00A0.dts` can be used instead:
```
cp cape-universallc-00A0.dts /lib/firmware
cd /lib/firmware
dtc -O dtb -o cape-universallc-00A0.dtbo -b 0 -@ cape-universallc-00A0.dts
echo cape-universallc > /sys/devices/bone_capemgr.*/slots
```
where `cape-universallc` has the lines corresponding to P9.31 commented out.
To trace any erros, use `dmesg | less`.
To test if everything is expored coorectly, run (in julia, as root)
```julia
include("packages/LabConnections/test/BeagleBone/GPIO_test.jl")
```https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/8Doc-webpage: 404 Error2018-01-18T08:12:27ZMarcus Thelander Andrénmarcus.thelander_andren@control.lth.seDoc-webpage: 404 ErrorWhen following the link to the documentation you're currently greeted by a 404 error... Something wrong with the link?When following the link to the documentation you're currently greeted by a 404 error... Something wrong with the link?https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/7Tests annd pipeline2018-01-18T08:10:51ZMarcus GreiffTests annd pipelineThe pipeline seems to be broken as of the first device_rewrite branch commit. I have no idea how to fix it, and gitlab keeps giving an "error 500" when trying to re-initialize it. It might be due to recent updates to Gitlab itself, but I...The pipeline seems to be broken as of the first device_rewrite branch commit. I have no idea how to fix it, and gitlab keeps giving an "error 500" when trying to re-initialize it. It might be due to recent updates to Gitlab itself, but I do not know how to resolve it.
Otherwise, the GPIO/SysLED/PWM tests pass, both with and without the BB, and the device re-write branch has been merged with the master.https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/6Proposal for dealing with IOStreams on the BB2017-09-04T13:23:36ZMarcus GreiffProposal for dealing with IOStreams on the BBHere is an example of how we could use the open() close() of IOStreams on the BB, as we discussed two days back. The code is implemented in [config_library.jl](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/Beagle...Here is an example of how we could use the open() close() of IOStreams on the BB, as we discussed two days back. The code is implemented in [config_library.jl](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/BeagleBone/config/config_library.jl), and an example is given in [config_example.jl](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/BeagleBone/config/config_example.jl) where the system is set up in accordance with the YAML file [example_configuration.yml](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/BeagleBone/config/example_configuration.yml).
The general idea is documented in [config_example.jl](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/BeagleBone/config/config_example.jl), and if you approve of the concept, it is easily modified to accommodate the existing modules for IO functionality (see the setup files etc.). What do you think?https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/5Automatic documentation through travis2017-09-02T10:02:32ZMarcus GreiffAutomatic documentation through travisI have made a first attempt at creating an automatic documentation of the project. And the files build and may be viewed in the docs/build directory. It would be nice to have them compile and update automatically through Travis, and to h...I have made a first attempt at creating an automatic documentation of the project. And the files build and may be viewed in the docs/build directory. It would be nice to have them compile and update automatically through Travis, and to host the html files in order to have the accessible in the README.md. I have not yet had time to do so, and I believe Fredrik might know how.https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/4Pre-compilation of dependencies2017-10-06T02:36:51ZMarcus GreiffPre-compilation of dependenciesThere is an issue with running the precompile if the LabConnections package depends on other packages, such as YAML.
I have tried to make YAML pre-compile before LabCommunications by editing the [startup.jl](https://gitlab.control.lth.s...There is an issue with running the precompile if the LabConnections package depends on other packages, such as YAML.
I have tried to make YAML pre-compile before LabCommunications by editing the [startup.jl](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/BeagleBone/startup/startup.jl) and [precompile.jl](https://gitlab.control.lth.se/labdev/LabConnections.jl/blob/master/src/BeagleBone/precompile.jl) files, but so far no changes have been successful. The breaking changes have not been comited in order to have the code on gitlab passing the automatic testing.
YAML depends on "Codecs" and "Compat", and all three may be installed using Pkg.add("YAML"), and transferred to the BB using flash_BB.sh. If anyone has any ideas on how best to make the precompile work with YAML, then feel free to make changes or share ideas.https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/3Tag release after merging bufferandcomedi2017-08-29T11:02:47ZFredrik Bagge CarlsonTag release after merging bufferandcomediTo be used in labsTo be used in labsMattias FältMattias Fält2017-08-31https://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/2Visibility needs to be public to be used in labs2017-08-31T14:27:19ZFredrik Bagge CarlsonVisibility needs to be public to be used in labsFor this repository to be used in labs by students, the visibility needs to be public.
Any objections? @mattiasf @mgreiff @marcus @rootFor this repository to be used in labs by students, the visibility needs to be public.
Any objections? @mattiasf @mgreiff @marcus @rootAdministratorAdministratorhttps://gitlab.control.lth.se/labdev/LabConnections.jl/-/issues/1Todo-list2018-01-18T08:10:09ZMarcus Thelander Andrénmarcus.thelander_andren@control.lth.seTodo-listThings to do:
- [ ] Make an Adafruit-like BB interface using Julia.
- [x] System Leds
- [x] GPIO (done at BB side)
- [x] PWM
- [ ] Quadrature Encoder
- [x] SPI
- [x] Define two types of streams (one sporadic, another periodic)...Things to do:
- [ ] Make an Adafruit-like BB interface using Julia.
- [x] System Leds
- [x] GPIO (done at BB side)
- [x] PWM
- [ ] Quadrature Encoder
- [x] SPI
- [x] Define two types of streams (one sporadic, another periodic).
- [x] Implement output buffer
- [x] Allow return (working read calls)
- [x] Set up build server.
- [x] Automatic testing.
- [x] Automatic documentation.
- [x] Timestamps on sensor data at BB-side.
- [ ] Handshaking between host computer and BB.