Welcome, Guest

Recent Posts

Pages: [1] 2 3 ... 10
1
RK3188 / Re: Up to date guide to get an OS for a RK3188?!?!
« Last post by hzg_it on Today at 02:02:25 PM »
Hi LubOlimex,

thank you very much, the download link worked like a charm and the RK3188 is now running Debian 7! :)

Best,
hzg_it
2
ESP32 / Re: ESP32-GATEWAY wired ethernet not working
« Last post by LubOlimex on Today at 01:35:16 PM »
Thanks for the feedback. I've separated this post in a own post.

I am not sure what caused the fault in your first board, reset is unlikely reason. Resetting revision C ESP32-GATEWAY might temporarily bug the Ethernet, but after re-programming and standard power-up it should work fine. If it certainly seems like a hardware fault then it might have been caused by accidental short-circuit; static electricity, or potential difference between different sources of power attached at the same time to the board. Overall I recommend you to consider some sort of case for the board to prevent such issues from occurring in future. Also be careful when attaching different peripherals of the board.

Since you purchased new ESP32-GATEWAY boards, consider this:

The newer revisions of ESP32-GATEWAY have differences in the Ethernet design compared to older revisions. Major changes were introduced in revision D, we no longer use external quartz but like most other designs use the ESP32 clock. I recommend you to check the details here: https://github.com/OLIMEX/ESP32-GATEWAY/tree/master/HARDWARE

Updated software was published here: https://github.com/OLIMEX/ESP32-GATEWAY/tree/master/SOFTWARE/Newest-board-revisions

and also in the newest releases of the ESP32 for Arduino IDE package.
3
ESP32 / ESP32-GATEWAY wired ethernet not working
« Last post by hugo on Today at 11:25:57 AM »
Hi,

Sorry for breaking in to this conversation, but it seems that I also experience this exact same issue. There are however a few differences:
- I'm using an ESP32-GATEWAY board
- the board started to work fine. It just died last weekend while working on my project, but ethernet has worked perfectly well in the weeks before.

I bought 2 boards a few months ago (from Mouser) and I've received rev. C (if that makes any difference). I tried loading the ethernet example on the board I was working on, but noticed the same behaviour: dhcp server is offering an ip, but the board is not responding to the offer (it should respond with DHCPACK). After swapping the board for the other (still new and untouched), ethernet worked with the same example.

I tried swapping network and usb cables and tried my laptop instead of my desktop pc (for flashing), but I cannot get the first board to work again. When trying the second board, the same cables and code work perfectly well.

I (also) have to conclude that the hardware started failing and that ethernet is broken since. Offcourse failures can happen, but should I be worried that the other device can fail as well in a (relatively short) time?
If I recall correctly the issue occurred after resetting the device, I did not flashed it at that point.

In the mean time I've ordered 2 new boards from Olimex webshop, hoping to get another batch or revision so that at least i have some spare boards available.
4
RK3188 / Re: Up to date guide to get an OS for a RK3188?!?!
« Last post by LubOlimex on July 20, 2019, 01:40:23 AM »
Get the archive with the latest image directly from here: ftp://staging.olimex.com/Lub-clients/RK3188_debian_3.0.36_SD_release2.img.7z

Compiling with newer compiler would be nearly impossible. If you wish to build our image you have to use the same tools.
5
RK3188 / Up to date guide to get an OS for a RK3188?!?!
« Last post by hzg_it on July 19, 2019, 07:01:08 PM »
Hi everyone,
today I received a RK3188-SOM-EVB. (https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/)

Now I am trying to get it working, however, the Wiki (https://www.olimex.com/wiki/RK3188-SOM) seems to be somewhat out of date - the torrent links for the prebuilt Debian images apparently have no peers from where I could download the ima (both, the v1 and the v2), the Link for the prebuilt Ubuntu image is also no longer pointing to an image (and the image mentioned is for 14.10, not the freshest Ubuntu...) - whe whole folder structure is not as written in the wiki, so I am a little bit confused on where to get prebuilt images.  :-\

Then I tried to compile my own image - but again, the wiki is not "compatible" with my current Ubuntu 18.04:
 - instead of gcc-4.7-arm-linux-gnueabihf, I had to install gcc-8-arm-linux-gnueabihf
 - instead of uboot-mkimage, I had to use u-boot-tools

So far, so good (or that´s what I thought).

Then I created the .config file for make with
Code: [Select]
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- olimex_rk3188_defconfig, apparently successful.
According to the wiki, I now should be able to build the kernel by running
Code: [Select]
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img - which fails.  :(

The make command could not find a command called
Code: [Select]
arm-linux-gnueabihf-gcc.
Google pointed me to https://packages.ubuntu.com/de/xenial/gcc-arm-linux-gnueabihf, so I did
Code: [Select]
sudo apt install gcc-arm-linux-gnueabihf.

Yay, one step further! Now the make error looks different:
Code: [Select]
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  HOSTCC  scripts/bmptologo
  CC      scripts/mod/empty.o
make[1]: 'include/generated/mach-types.h' is up to date.
  HOSTCC  scripts/conmakehash
  CC      kernel/bounds.s
  HOSTCC  scripts/mod/mk_elfconfig
In file included from include/linux/compiler.h:48:0,
                 from include/linux/stddef.h:4,
                 from include/linux/posix_types.h:4,
                 from include/linux/types.h:17,
                 from include/linux/page-flags.h:8,
                 from kernel/bounds.c:9:
include/linux/compiler-gcc.h:99:1: fatal error: linux/compiler-gcc7.h: No such file or directory
 #include gcc_header(__GNUC__)
 ^~~~
compilation terminated.
./Kbuild:35: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 1
Makefile:999: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
make: *** Waiting for unfinished jobs....
scripts/bmptologo.c:63:27: warning: ‘clut_vga16’ defined but not used [-Wunused-const-variable=]
 static const struct color clut_vga16[16] = {
                           ^~~~~~~~~~
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTLD  scripts/mod/modpost

As far, as I understand the things google tries to tell me when I ask about the above error, I am using a newer gcc than the toolchain is intended for...

For now, I am using this post to document stuff I am doing/trying but if anyone has any enlightening ideas on what am I doing wrong or what I could do to get a Linux (Debian or Ubuntu, I don´t care) running on my RK3188 faster (or a working link to an image), I would be grateful!

TIA,
hzg_it
6
A20 / Re: Prevent lime2 from booting when plugin power cable
« Last post by soenke on July 18, 2019, 07:37:18 PM »
To interrupt uboot while booting i think you need to press the space key a lot with an attached keyboard or UART.

But i think it would be easier to patch uboot so it is not overwriting the registers.
7
A20 / Re: Prevent lime2 from booting when plugin power cable
« Last post by JohnS on July 18, 2019, 06:18:22 PM »
Very interesting. I found out why REG40 41 42 43 are all 0x00 :
https://gitlab.denx.de/u-boot/u-boot/blob/master/drivers/power/axp209.c

The uboot driver of AXP209 is setting them all to 0x00 on boot...

No idea why they are doing this actually...

Maybe try asking the person who wrote the code.

If there's no good reason for that code, submit a patch (or fix request).

John
8
A20 / Re: Prevent lime2 from booting when plugin power cable
« Last post by PaddleStroke on July 18, 2019, 05:33:22 PM »
I wonder if to disable boot from pluging power cable, we don't need to read REG 00 bit 0
Quote
Indicating whether the boot source is ACIN or VBUS R
0: Boot source isn’t ACIN/VBUS; 1: Boot source is ACIN/VBUS.

And add a if in the uboot code to interrupt boot if this reg say it booted because of ACIN/VBUS.

But I don't think it's a good solution as it will still boot until reaching this part of uboot script.

Btw do you know what is uboot command to abort boot and shutdown?
9
A20 / Re: Using AXP209 GPIO ADC
« Last post by PaddleStroke on July 18, 2019, 05:20:02 PM »
Finally found the reason. The uboot driver of AXP209 is reseting the GPIO status on every boot...
https://gitlab.denx.de/u-boot/u-boot/blob/master/drivers/power/axp209.c

10
A20 / Re: Prevent lime2 from booting when plugin power cable
« Last post by PaddleStroke on July 18, 2019, 05:18:51 PM »
Very interesting. I found out why REG40 41 42 43 are all 0x00 :
https://gitlab.denx.de/u-boot/u-boot/blob/master/drivers/power/axp209.c

The uboot driver of AXP209 is setting them all to 0x00 on boot...

No idea why they are doing this actually...
Pages: [1] 2 3 ... 10