Tag: system

lzoDSO – prototype demo

Posted by May 15, 2013

Demonstrates the (currently limited) capabilities of the lazlo labs digital storage oscilloscope (lzoDSO) prototype. The test probe of the scope is connected to a timer circuit in mono-stable astable configuration so that it produces a more or less defined test signal. There is also a test signal source inside the scope that we need integrate into the firmare to get it working.

Uses an ATmega644 at 16 MHz and the internal 10-bit A/D converter (only using 8 bits).

See the lzoDSO project page for more at labs.lazlo.de/trac/lzodso.

lzoDSO – hardware prototype

Posted by April 11, 2013

IMG_0257_modified-small
lzoDSO hardware prototype

Recently I have been working on my oscilloscope project. Documenting ideas, digging out requirements and restructuring the whole projects documentation wiki. While doing so I realized that the page was totally confusing to new visitors since it does not say that there is no finished scope yet (even though there is a picture of one). What one can see on the pictures is actually a prototype. Until now we did not explicitly say so. This is NOT the final thing.

To address that issue we added a Status section to the start page of the wiki that clarifies the projects state.

Now the interesting part: We created a new page for the prototype which is linked on the wikis start page and moved existing files related to the components of the prototype from /trunk to /branches/prototype-a.

Next step will be to take the legacy firmware we have and adjusted it to make it run on the prototype hardware. When the firmware is ported (basically adjust pin mappings, enable/disable functionality) we will use is as the starting point to get the code incrementally refactored until we replaced everything with test-driven code.

lzoDSO – a DIY Oscilloscope

Posted by March 19, 2013

After quiet a while I have started to put my oscilloscope project online. Work is still in progress but I decided it won’t hurt to have online what has been done so far.

test-driven development for embedded systems


Found a nice article at embedded.com on how mocking can help build more robust and clear code. The article talks about development using C/C++ and the Unity unit testing framework which I have been using for quiet a while (thanks to the book “Test-Driven Development for Embedded C” by James Grenning).