Topics created by Angus Ryan

i have the same err message. Also when i used dmesg i saw a lot of "warp core" logo and so on, (up to me it's the wifi driver restarting but not sure) , closely linked to a wifi hang and ssh link cut. i followed what is said here https://community.onion.io/topic/3561/error-cntlenqueueforrecv-blockack-request-frame-length-size-44-incorrect/6 It did ok until "fsck.fat /dev/mmcblk0p1" that fail because there is no "mmcblk0p1" file. But up to now no more "warp core" message nor ssh link loss. But i stil have some "ERROR!!! CntlEnqueueForRecv: BlockAck Request frame length size = 44 incorrect" message sometimes. i noticed i have this: br-wlan: port 1(ra0) entered disabled state due to...? EDIT> finally i used factory revert and re installed all my stuff. Now it's clean. No restart of wifi nor SSH cut since yesterday.

@Angus-Ryan it looks like you are in the home directory of root, if so try, cd / , that should put you in the system root directory.

@György-Farkas THANKYOU! Yes it does, I have no idea why, but setting those 3 as inputs then outputs makes it function perfectly.

@Angus-Ryan Did you solve your problem? I had something similar with the Dock 2 and a 3.5" TFT display. The problem was a conflict between I2C communication between the omega and the Dock's AVR chip with uses pins A4 and A5. But the pin corresponding to A4 resets the TFT display, So I cut this pin on the display and wired it to the Tx pin on the Dock 2, to do a hard reset when needed, but not during I2C transfers. The other added wire in the picture enables GPIO11 to receive data from the Arduino, but that is unrelated to the flakey operation I had before cutting the reset pin on the display. Hope that's helpful.

@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.

@Angus-Ryan In that case, try Firmware Flashing from USB Storage.

@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.

For low-cost, simple resistive touchscreen, Adafruit has this https://www.adafruit.com/product/1571 as dedicated resistive/analog to I2C/SPI conversion/reader (STMPE610 chip)

A bit of progress: I have created a patch that can be applied to the openwrt 18.06.2 tree which makes fbtft and all fb_xxx chip drivers available in make menuconfig, under Kernel Modules -> Video Support -> kmod-fbtft-support. The main patch that adds these options is this one. To make sure the build does not try to create a VGA console, I also added another small patch. Finally, if you do this on a fresh OpenWrt 18.06 tree (and not on the onion fork which already contains mt7688 SPI fixes), you also need: this one for making MT7688 hardware SPI work at least in pseudo-fullduplex (real full duplex is broken in MT7688 hardware) and to allow SPI transfers >16bytes. and this one is not technically needed but nice to have because it fixes the bogus error message at startup regarding SPI and DT. With these patches in place, you can select fbtft and a suitable display driver in menuconfig (I use fb_ssd1306 with a tiny 128x64 OLED for now, because that's the only display I have right now, the bigger color LCDs I ordered haven't arrived yet). Then build the firmware and install. fbtft and all dependencies are autoloaded at startup, but the actual display must be instantiated as follows: # load the chip driver insmod fb_ssd1306 # parametrize it via the `fbtft_device` helper module insmod fbtft_device custom name=fb_ssd1306 busnum=0 cs=1 speed=16000000 mode=0 fps=50 gpios=reset:0,dc:1 width=128 height=64 verbose=3 After that, the linux framebuffer console automatically kicks in and the display shows a blinking cursor clear >/dev/tty1 echo "Hello World!" >/dev/tty1 echo "Hello Omega!" >/dev/tty1 echo "Hello OLED!" >/dev/tty1 # connect a USB keyboard and have a supertiny console: login -f root </dev/tty >/dev/tty1 2>&1 This type of display with so-called 4-wire SPI needs some extra signals (dc, reset, see gpios part in the insmod fbtft_device command). The complete wiring of what you see in the photo is: GND = GND VCC = 3.3V D0 = SCK -> Omega SCK/GPIO7 D1 = MOSI -> Omega MOSI/GPIO8 (NOTE: Omega2 does not coldboot when this is connected to the SSD1306 OLED, probably need to add resistor into the line or remove pullup/down on the display itself) RES = Reset -> Omega GPIO0 DC = Data/Command -> Omega GPIO1 CS = Chip Select -> Omega CS1/GPIO6 Next step will be a sample app with LittlevGL but probably I'll wait with that until I have a color display, will be more fun then