Hai,
We have Jetson Nano with TC358746 (Parallel to MIPI-CSI) custom carrier board. The chip connected to the Nano via SPI interface.
There is no driver support for SPI mode so, we are following the imx204.c V4l2-SPI driver and try to port the TC358746 in SPI mode. Is anyone working with TC358746 on SPI mode?
Please support us to bring up the SPI mode. Thanks in advance.
Moving to Jetson Nano forum.
This chip should provide i2c interface.
Thanks for the reply ShaneCCC.
We are working on TC358746 (Parallel to MIPI converter connected to Jetson Nano by SPI interface)
For the SPI interface you can reference to …/kernel/nvidia/drivers/media/spi/imx204.c to developer the driver for it.
We have updated the kernel from 32.3.1 to 32.5.1 and we got the below error during bootup.
tarting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.201-tegra (karthick@pandian) (gcc version 7.3.1
20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701]
(Linaro GCC 7.3-2018.05) ) #81 SMP PREEMPT Sat Jun 26 19:28:18 IST 2021
[ 0.000000] Boot CPU: AArch64 Processor [411fd071]
[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 32,
[ 0.000000] OF: fdt: - 80000000 , 7ee00000
[ 0.000000] OF: fdt: - 100000000 , 7f200000
[ 0.000000] Found tegra_fbmem: 003a0000@92ca9000
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options '')
[ 0.000000] bootconsole [uart8250] enabled
[ 1.148865] spi-tegra114 7000d600.spi: chipselect 0 already in use
[ 1.155226] spi_master spi1: spi_device register error /spi@7000d600/spi@0
[ 1.163987] tegradc tegradc.1: dpd enable lookup fail:-19
[ 1.290322] tegradc tegradc.0: blank - powerdown
[ 1.298903] tegra-xusb-padctl 7009f000.xusb_padctl: power on UTMI pads 1
[ 1.299185] usb usb2: usb_suspend_both: status 0
[ 1.324048] extcon-disp-state extcon:disp-state: cable 47 state 0
[ 1.324051] Extcon AUX1(HDMI) disable
[ 1.331109] max77686-rtc max77620-rtc: rtc core: registered max77620-rtc as r
tc0
[ 1.333254] rtc rtc1: alarm rtc device
[ 1.333267] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
[ 1.333283] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
[ 1.333653] i2c /dev entries driver
[ 1.338811] Unable to handle kernel paging request at virtual address ffc000000000
[ 1.338813] Mem abort info:
[ 1.338815] ESR = 0x96000004
[ 1.338819] Exception class = DABT (current EL), IL = 32 bits
[ 1.338821] SET = 0, FnV = 0
[ 1.338823] EA = 0, S1PTW = 0
[ 1.338825] Data abort info:
[ 1.338827] ISV = 0, ISS = 0x00000004
[ 1.338829] CM = 0, WnR = 0
[ 1.338832] [0000ffc000000000] address between user and kernel address ranges
[ 1.338836] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 1.338840] Modules linked in:
[ 1.338846] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.201-tegra #81
[ 1.338848] Hardware name: NVIDIA Jetson Nano Developer Kit (DT)
[ 1.338851] task: ffffffc0fa7baa00 task.stack: ffffffc0fa7c8000
[ 1.338860] PC is at __radix_tree_lookup+0x50/0xe0
[ 1.338865] LR is at radix_tree_lookup+0x14/0x20
[ 1.338868] pc : [<ffffff80084619a0>] lr : [<ffffff8008461a6c>] pstate: 20400
1c5
[ 1.338870] sp : ffffffc0fefc3f90
[ 1.338875] x29: ffffffc0fefc3f90 x28: ffffffc0fa7baa00
[ 1.338880] x27: ffffff8009e76000 x26: ffffffc0fefc4050
[ 1.338885] x25: ffffffc0fefc0060 x24: ffffffc0fa5d0000
[ 1.338889] x23: ffffffc0fa7cbe00 x22: 0000000000000000
[ 1.338893] x21: 0000000000000000 x20: 000000000000000a
[ 1.338897] x19: 000000000000000a x18: 0000000000000000
[ 1.338901] x17: 00000000000006ff x16: 0000000000000000
[ 1.338906] x15: 0000000000000010 x14: 0000000000d306be
[ 1.338910] x13: 0000000000000000 x12: 000000000011ca21
[ 1.338914] x11: 0000000000000400 x10: 0000000000000040
[ 1.338918] x9 : ffffff8009e94340 x8 : ffffffc0fa000000
[ 1.338922] x7 : ffffffc0fa000028 x6 : 0000000000000001
[ 1.338926] x5 : 0000ffc000000000 x4 : 000000000000000a
[ 1.338930] x3 : 0000000000000000 x2 : 0000000000000000
[ 1.338934] x1 : 000000000000000a x0 : 0000ffc000000001
[ 1.338935]
[ 1.338938] Process swapper/1 (pid: 0, stack limit = 0xffffffc0fa7c8000)
[ 1.338940] Call trace:
[ 1.338947] [<ffffff80084619a0>] __radix_tree_lookup+0x50/0xe0
[ 1.338953] [<ffffff80081205b8>] generic_handle_irq+0x28/0x50
[ 1.338956] [<ffffff8008120cb0>] __handle_domain_irq+0x68/0xc0
[ 1.338960] [<ffffff8008080d44>] gic_handle_irq+0x5c/0xb0
[ 1.338965] [<ffffff8008082c28>] el1_irq+0xe8/0x194
[ 1.338969] [<ffffff8008085960>] arch_cpu_idle+0x30/0x1b0
[ 1.338973] [<ffffff8008111358>] cpu_startup_entry+0x140/0x200
[ 1.338978] [<ffffff8008091cc8>] secondary_start_kernel+0x190/0x1f8
[ 1.338981] [<0000000084f6b1a4>] 0x84f6b1a4
[ 1.338990] ---[ end trace fd18cf8b2aad6719 ]---
[ 1.345699] Kernel panic - not syncing: Fatal exception in interrupt
[ 1.345705] SMP: stopping secondary CPUs
[ 1.345722] Kernel Offset: disabled
[ 1.345725] Memory Limit: none
[ 1.788535] Rebooting in 5 seconds..
Looks like doesn’t matter without the SPI or camera sensor driver cause the core dump.
Do have any others modification?
Yes. We have modified the device structure that is the issue. We fixed it. Thanks.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.