No SPI MISO Activity on M40 Profinet IRT Module with TWR-ABCC

Répondu

Laura Sastre

• 4 juillet 2024 07:34

Good day,

We are encountering an issue with our SPI communication: there is no activity on the MISO line. We suspect this might be due to a misconfiguration of our M40 Profinet IRT module.

Our setup includes:

• TWR-ABCC SPI interface board
• NUCLEO-H753ZI development board from ST Microelectronics
• HAEC example code and the appl_adimap_speed_example.c application

We have kept the SPI settings as per the default configuration for the HAEC project. In our modifications to the abcc_drv_cfg.h file, we have set ABCC_CFG_POLL_ABCC_IRQ_PIN, ABCC_CFG_INT_ENABLED, and ABCC_CFG_MOD_DETECT_PINS_CONN to FALSE, as the initialization does not proceed otherwise. Additionally, we have set the operating mode to SPI.

We observe that APPL_CyclicalProcessing() is reached, but ABCC_AnbState() always returns the default value of ABP_ANB_STATE_SETUP. The MS LED on the CompactCom M40 Profinet IRT module is lit, along with the activity LEDs on the RJ45 interface with a connector plugged in. The jumpers, hex knobs, and DIP switches on the TWR-ABCC board are set to their factory configuration, except for OM3, OM2, OM1, and OM0, which are set to 0 0 0 1 to operate in SPI mode.

Our main issues are:

1. What are we missing in the initialization process for the module?
2. Why do we not see any activity on the SPI MISO line?

Your assistance in resolving these issues would be greatly appreciated.

Yours sincerely,

0

• Commentaire officiel

  

  ALK

  • 16 juillet 2024 06:53

  Hi Laura,

  glad to hear that you succeeded in initializing the ABCC40 to WAIT_PROCESS state.  It is in this and in PROCESS_ACTIVE state (apart from IDLE) that the Ethernet transceivers are activated, and the module can be detected by the network.

  For a transition to PROCESS_ACTIVE, you'll need to establish a connection with a PROFINET IO Controller.  Prior to that, a GSD file adapted for your application is necessary.  I recommend using the HMS GSD Generator.

  Alternatively, you may use the HMS PROFINET Master Simulator where you can use your PC as an IO Controller for test purposes.  Unfortunately, you'll need to purchase a license for it.
• 

  ALK

  • 12 juillet 2024 09:10

  Hello Laura,

  I apologize for the late response.

  Your observations are somewhat contradicting.  On one hand, you state that there is no SPI response from the ABCC (it is still in state SETUP), on the other the module's MS LED is lit and there's activity on the Ethernet.

  Can you doublecheck your hardware settings for both the Nucleo and the TWR_ABCC board by means of the file /Doc/jumpers.txt that is part of the nucleo-h743zi2_m00765_xxx port with the ABCC driver?

  0
• 

  Laura Sastre

  • 15 juillet 2024 09:21

  Hey Alk!
  
  Thank you for your answer.
  Quick update on my issue with the M40 Profinet IRT module and TWR-ABCC.

   

  Reading through jumpers.txt, the jumpers on the board are as announced, JP12 to JP14, J20 to J22 unpopulated and the operating mode dip switch set for SPI (0001). The only power supply is the USB port from the nucleo board.

  I've got the HAEC console up and running, and I've noticed a couple of things:

  1. The activity LED might be lit due to foreign activity from other devices and the presence of a switch.
  2. I have been able to initialize the module but I'm currently stuck in the ABP_ANB_STATE_WAIT_PROCESS state and not sure what conditions are needed for the module to switch to ABP_ANB_STATE_PROCESS_ACTIVE.

  Here's my setup so far:

  • Configured TIA Portal with the ADI_SPEED_EXAMPLE GSD file.
  • Both IPs are set up and devices connected.
  • I can upload firmware to the M40 module and make its NS LED blink via TIA Portal's Online & diagnostics page.

  Console Output:

  ANB_STATUS: ABP_ANB_STATE_SETUP
  RSP MSG_DATA_FORMAT: 1
  RSP MSG_GET_PARAM_SUPPORT: 1
  RSP MSG_GET_MODULE_ID: 0x403
  RSP MSG_GET_NETWORK_ID: 0x89
  RSP MSG_GET_FW_VERSION: 2.10.1
  RSP MSG_MAP_IO_****
  RSP MSG_MAP_IO_****
  RSP MSG_SETUP_COMPLETE
  Mapped PD size, RdPd 2 WrPd: 2
  ANB_STATUS: ABP_ANB_STATE_NW_INIT
  ANB_STATUS: ABP_ANB_STATE_WAIT_PROCESS

  Looking for some guidance on:

  1. What needs to happen for the module to transition from ABP_ANB_STATE_WAIT_PROCESS to ABP_ANB_STATE_PROCESS_ACTIVE?
  2. Maybe setting up an alternative PROFINET master in Windows to be able to test the examples from HAEC.

  Thanks in advance for any help!

  0

Vous devez vous connecter pour laisser un commentaire.