Flashing jetpack and Econ camera drivers complications

Hi,

We are trying to flash Econ camera drivers (3.4mp e30 6 mipi CSI camera) and jetpack to our tx2.
Both needs to be flashed to tx2.
But while flashing, it wipes out the previous flash. (ie, if we flask camera module first, the jectpack removed the camera module and same the other way too)

If anyone had similar problem, please help and suggest any work around.

Thanks.

hello shubham.borikar,

the complete flashing process will wipe the eMMC.
you need to have partial update, especially kernel and device tree partition,
please refer to Flashing a Specific Partition session for the command and descriptions.
thanks

Hi shubham.borikar,
Can you tell me which jetpack version used for this e-con 3.4mp 6 cameras product?

If you are using correct jetpack ie. released for this e-CAM30_HEXCUTX2 product then just go through the “Upgrade procedure” section in Developer guide document.

Thanks

Hi Ritesh

Shubham has tried with Jetpack3.0 and 3.2 version but to no avail. I have read in various forums that this is a known issue. Can you let me know if any solution is there?

Thanks

Hi ar00555681,
Can you please explain the problems in details.
Are you trying 2 jetpack version in same TX2 board or you have tried jetpack 3.0 and 3.2 version one by one?

The latest release for e-CAM30_HEXCUTX2 product is Jetpack 3.2.1.

Regards,
Ritesh

Hi Ritesh

We flashed jetpack 3.2.1 then we tried flashing camera(ecam 30) module, after which my flashed jetpack crashed.
Again we repeated the process with jetpack 3.0 and the outcome was same.

We also tried with flashing the camera module first and then flashing jetpack 3.2.1 but to no avail.

Thanks

Hi ar00555681,
Yes, you are flashing correct jetpack which is 3.2.1 for this e-CAM30_HEXCUTX2 release.
After flashing jetpack 3.2.1 please follow the “Upgrade Procedure” section in Developer guide document for flashing and updating kernel image, device tree and kernel modules.

If still face the same problems then please send dmesg log or crashing log for identify the actual problem.

Regards,
Ritesh