Update FRAMOS-IMX415 to IMX678 documentation

[martinaxgloria]

Since the FRAMOS-IMX415 sensors are obsolete, we decided to substitute them with the FRAMOS-IMX678:

• iCubHeadEdge – Investigate about the feasibility of substituting the FRAMOS IMX415 with the IMX678C study-icub-headedge#235

With this PR, the documentation about the sensors and how to properly install and configure them is updated

[gemini-code-assist]

Summary of Changes

Hello @martinaxgloria, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on updating the project's documentation to reflect a significant hardware change: the replacement of obsolete FRAMOS-IMX415 camera sensors with the newer FRAMOS-IMX678 models. The changes involve creating a new, detailed setup guide for the new sensors and updating all existing references and links across various documentation files to ensure accuracy and provide correct instructions for installation and configuration. This ensures that users have up-to-date information for deploying and working with the current hardware.

Highlights

• Documentation Update: I've updated all relevant documentation to reflect the transition from obsolete FRAMOS-IMX415 sensors to the new FRAMOS-IMX678 sensors, ensuring accuracy and consistency across the guides.
• New Setup Guide: A comprehensive new guide (docs/icub_operating_systems/icubos/setup-framos-imx678.md) has been added, detailing the installation and configuration steps for the FRAMOS-IMX678 cameras with the NVIDIA Jetson Orin NX.
• System Compatibility Updates: The jetpack.md documentation now reflects updated Jetpack (6.2) and Ubuntu (22.04) versions for the Orin NX, aligning with the latest supported configurations.
• iCub Version Specification: The iCub head v2.10 specification in docs/icub_versions/index.md has been corrected to accurately list the new FRAMOS-IMX678 cameras.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request updates the documentation to reflect the change from FRAMOS-IMX415 sensors to FRAMOS-IMX678 sensors. The documentation covers the installation and configuration of the new sensors. There are a few minor issues that need to be addressed, such as a typo and ensuring that the documentation is clear about which camera connectors are enabled for the new configuration.