Profile cover photo
Profile photo
OpenEmbedded
165 followers -
the build framework for embedded Linux
the build framework for embedded Linux

165 followers
About
OpenEmbedded's posts

Post has shared content

Post has shared content
I think my SSD that I make +OpenEmbedded and +Yocto Project builds on has finally gave in and is pretty much dead. I've been having weird issues with it in the past several days, and I believed I repaired it last time around when I thought it was a software glitch. But apparently it is a hardware problem and I need to replace it completely... And as usual, it always happens at the worst possible time - it's not the data I'w worried about, it's all the time I've lost wrangling with it...

Post has shared content

Post has shared content
Easier ssh to constantly-rebuilt images

I have been using Yocto a lot lately and am constantly tweaking and rebuilding images. Yocto includes the really nifty 'runqemu' utility (that lets you quickly test an image using 'qemu') which does all the work of configuring (for example) your networking so you can 'ssh' into your image.

I prefer to 'ssh' into my image rather than go through the qemu window since my shell doesn't blank (yes, I realize it could be fixed with '$ setterm -blank 0'), I can set my shell to be whatever size I want, my mouse isn't captured by my shell window, and I can have a couple shells into the same image if I want to look at a couple things at the same time.

Currently my workflow involves something like this:
- tweak yocto configuration
- $ bitbake <image>
- $ ssh-keygen -R 192.168.7.2 -f /home/trevor/.ssh/known_hosts
- $ ssh root@192.168.7.2

The 'ssk-keygen -R' line is required otherwise ssh will complain about different keys (or something like that) and not allow me to 'ssh' into my image. The problem is that each time I create a new image, the first time that image boots it generates new, unique, ssh keys.

Since (and only because) I know the image to which I am connecting and I realize there's no security risk, I have found that adding the following lines to my ~/.ssh/config is very helpful:

Host yimage
    HostName 192.168.7.2
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null
    User root
    LogLevel QUIET

With this change I can now simply:
$ ssh yimage

and I have an easier name to type/remember, I don't not need to specify a user, and I can skip the 'ssh-keygen -R' step every cycle.

Post has shared content

Post has shared content
Be the first to get the new $199 Sitara AM335x Starter Kit! Making it even easier to develop on the Sitara AM335x ARM Cortex-A8 processor, TI has introduced a new low-cost development platform which gives quick access to key features and peripherals: http://bit.ly/QFEoE1
PhotoPhotoPhotoPhoto
4 Photos - View album

Post has shared content

Post has shared content
Blogger starting a license plate reading project using a BeagleBoard-xM

Post has shared content

Post has shared content
Wait while more posts are being loaded