February 04, 2023, 01:17:03 pm

Recent posts

Pages 1 ... 5 6 7 8 9 10
61
ESP32 / Re: olimex ESP32-EVB does not ...
Last post by jorn - January 20, 2023, 01:44:50 pm
I've made a (temporary) fix/bodge in hardware to disconnect the RX and TX lines until the code is loaded.
This is done by putting a 2n2222 transistor in series with the TX and RX line. Then these transistors are connected to another 2n2222 acting as a not-gate.
The not-gate input is connected to gpio 14.
During boot the RX and TX will be 'disconnected' and when the code is ready to use the UART it wil pull GPIO 14 low.
I needed the not gate because all the pins I could use are pulled high on boot.
This seems to solve my problem for now.
p.s. I'm using these pins because I wanted to use the UEXT connector and not have to solder to the EVB
62
ESP32 / Re: olimex ESP32-EVB does not ...
Last post by jorn - January 20, 2023, 10:40:13 am
In short the code reads in a sensor on gpio 16, when the sensor is high it will send and recieve data over serial to/from a barcode reader (RXD gpio 36 and TXD gpio 4, serial port 2). After that a UDP message will be send over ethernet and relay 1 will be triggered.
adding a delay to the start does not seem to work. I've tried 1s and 10s and in both cases I could still replicate the problem by pressing the reset button.
I'll try other code to see if I can replicate the problem.
-edit-
able to replicate problem with: https://github.com/espressif/arduino-esp32/blob/master/libraries/Ethernet/examples/ETH_LAN8720/ETH_LAN8720.ino
by pressing the reset button
-edit2-
only seems to happen when the barcode reader is (powered and) connected to the RX and TX pins
63
ESP32 / Re: ESP32 PoE ISO - Does not r...
Last post by LubOlimex - January 20, 2023, 10:00:34 am
Revision I is good enough regarding the Ethernet, anything after revision E has protection TVS1 on the Ethernet. Probably the TVS1 got damaged by your setup somehow. Probably you can fix hte boards by changing the TVS1, first measure if it is damaged.

Taken from the revision changes:

https://github.com/OLIMEX/ESP32-POE-ISO/blob/master/HARDWARE/Hardware-changes-log.txt

"Hardware revision E (internal, unreleased):

1. Added TVS1, ESDS314DBVR(SOT-23-5) to protect the Ethernet's PHY from ESD and other transient voltages;
...
"
64
ESP32 / Re: ESP32 PoE ISO - Does not r...
Last post by recursinging - January 20, 2023, 09:53:21 am
All 10 are "Rev.I" (or "Rev.1"?).

Is there a newer hardware revision out? I need another 10 working boards right now.

I've been sorting the bad ones out by flashing the "ETH_LAN8720" example.

65
A64 / Re: usb0-vbus: disabling
Last post by FalloutST - January 19, 2023, 09:25:40 pm
So
1) lets guest if is device tree

root@a64-olinuxino:/boot# cat uEnv.txt
#
# Auto-generated on: 2020-12-17 20:55:54.395035
# Generated UUID: ac9ed218-eca9-469d-a234-7ebcb5617e81
#
# Put u-boot environment variables here. Before boot, boot.scr will use these variables:
#
# boot_config - Explicitly specify the boot configuration
# fdtoverlays - List of overlay files
# load_legacy - Don't load FIT image,
# optargs - Optional arguments passed to the kernel

fdtoverlays=/usr/lib/olinuxino-overlays/sun50i-a64/spi0-spiflash.dtbo /usr/lib/olinuxino-overlays/sun50i-a64/sun50i-a64-i2c0.dtbo /usr/lib/olinuxino-overlays/sun50i-a64/sun50i-a64-uart2.dtbo

Lets add boot_config=config-9065

Then logs:

#journalctl -g usb
Jan 19 18:19:26 a64-olinuxino systemd[1]: Reached target Hardware activated USB gadget.
Jan 19 18:19:51 a64-olinuxino kernel: usb0-vbus: disabling
lets look closer to Jan 19 18:19:51
Jan 19 18:19:33 a64-olinuxino avahi-daemon[384]: Registering new address record for 192.168.88.243 on eth0.IPv4.
Jan 19 18:19:33 a64-olinuxino NetworkManager[387]: <info>  [1674152373.9702] device (eth0): state change: ip-config -> ip-check (>
Jan 19 18:19:34 a64-olinuxino NetworkManager[387]: <info>  [1674152374.0058] device (eth0): state change: ip-check -> secondaries>
Jan 19 18:19:34 a64-olinuxino NetworkManager[387]: <info>  [1674152374.0073] device (eth0): state change: secondaries -> activate>
Jan 19 18:19:34 a64-olinuxino NetworkManager[387]: <info>  [1674152374.0143] policy: set 'dhcpx-02' (eth0) as default for IPv4 ro>
Jan 19 18:19:34 a64-olinuxino NetworkManager[387]: <info>  [1674152374.0162] dns-mgr: Writing DNS information to /sbin/resolvconf
Jan 19 18:19:34 a64-olinuxino dbus-daemon[385]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='db>
Jan 19 18:19:34 a64-olinuxino dbus-daemon[385]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.se>
Jan 19 18:19:34 a64-olinuxino NetworkManager[387]: <info>  [1674152374.2843] device (eth0): Activation: successful, device activa>
Jan 19 18:19:34 a64-olinuxino NetworkManager[387]: <info>  [1674152374.2907] manager: startup complete
Jan 19 18:19:38 a64-olinuxino dhclient[445]: No DHCPOFFERS received.
Jan 19 18:19:38 a64-olinuxino sh[445]: No DHCPOFFERS received.
Jan 19 18:19:38 a64-olinuxino sh[445]: Trying recorded lease 192.168.0.1
Jan 19 18:19:38 a64-olinuxino dhclient[445]: Trying recorded lease 192.168.0.1
Jan 19 18:19:38 a64-olinuxino avahi-daemon[384]: Registering new address record for 192.168.0.1 on eth0.IPv4.
Jan 19 18:19:38 a64-olinuxino dhclient[445]: bound: renewal in 473331269 seconds.
Jan 19 18:19:38 a64-olinuxino sh[445]: bound: renewal in 473331269 seconds.
Jan 19 18:19:39 a64-olinuxino sh[639]: eth0=eth0
Jan 19 18:19:44 a64-olinuxino systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 19 18:19:51 a64-olinuxino kernel: usb0-vbus: disabling
Jan 19 18:19:58 a64-olinuxino systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 19 18:21:22 a64-olinuxino kernel: usb 2-1.4: USB disconnect, device number 3
Jan 19 18:21:23 a64-olinuxino kernel: usb 2-1.4: new high-speed USB device number 4 using ehci-platform
Very Interesting! So that why eth0 is getting 192.168.0.1 with out my wish....
So lets add some '#' to dhclient config:
#lease {
#  interface "eth0";
#  fixed-address 192.168.0.1;
#  option subnet-mask 255.255.255.0;
#  renew 2 2040/1/12 00:00:01;
#  rebind 2 2040/1/12 00:00:01;
#  expire 2 2040/1/12 00:00:01;
#}
I am away to check NetworkManager config
To be continued...
66
ESP32 / Re: ESP32 PoE ISO - Does not r...
Last post by LubOlimex - January 19, 2023, 04:57:33 pm
What was the hardware revision of the boards, as printed on them?
67
ESP32 / Re: olimex ESP32-EVB does not ...
Last post by LubOlimex - January 19, 2023, 04:56:09 pm
What kind of code is loaded to the board? Can you try to insert some software delay around the start of your code?
68
ESP32 / olimex ESP32-EVB does not alwa...
Last post by jorn - January 19, 2023, 04:27:43 pm
sometimes after power on or after programming the EVB will not load the programmed code but hang on the UART boot.
Via the terminal I'll get: rst:0x1 (POWERON_RESET),boot:0xf (UART_BOOT(UART0))
read somewhere it could be because of pin 2 not being held low during boot.
I've got a REV.k here any ideas?
69
ESP32 / Re: ESP32 ethernet UPD server ...
Last post by NielsO - January 19, 2023, 11:20:15 am
Hi LubOlimex

The version is ESP32-GATEWAY-IND rev. G.

Could you please provide your iperf ethernet test results for ESP32 gateway in server mode. What is the bandwidth? Which framework did you use?

The ESP-IDF iperf test is working in client mode, also the ESP-IDF basic ethernet example is working - the device is getting IP in DHCP mode AND it is possible to ping the device. 

We have also performed an ethernet speed test with Arduino where the bandwidth was measured to 700 Kbit/s.

We have experienced this ethernet speed problem with 2 different frameworks, that is why we reach out to you.

BR Niels
70
ESP32 / Re: ESP32 PoE ISO - Does not r...
Last post by recursinging - January 19, 2023, 11:07:10 am
So after ordering another 10 units, I've determined 4 have this defect, making them useless for my needs. Incredibly frustrating. Does anyone else here have such a high failure rate for these things?
Pages 1 ... 5 6 7 8 9 10