Skip to content

Bypass of spi_axis_reoder IP for Capture Zone 1 and SDI number 2 (ad4630) or 1 (ad4030) #1756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ladace
Copy link
Contributor

@ladace ladace commented Jun 12, 2025

PR Description

Removed spi_axis_reorder IP for ad4630 and ad4030 device with one SDI and Capture Zone 1 for Baylibres implementation of driver, this works only for NUM_OF_SDI 2 or 1

PR Type

  • Bug fix (change that fixes an issue)
  • New feature (change that adds new functionality)
  • Breaking change (has dependencies in other repos or will cause CI to fail)
  • Documentation

PR Checklist

  • I have followed the code style guidelines
  • I have performed a self-review of changes
  • I have compiled all hdl projects and libraries affected by this PR
  • I have tested in hardware affected projects, at least on relevant boards
  • I have commented my code, at least hard-to-understand parts
  • I have signed off all commits from this PR
  • I have updated the documentation (wiki pages, ReadMe files, Copyright etc)
  • I have not introduced new Warnings/Critical Warnings on compilation
  • I have added new hdl testbenches or updated existing ones

@ladace ladace force-pushed the dev_ad4630_no_reorder branch from 278af3e to 92fafe0 Compare June 12, 2025 08:43
@ladace
Copy link
Contributor Author

ladace commented Jun 12, 2025

V0:

  • Rebase to latest main

@ladace ladace force-pushed the dev_ad4630_no_reorder branch from 92fafe0 to 163149c Compare June 13, 2025 11:16
@ladace
Copy link
Contributor Author

ladace commented Jun 13, 2025

V1:

  • Updated READMEs
  • Added new parameter to optionally remove the spi_axis_reorder IP

@ladace
Copy link
Contributor Author

ladace commented Jun 13, 2025

V2:

  • Updated documentation

@ladace ladace marked this pull request as ready for review June 13, 2025 12:11
@ladace ladace self-assigned this Jun 13, 2025
@ladace ladace force-pushed the dev_ad4630_no_reorder branch from 78ca809 to a8d7821 Compare June 18, 2025 13:20
@ladace
Copy link
Contributor Author

ladace commented Jun 18, 2025

V3:

  • DMA_DATA_WIDTH_SRC different for 1 or 2 SDIs

@sarpadi
Copy link
Contributor

sarpadi commented Jul 2, 2025

Fix conflicts and update READMEs to include the new parameter

@@ -119,6 +119,15 @@ included in the SD card image that is provided with the evaluation board.
:align: center
:alt: AD4630_FMC SPI mode - transfer zone 1 block diagram

For 1 SDI (ad4030) or 2 SDIs (ad4630) a special mode can be build that bypass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo - bypasses

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

.. image:: ad463x_hdl_cm0_cz1_no_reorder.svg
:width: 800
:align: center
:alt: AD4630_FMC SPI mode - transfer zone 1 block diagram without spi_axis_reorder IP
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

without USING THE spi_axis_reorder IP

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Please enter the folder for the FPGA carrier you want to use and read the README.md.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for the FPGA carrier THAT you want

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

@ladace ladace force-pushed the dev_ad4630_no_reorder branch from a607fb8 to f6c0d23 Compare July 3, 2025 08:14
@ladace
Copy link
Contributor Author

ladace commented Jul 3, 2025

V4:

  • Fixed merge conflicts

@ladace ladace force-pushed the dev_ad4630_no_reorder branch from f6c0d23 to e9b7984 Compare July 3, 2025 09:50
@ladace
Copy link
Contributor Author

ladace commented Jul 3, 2025

V5:

  • Fixed remarks

@ladace ladace requested a review from sarpadi July 3, 2025 09:51
PIoandan
PIoandan previously approved these changes Jul 4, 2025
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the name of this configuration in the block diagram (under the diagram), as well as the name of the evaluation board (on top right corner).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment on lines 122 to 124
For 1 SDI (ad4030) or 2 SDIs (ad4630) a special mode can be build that bypasses
the spi_axis_reorder IP and connects the SPI Engine Offload directly to DMA.
For other number of SDIs this special mode is not expected to work.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For 1 SDI (ad4030) or 2 SDIs (ad4630) a special mode can be build that bypasses
the spi_axis_reorder IP and connects the SPI Engine Offload directly to DMA.
For other number of SDIs this special mode is not expected to work.
For 1 SDI (:adi:`AD4030`) or 2 SDIs (:adi:`AD4630`) a special mode can be built, that bypasses
the spi_axis_reorder IP and connects the SPI Engine Offload directly to the DMA.
For **other** number of SDIs, this special mode **is not expected to work**.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment on lines 22 to 23
Please enter the folder for the FPGA carrier you want to use and read the README.md. No newline at end of file
Please enter the folder for the FPGA carrier that you want to use and read the README.md.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert this change

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it is not according to the template, and that phrase is already grammatically correct as it is

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update the copyright range

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment on lines 41 to 42
NUM_OF_SDI = 1 (ad4030) or NUM_OF_SDI = 2 (ad4630) and directly connects the SPI
Engine to DMA
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NUM_OF_SDI = 1 (ad4030) or NUM_OF_SDI = 2 (ad4630) and directly connects the SPI
Engine to DMA
NUM_OF_SDI = 1 (ad4030) or NUM_OF_SDI = 2 (ad4630) and directly connects the SPI
Engine to DMA

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update the copyright range

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update the copyright range

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to add the description of this new parameter in the documentation as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@IuliaCMoldovan
Copy link
Contributor

Can you please update the title of the PR, to be clearer?
As well as the description of the PR, to offer more information.

ladace added 3 commits July 8, 2025 10:37
Remove reorder IP for the mentioned mode and number of SDIs and
connected the SPI Engine directly to DMA.
This will not work for other modes and number of SDIs.

Signed-off-by: Liviu 'Ceshu' Adace <liviu.adace@analog.com>
Signed-off-by: Liviu 'Ceshu' Adace <liviu.adace@analog.com>
Documentation update for the secial case where the spi_axis_reorder
IP is bypassed in Capture Zone 1 mode.

Signed-off-by: Liviu 'Ceshu' Adace <liviu.adace@analog.com>
@ladace
Copy link
Contributor Author

ladace commented Jul 8, 2025

V6:

  • Fixed remarks

@ladace ladace changed the title Dev ad4630 no reorder ad4630 (ad4030) bypass of spi_axis_reoder IP for Capture Zone 1 and SDI number 2 (ad4630) or 1 (ad4030) Jul 8, 2025
@ladace ladace requested review from IuliaCMoldovan and PIoandan July 8, 2025 08:14
@ladace ladace changed the title ad4630 (ad4030) bypass of spi_axis_reoder IP for Capture Zone 1 and SDI number 2 (ad4630) or 1 (ad4030) Bypass of spi_axis_reoder IP for Capture Zone 1 and SDI number 2 (ad4630) or 1 (ad4030) Jul 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants