@ccs-hello thanks ccs. I measured the current this morning as 180mA and the board remained cool until it connected to the wifi. Seems to match the findings in the link you posted.
I have 4 Omega2+ and all behave the same.
I've just helped one of my friends to install a part of 'iTunes' on a DELL N5010 notebook (Windows 10 Home x64).
We downloaded the 'iTunes64Setup.exe' installer - unpacked it with Total Commander 7.55a - and installed the 'Bonjour64.msi' file successfully.
PuTTY - Connection type: SSH - Host Name firstname.lastname@example.org or root@Omega-XXXX.local (not case sensitive) - it's an Omega2+ FW 0.2.0 b194.
(I rarely use MS Windows - it seems Bonjour64 works perfectly.)
@Maximilian-Gerhardt yes you are right, the "fps" is limited with the spi bus speed, and that is at max 100, in the memory it works same speed with the cpu's that one is the 387 for 150Kbytes 16bit embedded bmp. It can't be showing but it is there. In the future if there is much faster spi speed then we can use these rates.
fill screen function, after first line just memcpy()
fillScreen ( struct fb_info *fb_info, unsigned int color )
//~ for ( int i=0; i <= fb_info -> screensize; i++ )
//~ putPixelDirectToLocation( fb_info, i, color );
for ( int i=0; i < fb_info -> var.xres; i++ )
putPixel( fb_info, i, 0, color );
for ( int i=1; i < fb_info -> var.yres; i++ )
memcpy( fb_info -> ptr + ( fb_info -> fix.line_length * i ),
fb_info -> ptr,
( fb_info -> var.xres * ( fb_info -> var.bits_per_pixel / 8 ) ) );
//~ for ( int i = 0; i < fb_info -> var.yres; i++)
//~ drawHorizontalLine ( fb_info, 0, i, (unsigned int)fb_info -> var.xres, color );
this is the embedded bmp push code
for (int i=0; i<1000; i++)
/* memcpy() bmp show */
memcpy( fb_info.ptr, &logo_bmp, logo_bmp_len );
and this is the simple test code
date nanoseconds enabled from menuconfig "%N" and bc installed
echo -e "started\t"$first
#for i in `seq $count`; do ./fb-test; done;
echo -e "ended\t"$last
echo $(echo "$count/($last-$first)" | bc)" fps"
Last one the built in debug, i think it has some kind of bug or it is not an optimized code ( ~3000Kb * ~5 = ~15.000 Kb ) i think this is the equation:
when you use debug=$((1<<5)) it shows, (~ 3000Kb) * ( ~5 )
echo -e $((1<<5)) > /sys/class/graphics/fb0/debug
then, for cancle
echo -e 0 > /sys/class/graphics/fb0/debug
I wrote something similar Adafruit_GFX, it capable of draw lines, draw triangles, draw squares, draw circles, push 16bit bmps ... but the code has a lots of issue, there is a long way to go for stable. When i clean things up I will push the code to gitlab.
if you compile modules builtin, below script activates the display in 10 seconds or so when power up the omega2, i am trying to activate with uboot but no luck for now.
display init script init.d
rotate Change the display direction to one of the [0 1 2 3] values 0:0, 1:90, 2:180, 3:270
insmod fbtft_device custom name="fb_ili9341" busnum=32766 cs=1 speed=96666000 mode=3 fps=100 txbuflen=3145728 buswidth=8 bgr=1 gpios=reset:2,dc:3 width=240 height=320 verbose=0 rotate=$ROTATE_ANGLE debug=0
if [ ! -z $1 ]; then
if [ $1 -eq 0 ]; then
echo "$1 0"
elif [ $1 -eq 1 ]; then
echo "$1 90"
elif [ $1 -eq 2 ]; then
echo "$1 180"
elif [ $1 -eq 3 ]; then
echo "$1 270"
echo "$1 270"
I also ran into this problem with a remote connection to my Omega. You should write not "local", but the IP address of your Omega in the network.
For example, SSH root@omega-ABCD.192.168.3.1
Same issue as most people here with the ugpio/ugpio.h error. You a major problem in continuity with your documentation and is seems like it should be an easy fix. As others have expressed, this is very irritating. Please fix
I have figured that Onion will not talk to itself, no idea why. However it is not able to read anything from the /dev/ttyS1 even tho the attached Arduino sends text to the serial port which I can see with screen command. When I loop both the read and both the sending, I can see the sent string from arduino on the onion "screen" command, although with half the rate Im sending it, but still the Onion is unable to see it. I am slowly going mad above this, please help!
from the output of opkg --help you can see this information:
Use <dest_name> as the the root directory for package installation, removal, upgrading. <dest_name> should be a defined dest name from the configuration file, (but can also be a directory name in a pinch).
So, I edited my /etc/opkg.conf adding a dest name called opkg_test for /tmp folder; My etc/opkg.conf now is:
dest root /
dest ram /tmp
dest opkg_test /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay
option check_signature 1
Then, I've copied a package (transmission-web_2.92+git-4_mipsel_24kc.ipk) in /tmp/ to make a test, and launched opkg this way: