|
Embedded Systems
|
|
Written by Cliff Brake
|
|
Monday, 15 December 2008 |
|
One of the first things I do when designing a system based on a processor module is create a spreadsheet listing all the connector I/O. This is the easiest way I've found to make sure nothing gets missed. My first pass at a I/O spreadsheet for the Gumstix Overo is available at: https://dev.bec-systems.com/redmine/bec/wiki/omap3
| | |
|
Linux (embedded)
|
|
Written by Cliff Brake
|
|
Friday, 12 December 2008 |
|
This article presents a very nice overview of options to disable ssh host key checking. When working with embedded systems where you are constantly reloading the rootfs, it is really annoying to have to edit your ~/.ssh/known_hosts every time you update the rootfs on the target device. The solution is to simply disable host key checking for your local subnet by adding something like the following to the beginning of /etc/ssh/ssh_config: Host 192.168.1.*
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null Anything not on the 192.168.1.* subnet is still checked.
| | |
|
Last Updated ( Monday, 15 December 2008 )
|
|
Linux (embedded)
|
|
Written by Cliff Brake
|
|
Tuesday, 02 December 2008 |
|
How does one implement support for printing in embedded systems? I recently had the opportunity to add printing support to an embedded Linux system. The device is an industrial touch screen powered by a Compulab cm-x270 module (PXA270 CPU), and runs a GTK+ application. The customer is implementing a device calibration system where customers bring their equipment in to get calibrated, and the system prints out a report on a local printer. This article describes how components of Hewlett Packard's HPLIP solution along with Cairo can be used to implement printer support in a non-desktop Linux system. | | |
|
Last Updated ( Friday, 12 December 2008 )
|
|
Read more...
|
|
General
|
|
Written by Cliff Brake
|
|
Wednesday, 19 November 2008 |
|
Running a small business has a special set of challenges, and if you are not careful, the overhead can quickly consume you. This article is a list of things that I use in my business that work well for me, and help me to be efficient when there is so much to do ... Entire article at: http://bec-systems.com/web/content/view/101/9/ | | |
|
Last Updated ( Friday, 28 November 2008 )
|
|
Read more...
|
|
|
Linux (embedded)
|
|
Written by Cliff Brake
|
|
Wednesday, 22 October 2008 |
|
Recently the OpenEmbedded project has switched to the Git version control system. This is good news for many reasons. The obvious reasons are Git is faster than Monotone, handles branching better, has lots of nice features, larger user base, etc. Monotone has served us well, but as new tools become available, it is time to change. For those of us helping customers use OE for embedded projects, Git will make using OE much easier. Companies want to be able to track OE with minimal effort and typically maintain a few minor tweaks to OE. As most Embedded Linux projects now implement Git infrastructure for kernel development, the OE source tree can be maintained using the same infrastructure. Branching is very natural in Git, so it is fairly easy to create a OE "topic branch" and periodically merge with upstream changes as needed. The ability for easy repo hosting and branching allows OE users to lock down a version of OE for periods of project development, and still maintain a connection to the upstream OE repository for easily updating to new versions, or cherrypicking changes. So a big thank you to all who helped make this change happen. | | |
|
|
Linux (embedded)
|
|
Written by Cliff Brake
|
|
Tuesday, 26 August 2008 |
|
One thing you learn after using git for awhile is you get used to trying random things, and it will often just work. For example, if I want to know the differences between Linus's kernel tree, and the Wolfson dev branch for a particular directory: cbrake@happy:/build/linux-2.6$ git diff --stat origin/master..wolfson/dev sound/soc/codecs
sound/soc/codecs/Kconfig | 125 +++
sound/soc/codecs/Makefile | 34 +
sound/soc/codecs/ad1939.c | 690 +++++++++++++++
sound/soc/codecs/ad1939.h | 70 ++
sound/soc/codecs/ad1980.c | 309 +++++++
sound/soc/codecs/ad1980.h | 23 +
sound/soc/codecs/cs4251x.c | 771 +++++++++++++++++ Another way to get similar information is: git log origin/master..wolfson/dev sound/soc/codecs
If I'm working on a topic branch, and I want to see a summary of all the changes in my Topic branch: git log --stat origin/master..origin/my_topic_branch > my_topic_branch_changelog.txt One of the neat things about git branches is you don't have to be on a branch to interact with it. You can diff, log, and checkout from branches other than the one you are currently in, and it is all very fast. For instance, if I want to grab the latest copy of a file in the Wolfson dev branch, I can do something like: git log checkout wolfson/dev sound/soc/codecs/wm9713.c Not that this is a very good idea, but just to illustrate a point. Git branches are amazing and make development work so much less tedious.
| | |
|
Last Updated ( Tuesday, 26 August 2008 )
|
|
|
Linux (embedded)
|
|
Written by Cliff Brake
|
|
Friday, 22 August 2008 |
The Linux input layer has made a lot of progress in recent years. When writing a new input driver (such as keyboard, trackball, etc), it is useful to be able to monitor input events using a test application. This article describes two ways to accomplish this using kernel input debugging, and the evtest utility.
| | |
|
Last Updated ( Tuesday, 26 August 2008 )
|
|
Read more...
|
|
|
|
<< Start < Prev 1 2 3 4 Next > End >>
|
| Results 1 - 17 of 63 |
Blog 
