![]() So first problem was the compiler would not run on the old version of Raspbian on the Pi B. So compiling some code for for a beta version of LH will be no problem, right? So bought a 5" HDMI LCD with touchscreen and a Pi B (I already had another B). Only problem is I've never been a big Linux user and haven't touched it for at least 5 years. As you know, I decided to try upgrading to Lady Heather running on a Raspberry Pi. ladyheath 2>stracelog.txt followed by: grep '/dev/tty' -C20 stracelog.txt My starting point would be to run it via strace and see what error codes are being generated when it tries to open /dev/ttyXYZ. If this doesn't work: I would start debugging lady heather. This temporarily grants all users read & write permissions to all of your USB uarts (and all of your ttys, but if it's a single-user computer then you probably don't care). Already being read from by another program Robert763: are you running Cutecom as your own user or as root? Does it prompt you for a password at any point? What about Lady Heather? Temporary hack to try: sudo chmod a+rw /dev/tty*. (EDIT: actually I lie, stdin stdout stderr tend to have special numeric file descriptors of 0 1 2, but I'm not sure if this is enforced or not) Whenever people have problems accessing UART nodes in /dev/ my immediate suspicions are: 1. ![]() ![]() Indeed Linux doesn't special-case certain filesystem names like Windows and DOS do. Yes it will make a difference, the version without the leading slash will be completely wrong (it will be read as relative to the current directory). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |