Fred's firmware development diary

[Fred]

http://builds.freeems.org/openlogviewer/bins/ < about box info is now awesome, AND, RPM packaging works! It's more basic than Debian, but I'll fix that with time.

[Fred]

[Fred]

And while I was (every so briefly) asleep, someone's been busy making the rest of us look bad:



I should be ashamed of myself. But I'm too busy being very happy :-p

Kinda reminds me of my little friend:



Both have their place, and I'm looking forward to trying to integrate them as part of the release process, somehow.

Fred.

[Fred]

Just an FYI for anyone using eclipse Juno, if you're on SR1, you need to read this and install the optimisations patch. It makes a world of difference!

http://wiki.eclipse.org/Platform_UI/Jun ... estigation

Fred.

[Fred]

I've been working hard on docs and website stuff today. Hopefully I can get that completed tomorrow morning, and do some coding in the evening. Fingers crossed. 2:35am, time to sleep.

[Fred]

Docs are coming along nicely, nearly done. Meanwhile...

Eric found some of my crappy code via cross compiled unit testing! And I proved that it doesn't have any practical effect via over the wire unit testing.

I was more worried about cases that work cross compiled, but not on the device (due to toolchain issues), however it appears both directions are possible due to tool and device silicone implementation decisions.

Fred.

[Fred]

OTW tests updated to be useful:



They all used the same values before; now there is below, on, int, int, on, above.

Fred.

[Fred]

I've been doing some work on converting to mapped basic types:



The "_t" variety are very much not welcome, not at all. For an anti-thesis on how to write code, go here: http://www.freertos.org/FreeRTOS-Coding ... Guide.html

I feel sick.

Obviously it would be better if C had standards that made some sense, but it doesn't, and never will, so typedefs are it.

This will allow the PC-side unit tests to work adequately accurately, unlike without this change where long is 32 for us and 64 for them.

Fred.

[Fred]

The "_t" variety are very much not welcome, not at all. For an anti-thesis on how to write code, go here: http://www.freertos.org/FreeRTOS-Coding ... Guide.html

I feel sick.

Someone PMed me, despite my sig, about justifying the above, and some other things, to be discussed via skype soon. In contrast to that, the same person who linked me the above page, JohnTramp, also linked me this article, which is much more along the lines of my style:

http://kotaku.com/5975610/the-exception ... ource-code

I'll do a proper style guide at some point, and provide an eclipse formatter to help the lazy and stupid.

BTW, I don't necessarily advocate trying to code neat all of the time (although that IS what I (try to) do), rather you want to get it working any way you can, then tidy up afterward. As long as it's clean before I get to see it, no worries.

Fred.

[Fred]

I try to make sure I respond quickly to urgent requests for firmware fixes. Overnight, I failed. I'm deeply sorry. http://git.io/M0Rz2g