Post Go back to editing

#adin3310 SES AddDevice error -1

Category: Software

Hello,

I am trying to configure the ADIN3310 Ethernet switch using the SPI interface. I built the **ses-example-app** through cross-compilation on my Ubuntu host system, targeting a custom board based on the Kria K26 SoM running PetaLinux.

After successfully building the application, I transferred the executable to the target board and attempted to run it with the following command:

sudo LD_LIBRARY_PATH=/home/petalinux/adin3310/deploy_libs ./ses-example-app -f example-eval-6310.xml -g /dev/gpiochip0:5 -p /dev/spidev3.0 -m sysrepo-glue-srv/modules/ -s 1 -i production -l

The application starts but fails during initialization with the following output:

Interface Information:
-- /dev/spidev3.0, /dev/spidev1.0

Board settings file is located at example-eval-6310.xml
Yang modules folder sysrepo-glue-srv/modules/
libyang[0]: Value "00" was not found in the dictionary.
libyang[1]: String "00" not freed from the dictionary, refcount 1
Device MAC: 00:E0:22:12:34:56
Init with device on: /dev/spidev3.0 ready_pin:/dev/gpiochip0:5 speed:16000000
SES AddDevice error -1

The failure occurs during the device initialization step (SES AddDevice error -1). SPI pin strapping is configured correctly, but no pulses are observed on Timer0. A dummy MAC address is used in the XML file. I am not sure whether this is related to SPI communication, GPIO configuration, device tree settings, or the libyang/sysrepo setup.

Could you please help identify what might be causing this issue and what I should check or modify to resolve it?

Thank you.

Thread Notes

Parents
  • Hello Kiranmaye,

    Apology for the slow response.

    The behavior of the interrupt pin will change once the firmware is flashed or loaded. In the absence of firmware, the interrupt pin is expected to go high for approximately 1.25 seconds and low for about 2ms.
    Could you confirm whether the firmware was flashed/loaded using the evaluation application or via the driver API?

    For SPI communication, the switch operates as an SPI receiver, and the interrupt pin is asserted only when there is a response from the switch to the host. Therefore, this behavior is expected in such cases.

    Do you have any logic analyzer captures while running the application? If so, please share them. Also, kindly provide your porting layer for further review to adin6310@analog.com.

    Regards,
    Himanshu

Reply
  • Hello Kiranmaye,

    Apology for the slow response.

    The behavior of the interrupt pin will change once the firmware is flashed or loaded. In the absence of firmware, the interrupt pin is expected to go high for approximately 1.25 seconds and low for about 2ms.
    Could you confirm whether the firmware was flashed/loaded using the evaluation application or via the driver API?

    For SPI communication, the switch operates as an SPI receiver, and the interrupt pin is asserted only when there is a response from the switch to the host. Therefore, this behavior is expected in such cases.

    Do you have any logic analyzer captures while running the application? If so, please share them. Also, kindly provide your porting layer for further review to adin6310@analog.com.

    Regards,
    Himanshu

Children
No Data

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.