September 25, 2021, 04:35:38 am

Recent posts

Pages 1 2 3 4 5 ... 10
21
A64 / Re: Camera module for OLinuxIN...
Last post by Eric976 - September 14, 2021, 05:56:45 am
I keep trying.
My new overlay is as following:
/dts-v1/;
/plugin/;

/ {
        compatible = "allwinner,sun50i-a64\0olimex,a64-olinuxino";
        description = "Test camera OV5647";

        fragment@0 {
                target = <&i2c1>;

                __overlay__ {
                        #address-cells = <1>;
                        #size-cells = <0>;
                        status = "okay";

                        ov5647: ov5647@36 {
                                compatible = "ovti,ov5647";
                                reg = <0x36>;
                                status = "okay";

                                clocks = <&ov5647_clk>;
                                clock-names = "xclk";

                                rotation = <0>;
                                orientation = <2>;

                                ov5647_clk: camera-clk {
                                        compatible = "fixed-clock";
                                        #clock-cells = <0>;
                                        clock-frequency = <25000000>;
                                };

                                port {
                                        ov5647_ep: endpoint {
                                                remote-endpoint = <&dsi_ep>;
                                                clock-lanes = <0>;
                                                data-lanes = <0 1>;
                                                clock-noncontinuous;
                                                link-frequencies =
                                                        /bits/ 64 <297000000>;
                                        };
                                };
                        };
                };
        };

        fragment@1 {
                target = <&dsi>;
                __overlay__ {
                        status = "okay";
                        vcc-dsi-supply = <0x04>;

                        port {
                                dsi_ep: endpoint {
                                        remote-endpoint = <&ov5647_ep>;
                                        data-lanes = <1 2>;
                                };
                        };
                };
        };

        fragment@2 {
                target = <&dphy>;
                __overlay__ {
                        status = "okay";
                };
        };
};

I added the fragment 2 to solve the D-PHY error, that I said before, and I added "vcc-dsi-supply = <0x04>" because I had an error related to this.
22
A64 / Re: Camera module for OLinuxIN...
Last post by Eric976 - September 14, 2021, 05:21:08 am
One more update, I can see the driver, but there is no video in the device "video0".
olimex@a64-olinuxino:/$ sudo find -name "*ov5647*"
find: './run/user/1000/gvfs': Permission denied
./usr/lib/olinuxino-overlays/sun50i-a64/ov5647-eric.dts.bak2
./usr/lib/olinuxino-overlays/sun50i-a64/ov5647-eric.dts
./usr/lib/olinuxino-overlays/sun50i-a64/ov5647-eric.dts.bak
./usr/lib/olinuxino-overlays/sun50i-a64/ov5647-eric.dtbo
./usr/lib/modules/5.10.60-olimex/kernel/drivers/media/i2c/ov5647.ko
./sys/bus/i2c/drivers/ov5647
./sys/firmware/devicetree/base/soc/i2c@1c2b000/ov5647@36
./sys/module/videodev/holders/ov5647
./sys/module/v4l2_fwnode/holders/ov5647
./sys/module/ov5647
./sys/module/ov5647/drivers/i2c:ov5647
./sys/module/mc/holders/ov5647
23
A20 / A20 LIME2 with LCD-OLinuXino-...
Last post by MPH - September 13, 2021, 06:32:33 pm
Hi All,

I have an  A20-OLinuXino-LIME2 that I want to use with an  LCD-OLinuXino-5CTS.
The display works fine, but I am unable to use/calibrate the touchscreen and only get the error "No calibratable devices found".
Then I read that the standard configuration for the LIME2 is to only work with analog touchscreens, while the LCD-5CTS has a digital touchscreen.

If I want to only use the LIME2 with digital touchscreens, would it be sufficient to disconnect the IC RM1 and move it to RM2 or do both need to be connected? In the Bill of Materials (https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/HARDWARE/A20-OLinuXino-LIME2/1.%20Latest%20hardware%20revision/Bills-of-materials/A20-OLinuXino-Lime2_Rev_L_1Ge16Gs16MB_bom.pdf) it seems like this is the same IC/Resistor Network.

Thanks for reading and I hope you can help!
24
A64 / Re: Camera module for OLinuxIN...
Last post by Eric976 - September 13, 2021, 02:51:46 pm
Hello again, guys
I think that I'm almost there...

I came back to the first camera module that I was testing, the OV5647, because I saw the driver already included in the kernel. So let me post some results I have so far with the board A64-OLinuxIno Rev C.

The hardware connections that I've done
https://drive.google.com/file/d/1NMO6MsOGPhU9EPOtvKFlgxWsYtoXcxjq/view?usp=sharing.

The overlay that I'm writing
/dts-v1/;
/plugin/;

/ {
compatible = "allwinner,sun50i-a64\0olimex,a64-olinuxino";
description = "Test camera OV5647";

fragment@0 {
target = <&i2c1>;

__overlay__ {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";

ov5647: ov5647@36 {
compatible = "ovti,ov5647";
reg = <0x36>;
status = "okay";

clocks = <&ov5647_clk>;
clock-names = "xclk";

rotation = <0>;
orientation = <2>;

ov5647_clk: camera-clk {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <25000000>;
};

port {
ov5647_ep: endpoint {
remote-endpoint = <&dsi_ep>;
clock-lanes = <0>;
data-lanes = <0 1>;
clock-noncontinuous;
link-frequencies =
/bits/ 64 <297000000>;
};
};
};
};
};

fragment@1 {
target = <&dsi>;
__overlay__ {
status = "okay";

port {
dsi_ep: endpoint {
remote-endpoint = <&ov5647_ep>;
data-lanes = <1 2>;
};
};
};
};
};

My config file
olimex@a64-olinuxino:~$ cat /boot/config-`uname -r` | grep I2C | grep GPIO
CONFIG_I2C_ARB_GPIO_CHALLENGE=m
CONFIG_I2C_MUX_GPIO=m
CONFIG_I2C_CBUS_GPIO=m
CONFIG_I2C_GPIO=y
# I2C GPIO expanders
# end of I2C GPIO expanders

I can detect the I2C device
olimex@a64-olinuxino:~$ sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- 

The driver seems to be loaded
olimex@a64-olinuxino:~$ lsmod | grep ov
ov5647                 16384  0
v4l2_fwnode            20480  1 ov5647
videodev              262144  6 sunxi_cedrus,v4l2_fwnode,ov5647,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
mc                     49152  6 sunxi_cedrus,videodev,ov5647,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem

Now I think that the next step is to solve these errors
olimex@a64-olinuxino:/usr/lib/olinuxino-overlays/sun50i-a64$ dmesg | grep dsi
[    9.489756] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.490088] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.510836] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.511156] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.530344] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.530637] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.576110] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.576457] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.616954] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.617276] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.811233] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.811529] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.842259] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.842600] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[    9.865445] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[    9.865779] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
[   11.154077] sun6i-mipi-dsi 1ca0000.dsi: supply vcc-dsi not found, using dummy regulator
[   11.154431] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY

Can someone please help me to get this camera module to work?

I'm waiting for a return.
Thanks in advance.
25
ESP32 / Re: ESP 32 POE ISO ethernet no...
Last post by LubOlimex - September 13, 2021, 08:19:53 am
It has static IP address set and maybe it doesn't belong to your network. Try to fiddle with this part:

ETH.config(IPAddress(192, 168, 1, 101),IPAddress(192, 168, 1, 1),IPAddress(255, 255, 255, 0),IPAddress(192, 168, 1, 1), IPAddress(192, 168, 1, 1));

Try with DCHP instead, maybe try this demo:

https://raw.githubusercontent.com/OLIMEX/ESP32-POE/master/SOFTWARE/ARDUINO/ESP32_PoE_Ethernet_SD_Card_Arduino/ESP32_PoE_Ethernet_SD_Card_Arduino.ino

26
UEXT / Re: MOD-IO2: UEXT male vs UEXT...
Last post by LubOlimex - September 13, 2021, 08:15:06 am
Thanks for the update. Glad you figured it out. The thing with UEXT_PWR_E jumper was invented because by default "MOD-xxx" boards were not meant to provide power by default, because you usually connect them to "master" board that provides 3.3V and it is real possibility to have both "master" and "MOD-xxx" boards provide 3.3V at the UEXT, which would lead to short circuit.
27
A64 / Re: u-boot-olinuxino
Last post by afancher - September 11, 2021, 08:31:20 pm
Hi, just an update for those who are interested...

I've expanded my knowledge a bit on shell and python scripting and am right now testing and troubleshooting a patch that will create an entrypoint to pause the Olimage build process to allow a custom-built u-boot-olinuxino binary to be substituted and included in the final image.

Once I've gotten it working I'll include the other supported platforms and put in a pull request on the Olimage git repository.  Stay tuned :)
28
ESP32 / ESP 32 POE ISO ethernet not wo...
Last post by MicBar - September 10, 2021, 09:14:52 pm
Hi,

i'm new on Arduino community and I've been working on ESP32 poe iso for a few days

i want established an ethernet connection between the board and my pc to create a tcp/ip connection between my pc and the board. i tried to use this code



#define ETH_CLK_MODE ETH_CLOCK_GPIO17_OUT
#define ETH_PHY_POWER 12

#include <ETH.h>

static bool eth_connected = false;

void WiFiEvent(WiFiEvent_t event)
{
  switch (event) {
    case SYSTEM_EVENT_ETH_START:
      Serial.println("ETH Started");
      //set eth hostname here
      ETH.setHostname("esp32-ethernet");
      break;
    case SYSTEM_EVENT_ETH_CONNECTED:
      Serial.println("ETH Connected");
      break;
    case SYSTEM_EVENT_ETH_GOT_IP:
      Serial.print("ETH MAC: ");
      Serial.print(ETH.macAddress());
      Serial.print(", IPv4: ");
      Serial.print(ETH.localIP());
      if (ETH.fullDuplex()) {
        Serial.print(", FULL_DUPLEX");
      }
      Serial.print(", ");
      Serial.print(ETH.linkSpeed());
      Serial.println("Mbps");
      eth_connected = true;
      break;
    case SYSTEM_EVENT_ETH_DISCONNECTED:
      Serial.println("ETH Disconnected");
      eth_connected = false;
      break;
    case SYSTEM_EVENT_ETH_STOP:
      Serial.println("ETH Stopped");
      eth_connected = false;
      break;
    default:
      break;
  }
}

void testClient(const char * host, uint16_t port)
{
  Serial.print("\nconnecting to ");
  Serial.println(host);

  WiFiClient client;
  if (!client.connect(host, port)) {
    Serial.println("connection failed");
    return;
  }
  client.printf("GET / HTTP/1.1\r\nHost: %s\r\n\r\n", host);
  while (client.connected() && !client.available());
  while (client.available()) {
    Serial.write(client.read());
  }

  Serial.println("closing connection\n");
  client.stop();
}

void setup()
{
  Serial.begin(115200);
  WiFi.onEvent(WiFiEvent);
  ETH.begin();
  ETH.config(IPAddress(192, 168, 1, 101),IPAddress(192, 168, 1, 1),IPAddress(255, 255, 255, 0),IPAddress(192, 168, 1, 1), IPAddress(192, 168, 1, 1));
}


void loop()
{
 
  Serial.print("Looping.. ");
  Serial.print("IPv4: ");
  Serial.println(ETH.localIP());
  if (eth_connected) {
    testClient("google.com", 80);
  }
  delay(10000);
}

but after the flash, from the serial plotter i can see only

Looping.. IPv4: 0.0.0.0

why does ethernet connection not work?

how can i set a static IP and then ping it by command prompt line? i'm using win 10

best regards
29
UEXT / Re: MOD-IO2: UEXT male vs UEXT...
Last post by Peter G. - September 10, 2021, 05:41:27 pm
Sorry, it was my fault. I will answer my own question.
Quote from: Peter G. on September 10, 2021, 11:01:49 amEach UEXT connector can provide power, but it has not to
That was the whole problem! Closing jumper UEXT_FPWR_E fixed it. So now following combination works like a charm:
ESP32-EVB, UEXT male 3V3 <-> UEXT cable 3V3 <-> UEXT male, MOD-IO2, UEXT_FPWR_E closed, UEXT female 3V3 <-> UEXT male, MOD-ENV
30
ESP32 / Re: ESP32-S2-DevKit-Lipo-USB R...
Last post by findmyname - September 10, 2021, 01:05:42 pm
Quote from: LubOlimex on September 10, 2021, 09:30:06 amAnd there are hardware differences between WROOM and WROVER modules. WROVER has 2 MB PSRAM, and WROOM lacks such PSRAM.

Hmm does it mean that RTC works only if there is PSRAM ?
But it kind of make sense - info from https://diyprojects.io/esp32-store-temporary-data-rtc-memory-deep-sleep
```
8 KB of RTC SRAM, called RTC FAST memory, can be used for data storage. It is accessible by the main processor during RTC boot when exiting Deep-Sleep mode.
8 KB of RTC SRAM, called RTC SLOW memory and accessible by the ULP coprocessor when the processor is in Deep-Sleep.
```
I expect PSRAM == SRAM.
Pages 1 2 3 4 5 ... 10