Robert Heller

  • Content Count

    13
  • Joined

  • Last visited

1 Follower

About Robert Heller

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. A fragment of my DTS is elsewhere in this thread. Note: it is for a Banana Pi M64, which is probably different from your Pine64. I got my working properly by refering to the schematic diagram I have for the Banana Pi M64. You need to get the schematic diagram for your Pine64, so you know exactly which GPIO pines are wired to the CSI connector, then you can be sure that the DTS file properly sets up the correct GPIO pins to the correct functions.
  2. I found a .dts file that was similar to my board and copy and pasted the parts relating to the camera to the dts file for mine, and then recompiled the dts to a dtb with "make dtbs" and then installed it using "make dtbs_install". Do you have the schematic for your board? That should show you which GPIO pins are used for the camera, so you can make the necessary changes to the device tree code you copied.
  3. You need to enable "V4L platform devices" under Device Drivers > Multimedia support > Media drivers, then under "V4L platform devices" you want "Allwinner V3s Camera Sensor Interface driver" enabled as M.
  4. I have a couple of questions: Exactly how is the Image Format and Image Size information get decoded from the output of and into the command line arguments to media-ctl and fswebcam, and how do I make the settings "stick" for programs like cheese and chromium (the latter so I can use programs / sites like Zoom and GoToMeeting and Google Hangouts -- eg video conferencing, etc.)?
  5. I don't understand how to format the command line for media-ctl. There doesn't appear to be a man page for it and the example from the (scant) documentation for fswebcam does not match what I have.
  6. OK, got the sun6i_csi module built, now the addition /dev files are there, but running cheese raises an error: Script started on 2020-10-29 19:29:03-04:00 [TERM="xterm" TTY="/dev/pts/0" COLUMNS="80" LINES="33"] heller has logged on pts/0 from 192.168.250.5 at 29-Oct-2020 19:19. gollumm64% dmesg | grep sun6i-csi [ 40.914900] sun6i-csi 1cb0000.csi: creating ov5640 0-003c:0 -> sun6i-csi:0 link [ 234.073723] sun6i-csi 1cb0000.csi: Wrong width or height 4800x3840 (640x480 expected) [ 235.308627] sun6i-csi 1cb0000.csi: dma_alloc_coherent of size 27648000 failed [ 358.830527] sun6
  7. gollumm64% lsmod | grep ov overlay 126976 3 ov5640 32768 0 v4l2_fwnode 28672 1 ov5640 videodev 258048 6 sunxi_cedrus,v4l2_fwnode,ov5640,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem mc 57344 6 sunxi_cedrus,videodev,ov5640,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
  8. gollumm64% ls -1 /sys/bus/i2c/devices/*/name /sys/bus/i2c/devices/0-003c/name /sys/bus/i2c/devices/i2c-0/name /sys/bus/i2c/devices/i2c-1/name /sys/bus/i2c/devices/i2c-2/name gollumm64% cat /sys/bus/i2c/devices/*/name ov5640 i2c-csi DesignWare HDMI mv64xxx_i2c adapter gollumm64% ls -1 /sys/bus/i2c/devices/*/i2c-dev/*/name /sys/bus/i2c/devices/i2c-0/i2c-dev/i2c-0/name /sys/bus/i2c/devices/i2c-1/i2c-dev/i2c-1/name /sys/bus/i2c/devices/i2c-2/i2c-dev/i2c-2/name gollumm64% cat /sys/bus/i2c/devices/*/i2c-dev/*/name i2c-csi DesignWare HDMI mv64xxx_i2c adapter OK, still no luck. I looked
  9. OK, I changed CONFIG_I2C_GPIO from module (m) to built in (y): gollumm64% 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 # CONFIG_I2C_GPIO_FAULT_INJECTOR is not set # I2C GPIO expanders # end of I2C GPIO expanders No change.
  10. U-Boot SPL 2020.04-armbian (Jun 14 2020 - 23:09:55 +0200) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.3(debug):635912f-dirty NOTICE: BL31: Built : 23:09:46, Jun 14 2020 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x4095f08, model: BananaPi-M64 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP803 on RSB INFO: PMIC: Enabling DRIVEVBUS INFO: PMIC: dcdc1 voltage: 3.300V INFO: PMIC: dcdc5 voltage: 1.500V INFO: PMIC: dcdc6 voltage: 1.100V INFO: PMIC: dldo1 voltage: 3.300V
  11. I am trying to get an OV5640 camera module to work on a Banana Pi M64 (Allwinner A64). I am running Armbian 20.08.13 Focal with Linux 5.8.16-sunxi64. I have loaded the kernel sources, updated the config to include the ov5640 kernel driver module and updated the device tree, sun50i-a64-bananapi-m64.dts file by copying and adjusting the camera overlay code from sun50i-a64-pinetab.dts, but it is not working: gollumm64% v4l2-ctl --list-devices cedrus (platform:cedrus): /dev/video0 /dev/media0 gollumm64% v4l2-ctl -d 0 --list-formats --list-ctrls Codec Controls