SOLVED Direct download img from baidu
-
@veye_xumm I also have tried from host:
copy dtb to kernel/dtb
sudo ./flash.sh -r -k DTB jetson-nano-qspi-sd mmcblk0p1
from L4T but nothing, /dev/video0 is not present.About system:
cat /etc/nv_tegra_release
R32 (release), REVISION: 4.4, GCID: 23942405, BOARD: t210ref, EABI: aarch64, DATE: Fri Oct 16 19:44:43 UTC 2020number@number:~$ dpkg-query --show nvidia-l4t-core
nvidia-l4t-core 32.4.4-20201016124427Bsp from here:
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/Nano/JetPack_4.4.1_Linux_JETSON_NANO_DEVKIT/dts dtb/VEYE-MIPI-327
Kernel from here:
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/blob/master/kernel_image/Image_l4t_r32.4.4_veyecam.tar.gzSo, please tell me how to repair Veye327 system after ubuntu software update?
-
@veye_xumm Here is screenshot, after fresh installation, ubuntu wants 600mb updates, include nvidia l4t4.4: cam360.tv/etc/43-44.jpg
So i need to update system without reflash as on other native jetson platforms.
Please help.
-
@viktor
If you want to upgrade new version of L4T, I suggest you upgrade the system first, then do our VEYE bsp upgrade.
This is the list of version we provide:Jetpack4.2.2,L4T r32.2.1 Jetpack4.3,L4T r32.3.1 Jetpack4.4,L4T r32.4.3 Jetpack4.4.1,L4T r32.4.4 Jetpack4.5,L4T r32.5 Jetpack4.5.1,L4T r32.5.1
About your failure here:
@viktor said in Direct download img from baidu:
@veye_xumm Hi, have tried.
cat /etc/nv_tegra_release -> r32, 4.4
Download Image and dtb.
Copy to /boot
Edit /boot/extlinux/extlinux.conf -> FDT /boot/dtb fileAnd now i have nvidia logo only and loop reboot.
My system nano b01, imx327.
Please check the dtb file name and the line you add in /boot/extlinux/extlinux.conf, they must be the same.
-
Have build 4.5.1 from scratch and it works.
About upgrade.
Can i apply VEYE image/drivers without reflash and changing /app/home partition? -
-
@veye_xumm Yes. It was first method what i did, but it does not work for Nano. Fdt line brokes system.
-
@viktor
pls paste your fdt line here. It must be wrong. -
-
@viktor
I think this line is correct.
It's very strange. It works normally in my place. -
@veye_xumm ok. Will try again.