My omega 2+ boots fine however every so often in the console I get this error message:
[ 1687.074870] ERROR!!! CntlEnqueueForRecv: BlockAck Request frame length size = 44 incorrect
It doesn't actually seem to affecting my omega however I'm curious why it keeps popping up as every few minutes of so it'll randomly print in my console.
Thanks
P.S photo example attached: 
When I first got my Omega2+ I could see all my system files in code editor.
Now there is nothing there, just an empty project folder, my omega still boots fine and runs so it's not like all the system files disappeared but for some reason I can't seem to find them at all.
If I type in the terminal
ls nothing appears, type pwd it says I'm in the /root directory, surely all my files can't have been deleted if the boot and wifi process works?
Any suggestions?
@György-Farkas THANKYOU! Yes it does, I have no idea why, but setting those 3 as inputs then outputs makes it function perfectly.
I have a touch screen that only works if I type the following commands into the terminal in the following order:
fast-gpio set-input 15
fast-gpio set-input 16
fast-gpio set-input 17
fast-gpio set-output 15
fast-gpio set-output 16
fast-gpio set-output 17
I think I have to set it as an input first as the docs mention something about how you should prior to setting it as an output and driving voltage to it.
The issue is everytime I unplug my omega or reset it, I have to go back to the terminal and type these commands to make it work, is there a way I can store these settings somewhere so when it boots I don't need to enter it via the terminal?
Thanks
I have an Onion Omega 2+, Arduino Dock 2 and a 2.8 TFT Touch Shield for Arduino Uno.
I tested the touch screen with my Arduino Uno and it works perfectly, using the example code from the Adafruit libraries to test the touch screen.
My problem is when I then upload the same example to my Omega (while it’s in the Arduino Dock) I can’t get the touch screen to work. At first the display works fine however the touch screen functionality doesn’t work at all.
After a bit of research I found if I set via terminal:
fast-gpio set-input 15
fast-gpio set-input 16
fast-gpio set-input 17
I could get the touch screen working partially. That is, if I touch the screen the button changes state (as expected) except suddenly after that it’s as if the screen it repeatedly being tapped, without myself physically touching it again the 3 different buttons across the screen changes state as if theyre being touched when they are not. So if I can work out why the screen thinks it’s being touched when its not after the first press it’d solve my problem!
Can anyone enlighten me on what would cause this, and if possible point me in the right direction!
Thanks
@György-Farkas it seems setting the inputs 'fast-gpio set-input 15' as well as 16 and 17 makes the touch screen work in the dock (while omega is plugged in), but causes the touch screen to think its repeatedly being tapped without actually tapping it. The first touch works, but then the screen acts as if its being touched everywhere. For example I have three buttons which when tapped change colour, what happens is when I tap one button it changes colour and then all of a sudden the other buttons start changing colours and flickering (as if i am tapping them when I am not). (without the omega plugged in touch screen doesnt respond).
WHEREAS in the Arduino Uno (not dock) touch screen works perfectly.
@György-Farkas kind of worked. If I touch it once, the whole screen keeps registering clicks everywhere continously. The project works on my arduino, one click turns a button on, again turns it off.
On the omega i touch the button and it turns on and then continously flickers on and off without it being touched? It's as if im spamming my finger tapping everywhere.
@György-Farkas please read update at top of page.
That is what it currently is displaying
This is what it's meant to display, which works when using my arduino uno.
@György-Farkas this is the example code I'm trying to run
Appreciate your help by the way!
@György-Farkas The shield works perfectly when plugged into the dock and the example 'graphic test' is flashed wirelessly to the omega. However when I flash the 'touch test' the touch screen seems to just be black and white strips of light (clearly stuffing up and struggling).
and yes I have v2.
@György-Farkas Also if the graphics work on the screen, however not the touch functionality wouldn't that mean that pins 13-9 arent the problem (even though the Omega uses 11-13) as the graphics are displaying fine, rather that pin 8's functionality is not working?
@György-Farkas set it via the terminal?
UPDATE: after changing the pins as written in the reply the touch screen works....partially. Confusingly the touch screen works ONLY if I
1. upload code to omega without touch screen in.
2. plug touch screen into arduino uno with new code
3. then plug back into omega with the new code running.
IT DOES NOT WORK if I have the touch shield in and I upload new code, the graphics change accordingly but I lose touch functionality.
ORIGINAL
I had a touch screen shield that works perfectly with my Arduino Uno. I wanted to repeat the same project using a Omega, however realised there were no Analog I/O pins.
I purchased the dock and am trying to get this touch screen working however the example library file supplied by the touch screen manufacturer doesn't seem to be working with the dock.
The example works perfectly with my Uno however not with the dock, the screen just has black and white lines across it.
I assume it has something to do with the analog pins as the non-touch related example where you print text and shapes works fine on the dock, just not the touch related example.
Any ideas why it wouldn't be working?
This is the Touch Screen
@Jon-Gordon glad (I think?) that you have faced the same issue as it makes me feel like it was shipped that way. I didn't realise they only have 2 week warranty? I'll chat with them, I think it may be the Arduino Dock though as it runs fine in the Expansion Dock just overheats in Arduino Dock.
@Douglas-Kryder ah alright, I'll have a look, but no other power supply attached but the Micro USB as per the documentation instructs.
@cas yeah I know what you mean hot, but this is burning components hot, I can smell the burning within 1 minute.
Quite frankly the reset button doesn't seem to be doing anything. I attempted it earlier, not sure if faulty button or the Omega is refusing commands
@cas I've attached what the serial printed during the boot session. Not sure what I'm looking for but all I know is the wifi never appears and the LED doesn't stop flashing 
This just printed below [ 80.988350] random: nonblocking pool is initialized
@cas yeah I was following the documentation 
Now I think its damaged my omega entirely, I just tried to use the expansion dock instead and now the LED wont stop flashing and the wifi isnt appearing like it used to.
