Welcome, Guest

Recent Posts

Pages: 1 ... 8 9 [10]
ESP8266 / Re: mod wifi esp8266 dev board
« Last post by Lurch on March 02, 2018, 03:36:39 PM »
The modules are loaded by Olimex with one of their demo programs. It doesn't run the AT stack you want. If you want to work with AT commands, you will have to load the AT image. There are documents and images at Espressif on GitHub to do this.
ESP8266 / mod wifi esp8266 dev board
« Last post by Prasanth on March 02, 2018, 08:56:08 AM »
Dear all,
    I'm a beginner for using ESP8266 wifi module. while connecting this wifi module with usb serial converter to PC i can't able to communicate with it like when i send "AT" to it i can't get anything back from wifi. Its crystal frequency is 26Mhz and default flash mode.
    When swapping the tx and rx lines then getting the below information from that.
 ets Jan  8 2013,rst cause:1, boot mode:(3,6)

 ets Jan  8 2013,rst cause:1, boot mode:(3,6)

load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
  SPI Speed      : 40MHz
  SPI Mode       : QIO
  SPI Flash Size & Map: 16Mbit(512KB+512KB)
jump to run user1 @ 1000

rf cal sector: 507
rf[112] : 00
rf[113] : 00
rf[114] : 01

SDK ver: 2.0.0(656edbf) compiled @ Jul 19 2016 17:58:40
phy ver: 1055, pp ver: 10.2


I don't now what changes i want to made. Please assist me to work with this module.

Thanks & Regards,
TERES DIY Laptop / Re: going mainline
« Last post by lambda on February 28, 2018, 01:43:52 PM »
JFTR: User dddddd from the olimex irc channel (user deesix here on the forum) has figured out how to make a debug cable for the theres: (Log is here: https://www.olimex.com/irc?date=2018-01-20)

We are now working together to get mainline kernels booting.

A13 / Re: Compilling qt-everywhere fails
« Last post by Melange on February 27, 2018, 08:30:40 PM »
/tmp/ccMg97nX.s:18059: Error: selected processor does not support `swp r3,r2,[r1]' in Thumb mode

This means that your selected soc architecture (-mcpu=cortex-a8) is not supported, you'll need to try a more recent version of Qt.

I recommend you try Qt 5.9.4, I used it recently with success in this cross-build script for the Raspberry Pi:


But note that it's for the Pi, I do not believe it works for the A13 without serious modifications. Also there might be a RAM problem with Qt, the A13 has only 512M.
A20 / Re: g_hid module results in kernel crash if used with Windows
« Last post by aljumail.mustafa on February 26, 2018, 10:46:08 AM »
Pleas did you manage to solve this problem !
A13 / Compilling qt-everywhere fails
« Last post by zdenekrejci on February 25, 2018, 07:41:23 PM »
Hi to all. I am trying to get working cross platform programming for A13 ARM from olimex.
I have searched already here but did not find a way to make it work.

I have installed Qt Creator 3.5.1 and also installed cross compillers arm-linux-gnueabi and arm-linux-gnueabihf.
Then i did try one million times to compile qt-everywhere-opensource ,,,


with ./configure -embedded arm -prefix /usr/local/qt -little-endian -no-qt3support -no-cups -no-largefile -optimized-qmake -no-openssl -xplatform qws/linux-arm-g++ -nomake tools -nomake examples -no-webkit -opensource -confirm-license

but always get output from make command

arm-linux-gnueabihf-g++ -mcpu=cortex-a8 -mtune=cortex-a8 -O0 -mfpu=neon -lrt -c -fno-exceptions -D_REENTRANT -DQT_SHARED -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DELF_INTERPRETER=\"/lib64/ld-linux-x86-64.so.2\" -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -I../../mkspecs/qws/linux-arm-g++ -I. -I../../include -I../../include/QtCore -I.rcc/release-shared-emb-arm -Iglobal -I../3rdparty/zlib -I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4 -I.moc/release-shared-emb-arm -o .obj/release-shared-emb-arm/moc_qnamespace.o .moc/release-shared-emb-arm/moc_qnamespace.cpp
arm-linux-gnueabihf-g++ -mcpu=cortex-a8 -mtune=cortex-a8 -O0 -mfpu=neon -lrt -c -fno-exceptions -D_REENTRANT -DQT_SHARED -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DELF_INTERPRETER=\"/lib64/ld-linux-x86-64.so.2\" -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -I../../mkspecs/qws/linux-arm-g++ -I. -I../../include -I../../include/QtCore -I.rcc/release-shared-emb-arm -Iglobal -I../3rdparty/zlib -I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4 -I.moc/release-shared-emb-arm -o .obj/release-shared-emb-arm/moc_qthread.o .moc/release-shared-emb-arm/moc_qthread.cpp
/tmp/ccMg97nX.s: Assembler messages:
/tmp/ccMg97nX.s:18059: Error: selected processor does not support `swp r3,r2,[r1]' in Thumb mode
Makefile:17777: recipe for target '.obj/release-shared-emb-arm/qobject.o' failed
make[1]: *** [.obj/release-shared-emb-arm/qobject.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/root/qt-everywhere-opensource-src-4.6.2/src/corelib'

and also was trying to changing and combining commands but no luck. Iam not linux professional but just trying by manuals and tutorials.

can someone help? please  :)
RT5350F / Re: Clean shutdown of RT5350F?
« Last post by JohnS on February 25, 2018, 06:57:59 PM »
That's very odd - I've never been unable to interrupt uboot (it's why it has the menu).

Problem with your lead/etc?

As to why it doesn't halt... read (*) the code?  It's why source is useful :)

(*) and I suppose fix

RT5350F / Re: Clean shutdown of RT5350F?
« Last post by shish on February 24, 2018, 10:23:48 PM »
Thanks John! Unfortunately, it seems that pressing space (or any other character) does nothing to stop the (re)boot?
RT5350F / Re: Clean shutdown of RT5350F?
« Last post by JohnS on February 24, 2018, 07:21:07 PM »
At the least you can maybe interrupt U-Boot (hit a char such as space) and then power off.

RT5350F / Clean shutdown of RT5350F?
« Last post by shish on February 24, 2018, 06:43:48 PM »

I recently bought the RT5350F-OLinuXino-EVB and just started testing it. I came with OpenWrt Linux-3.18.19 pre-installed. (I have not altered it in any way.)

However, when I try to shut it off cleanly via the serial terminal using 'halt' or 'poweroff', it always reboots. No matter what arguments I use.

Anybody who knows how to do this? There is a little pause between the "System halted" message and the reboot, but to pull the power at that point seems a little "dangerous".

Log from using the 'halt' command:
Code: [Select]
root@OpenWrt:/# halt
root@OpenWrt:/# [  271.600000] br-lan: port 1(eth0.1) entered disabled state
[  271.620000] device eth0.1 left promiscuous mode
[  271.630000] br-lan: port 1(eth0.1) entered disabled state
[  271.650000] IPv6: ADDRCONF(NETDTV_UP): eth0.1: link is not ready
[  272.090000] device eth0 left promiscuous mode
[  275.990000] reboot: System halted

U-Boot 1.1.3 (Apr 20 2005 - 13:25:55)

Board: RT5350F-OLinuXino DRAM:  32 MB

relocate_code Pointer at: 81fb4000

Software System Reset Occurred

spi_wait_nsec: 42
spi device id: 1c 30 17 1c 30 (30171c30)
find flash: EN25Q64
raspi_read: from:30000 len:1000

.*** Warning - bad CRC, using default environment

RT5350F-OLinuXino UBoot Version:
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
Flash component: SPI Flash
Date:Apr 20 2015  Time:13:25:55

icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

 ##### The CPU freq = 360 MHZ ####
 estimate memory size =32 Mbytes

Please choose the operation:

   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.

3: System Boot system code via Flash.

## Booting image at bc050000 ...

raspi_read: from:50000 len:40

   Image Name:   MIPS OpenWrt Linux-3.18.19
   Created:      2015-08-24   6:49:42 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1084701 Bytes =  1 MB
   Load Address: 80000000
   Entry Point:  80000000

raspi_read: from:50040 len:108d1d

.................   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

No initrd
## Transferring control to Linux (at address 80000000) ...
## Giving linux memsizz in MB, 32

Starting kernel ...

[    0.000000] Linux version 3.18.19 (stefan@debian) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r45456) ) #7 Mon Aug 24 09:48:45 EEST 2015
[    0.000000] SoC Type: Ralink RT5350 id:1 rev:3
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001964c (MIPS 24KEc)
[    0.000000] MIPS: machine is RT5350F-OLINUXINO
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x01ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
Pages: 1 ... 8 9 [10]