modules: hal: mchp sam: Add SAMA5D2 and SAM9X7 header files

[TonyHan11]

changes in this PR includes:

• add header files and ATDF files for sama5d2 SoCs
• update CMakeLists.txt accordingly

[TonyHan11]

ping @nandojve

[TonyHan11]

Hi @NhMchp ,

Would you like to help merging the commits in this PR for solving the CI failures related with pic32cx_sg61_cult/pic32cx1025sg61128 in zephyrproject-rtos/zephyr#103557? Thank you very much.

[NhMchp]

Hi @NhMchp ,

Would you like to help merging the commits in this PR for solving the CI failures related with pic32cx_sg61_cult/pic32cx1025sg61128 in zephyrproject-rtos/zephyr#103557? Thank you very much.

@TonyHan11 , Could you please share details of failures related to pic32cx_sg61_cult/pic32cx1025sg61128 ?

[TonyHan11]

Hi @NhMchp ,
Would you like to help merging the commits in this PR for solving the CI failures related with pic32cx_sg61_cult/pic32cx1025sg61128 in zephyrproject-rtos/zephyr#103557? Thank you very much.

@TonyHan11 , Could you please share details of failures related to pic32cx_sg61_cult/pic32cx1025sg61128 ?

https://github.com/zephyrproject-rtos/zephyr/actions/runs/21930226291/job/63332687272?pr=103557#step:13:1498

In zephyrproject-rtos/zephyr#103557, the hal_microchip reversion is pull/49/head. The failure is caused by some commits in the master branch of hal_microchip which are related to pic32 is not included.

It's better to update the reversion to the hash value after the merge. It might be solved by using pull/49/merge too.

[nandojve]

Hi @NhMchp ,
Would you like to help merging the commits in this PR for solving the CI failures related with pic32cx_sg61_cult/pic32cx1025sg61128 in zephyrproject-rtos/zephyr#103557? Thank you very much.

@TonyHan11 , Could you please share details of failures related to pic32cx_sg61_cult/pic32cx1025sg61128 ?

https://github.com/zephyrproject-rtos/zephyr/actions/runs/21930226291/job/63332687272?pr=103557#step:13:1498

In zephyrproject-rtos/zephyr#103557, the hal_microchip reversion is pull/49/head. The failure is caused by some commits in the master branch of hal_microchip which are related to pic32 is not included.

It's better to update the reversion to the hash value after the merge. It might be solved by using pull/49/merge too.

To avoid this situation we should merge the HAL content only when the PR in zephyr side is ready. This is the only way to keep HAL and Zephyr content sane due to the number of activity in parallel.

[NhMchp]

Hi @NhMchp ,
Would you like to help merging the commits in this PR for solving the CI failures related with pic32cx_sg61_cult/pic32cx1025sg61128 in zephyrproject-rtos/zephyr#103557? Thank you very much.

@TonyHan11 , Could you please share details of failures related to pic32cx_sg61_cult/pic32cx1025sg61128 ?

https://github.com/zephyrproject-rtos/zephyr/actions/runs/21930226291/job/63332687272?pr=103557#step:13:1498
In zephyrproject-rtos/zephyr#103557, the hal_microchip reversion is pull/49/head. The failure is caused by some commits in the master branch of hal_microchip which are related to pic32 is not included.
It's better to update the reversion to the hash value after the merge. It might be solved by using pull/49/merge too.

To avoid this situation we should merge the HAL content only when the PR in zephyr side is ready. This is the only way to keep HAL and Zephyr content sane due to the number of activity in parallel.

I see the issue related to pic32cx is fixed in the latest of master branch. I think, it will be resolved if you could rebase the branch to latest of master.

[TonyHan11]

I see the issue related to pic32cx is fixed in the latest of master branch. I think, it will be resolved if you could rebase the branch to latest of master.

Hi @NhMchp ,

Temporarily solved by using pull/49/merge in the PR. Thanks.

Do you know who would handle the hal_microchip merge action?

[nandojve]

Hi @TonyHan11 ,

What should the merge sequence in zephyr and when the HAL content will be need to build and pass in the tests?