VEYE IMAGING Forum
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc
    • Register
    • Login
    1. Home
    2. natzguk
    3. Topics
    N
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 19
    • Groups 0

    Topics

    • N

      veye_mipi_i2c.sh Raspberry Pi 5

      Watching Ignoring Scheduled Pinned Locked Moved Raspberry Pi App Software
      2
      0 Votes
      2 Posts
      2k Views
      veye_xummV
      @natzguk Raspberry Pi 5 is special, its i2c bus is 4 and 6. meanwhile, Raspberry Pi need to configure the parameters in advance, please refer to this link below: https://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#Raspberry_Pi_5_Setting
    • N

      ROC-RK3588S-PC and IMX462

      Watching Ignoring Scheduled Pinned Locked Moved Rockchip App camera
      18
      0 Votes
      18 Posts
      9k Views
      veye_xummV
      @natzguk pls try this: https://github.com/veyeimaging/rk35xx_firefly/blob/main/linux/samples/gstreamer/veye camera/preview.sh
    • N

      RaspberryPi OS 64-bit

      Watching Ignoring Scheduled Pinned Locked Moved Raspberry Pi App Software
      3
      0 Votes
      3 Posts
      2k Views
      N
      @veye_xumm For anyone else. This works perfectly. Note that when recompiling on 64-bit Pi, the following warning is produced. It still builds. Just copy the outputs to bin and the scripts work fine. ./make.sh i2c_read.c: In function ‘main’: i2c_read.c:112:35: warning: passing argument 4 of ‘i2c_rd’ from incompatible pointer type [-Wincompatible-pointer-types] 112 | i2c_rd(fd, device_addr,reg_addr, &value, num); | ^~~~~~ | | | unsigned char (*)[512] i2c_read.c:20:68: note: expected ‘unsigned char *’ but argument is of type ‘unsigned char (*)[512]’ 20 | static int i2c_rd(int fd, uint8_t i2c_addr, uint16_t reg, uint8_t *values, uint32_t n)
    • N

      Debian 12 - Bookworm driver

      Watching Ignoring Scheduled Pinned Locked Moved Raspberry Pi App Software
      6
      0 Votes
      6 Posts
      3k Views
      veye_xummV
      @natzguk I believe the code is compatible. You can refer to the following link and try compiling it yourself: https://wiki.veye.cc/index.php/Build_drivers_from_source_for_rpi