Imx230 (B0324) fails and can't be accessed

  1. Where did you get the camera module(s)? thepihut

  2. Model number of the product(s)? imx230

  3. What hardware/platform were you working on? pi 3 B +

  4. Instructions you have followed. (link/manual/etc.)
    Quick start

  5. Problems you were having?
    Can’t access camera. See further details

  6. The dmesg log from your hardware?
    See further details

  7. Troubleshooting attempts you’ve made?
    Checked this forum

  8. What help do you need?
    Is this a hardware issue? If so I will need to send it back

Hi,

I have recently purchased the imx230 camera module but I can’t get it working. If the problem is not with the software or the process I’ve followed (all installed fresh with new OS and repeatable) then I can only assume the camera is faulty. If this could be confirmed then I will start the process of returning the camera. I also have three other camera: 64MP, IMX519 and IMX462 which all work so hopefully I’m familiar with the process.

The problem:

Once the installation processes is complete using a fresh OS the --list-cameras command fails as follows:

pi@raspberrypi3s1n16gb:~ $ libcamera-hello --list-cameras
Read failed
Available cameras

0 : arducam-pivariety [5344x4016] (/base/soc/i2c0mux/i2c@1/arducam_pivariety@c)

At this point the session locks up and I can’t gain control by pressing control c or z so I have to close the session.

The installation process was following under quick start. i.e.

  1. Download install_pivariety_pkgs.sh
  2. Install libcamera_dev
  3. Install libcamera_apps
  4. Amend config.txt to add dtoverlay=arducam-pivariety

Its hard to see what I have done wrong as there are so few steps.

The dmesg seems to contain repeated errors.

[ 119.747718] arducam-pivariety 10-000c: pivariety_read: Reading register 0x107 failed

The above line repeats over and over again.

Any ideas?

Now follows required machine info:

pi@raspberrypi3s1n16gb:~ $ uname -a
cat /etc/os-release
cat /proc/meminfo
cat /boot/config.txt
Linux raspberrypi3s1n16gb 5.15.84-v7+ #1613 SMP Thu Jan 5 11:59:48 GMT 2023 armv7l GNU/Linux
PRETTY_NAME=“Raspbian GNU/Linux 11 (bullseye)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“11”
VERSION=“11 (bullseye)”
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/
SUPPORT_URL=“RaspbianForums - Raspbian
BUG_REPORT_URL=“RaspbianBugs - Raspbian
MemTotal: 944268 kB
MemFree: 405356 kB
MemAvailable: 739524 kB
Buffers: 24492 kB
Cached: 350820 kB
SwapCached: 0 kB
Active: 78272 kB
Inactive: 397024 kB
Active(anon): 984 kB
Inactive(anon): 103756 kB
Active(file): 77288 kB
Inactive(file): 293268 kB
Unevictable: 16 kB
Mlocked: 16 kB
SwapTotal: 102396 kB
SwapFree: 102396 kB
Dirty: 196 kB
Writeback: 0 kB
AnonPages: 100072 kB
Mapped: 119584 kB
Shmem: 4732 kB
KReclaimable: 17336 kB
Slab: 34876 kB
SReclaimable: 17336 kB
SUnreclaim: 17540 kB
KernelStack: 1896 kB
PageTables: 4160 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 574528 kB
Committed_AS: 1038576 kB
VmallocTotal: 1114112 kB
VmallocUsed: 5860 kB
VmallocChunk: 0 kB
Percpu: 448 kB
CmaTotal: 262144 kB
CmaFree: 256660 kB

For more options and information see

Raspberry Pi Documentation - Configuration

Some settings may impact device functionality. See link above for details

uncomment if you get no picture on HDMI for a default “safe” mode

#hdmi_safe=1

uncomment the following to adjust overscan. Use positive numbers if console

goes off screen, and negative if there is too much border

#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

uncomment to force a console size. By default it will be display’s size minus

overscan.

#framebuffer_width=1280
#framebuffer_height=720

uncomment if hdmi display is not detected and composite is being output

#hdmi_force_hotplug=1

uncomment to force a specific HDMI mode (this will force VGA)

#hdmi_group=1
#hdmi_mode=1

uncomment to force a HDMI mode rather than DVI. This can make audio work in

DMT (computer monitor) modes

#hdmi_drive=2

uncomment to increase signal to HDMI, if you have interference, blanking, or

no display

#config_hdmi_boost=4

uncomment for composite PAL

#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

Uncomment some or all of these to enable the optional hardware interfaces

#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

Uncomment this to enable infrared communication.

#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on

Automatically load overlays for detected cameras

camera_auto_detect=1

Automatically load overlays for detected DSI displays

display_auto_detect=1

Enable DRM VC4 V3D driver

dtoverlay=vc4-kms-v3d
max_framebuffers=2

Disable compensation for displays with overscan

disable_overscan=1

[cm4]

Enable host mode on the 2711 built-in XHCI USB controller.

This line should be removed if the legacy DWC2 controller is required

(e.g. for USB device mode) or if USB support is not required.

otg_mode=1

[all]

[pi4]

Run as fast as firmware / board allows

arm_boost=1

[all]
dtoverlay=arducam-pivariety
pi@raspberrypi3s1n16gb:

pi@raspberrypi3s1n16gb:~ $ dmesg | grep -i ardu
[ 15.688355] arducam-pivariety 10-000c: firmware version: 0x10001
[ 16.054777] arducam-pivariety 10-000c: Consider updating driver arducam-pivariety to match on endpoints
[ 105.188259] arducam-pivariety 10-000c: pivariety_write: Write 0x0000 to register 0x200 failed
[ 107.268081] arducam-pivariety 10-000c: pivariety_write: Write 0x0007 to register 0x300 failed
[ 110.388028] arducam-pivariety 10-000c: pivariety_read: Reading register 0x107 failed
[ 113.507916] arducam-pivariety 10-000c: pivariety_read: Reading register 0x107 failed
[ 116.627794] arducam-pivariety 10-000c: pivariety_read: Reading register 0x107 failed
[ 119.747718] arducam-pivariety 10-000c: pivariety_read: Reading register 0x107 failed

Above errors repeat 20 or 30 times.

@bmike

This is an older version of hardware and the new tutorial does not apply.
We need to discuss this and get back to you later.

Ok, thanks.
Does this mean there is a new version of the same imx230 camera ?
Am I waitning for a software fix or should I follow the old instructions. I think I remeber following, what seemed to be older instructions which required an imx230 driver. I’m sure this didn’t work either.

@bmike

Hello, thank you for your question. If you want to learn how to use the camera, we have a link for you that contains a tutorial on how to use the camera, including how to connect it, how to install the driver and SDK, how to adjust the settings, and how to capture images and videos. The link is “OBISP Camera Userland Driver and SDK - Arducam. We hope this helps you, if you have any questions, please feel free to contact us.

Before I go down this route I need to use my camera with libcamera-apps using my own development version based on the latest code. A quick read seems to be implying this is not possible. Is that correct?

If so I need to send it back and get a refund. Is there a newer version of the IMX230 camera that is compatible or should I stick other cameras.

@bmike

yes.

The hardware you get is very old. For this camera, we now release all supported libcamera-apps, you can ask the dealer to replace you with the latest version, if they are not clear, you can ask them to contact us, we are now free for them to replace into the latest.

Thanks, I will contact the supplier with the details

Thanks, I have now returned the item and it has been refunded.
Could you tell me is the imx230 depreciated or can I still purchase one with up to date hardware. If so, how would I recognise one so I can confirm it is the latest before it is sent.

Hi,
You can contact [email protected] for further information.