I'm working in an embedded linux environment. I have a display setup with the linux framebuffer.
I can use the fbgrab to capture the contents of the framebuffer and store it in an image:
I can use the fbv utility to set images to my screen:
I can even write (raw) images directly to the framebuffer using dd:
dd if=./myimage.raw of=/dev/fb0
However, if I launch fbterm:
[root@buildroot ~]# fbterm
It just sits there, does not exit. That's probably normal, however, I don't see anything come up on the display - and dumping the framebuffer contents again using
fbgrab reveals nothing that looks like a terminal - it simply contains whatever it did before launching fbterm. In addition, no information is printed to the console.
Is this the expected behavior of fbterm when launching it directly from the console? Do I have to feed it more information or launch it in a different manner before I can view it on the display?
I've read many articles online about launching fbterm at startup - but I figured that I would need to get it to work at all before trying that?
In fact, I am not sure how to debug or troubleshoot the problem. I do not see any messages appear in the system logs when opening or closing fbterm. Any tips?