EEPROM reading using Hexdump

[MyMylou]

Hello,

I am implementing a custom camera driver for Jetson Orin - jetpack 5.1.3

I implemented the EEPROM in device tree.
I am able to detect the EEprom correctly using i2cdetect
I can read the EEprom correctly using i2cdump or i2cset/i2cget
However, when I read the EEprom using Hexdump I got only one value then a lot of “FF” then a good value then a lot of “FF”

I fill like the regmap_bulk_read is going too fast and cannot get all the values correctly.
Would you have a idea what’s happening?

Thanks

[carolyuu]

Hi,

For the camera basic functionality first needs to check the device and driver configuration.
You can reference to below program guide for the detailed information of device tree and driver implementation.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#sensor-software-driver-programming

Please refer to Applications Using V4L2 IOCTL Directly by using V4L2 IOCTL to verify basic camera functionality.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#to-run-a-v4l2-ctl-test

Once confirm the configure and still failed below link help to get log and some information and some tips for debug.
https://elinux.org/Jetson/l4t/Camera_BringUp#Steps_to_enable_more_debug_messages

Thanks!

[MyMylou]

Hello and thanks for the answer. The driver implementation seems good as I am able to get a stream.

The issue comes from the EEprom module only.
I am able to read EEprom using i2cdump and i2cset and i2cget.
However, reading EEprom using Hexdump with driver atmel at24 I got some FF values instead of real values.

[JerryChang]

hello MyMylou,

how about adding some options to hexdump?
for instance, -C: canonical hex+ASCII display; -n: length of bytes; -s: offsets;
i.e. $ hexdump -C -n 4 -s 0x24 xxx.bin