Management of non-intelligent RTM

Hi,

For our project, we would like to manage a non-intelligent RTM. How do we go about this?
Can we use the pin groups assigned to AMC slot 8 to manage the hotswap controller of the non-intelligent RTM?

Best regards,

Fatih

Hello Fatih,

the XML scheme currently only supports intelligent RTMs (like AMCs). However, the PigeonPoint software framework also provides support for non-intelligent RTMs, but we have not yet used this feature. We do however also have a module being designed now where we are planning to use a non-intelligent RTM.

You can indeed use the signals from AMC slot 8 for the hot-swap controller. However, the non-intelligent RTM needs some additional signals, since the IPMC now must take over some of the functions that are handled by the MMC on an intelligent RTM. These are the following:

  • Handle switch on the RTM
  • Blue LED enable
  • Other FRU LEDs (if required)
  • Reset signal to the RTM (if required)
  • An I2C EEPROM on the RTM for the FRU information. It may be possible to use the EEPROM on the main blade for this, but we would have to double check this if it is of interest.

You can use any of the USR or IPM I/O signals for the additional signals. Let us know if you have any questions.

cheers,
Stefan

Hi Stefan,

Just to clarify things regarding the non-intelligent RTM, we can therefore use the AMC slot 8 signals to manage the Hot-Swap controller. My question is, are we able to use IPMB-L signals from the AMC slot 8 to read/write EEPROM on the non-intelligent RTM, and how do we proceed to define this non-intelligent RTM in the IPMC code?

Thanks,

Fatih

Hello Faith,

yes, you can use the hot-swap signals from AMC port 8 for the non-intelligent RTM, have a look in the hardware guide here on page 6:

https://cernbox.cern.ch/pdf-viewer/eos/project/c/cern-ipmc-support/public/CERN-IPMC%20-%20hardware%20guide.pdf

Also connect IPMB-L to the RTM through a. hot-swappable I2C buffer as shown there. On the RTM you should connect the EEPROM and any I2C sensor devices you may have to this bus. And you also need the addition signals I mentioned in my previous message (handle switch, blue LED, etc).

As I said previously, the XML scheme does not yet include the settings for non-intelligent RTMs, this still needs to be added. However, enabling support for these in the Pigeon Point software framework only requires some #define statements. If you need a working IPMC firmware urgently, we can work with you to tailor these to your needs until the XML support is ready.

Having said this, I am currently on vacation (until end of July), however I’m sure Markus or Ralf can assist you if needed.

cheers,

Stefan

Hello Markus and Ralf,

The answer regarding the IPMB-L is not clear to us. So let me rephrase my question.

Knowing that we will have a non-intelligent RTM, therefore without MMC, the IPMB-L bus is not used in this case.
Our question is: can we connect IPMB-L directly to the RTM’s EEPROM and does the Pigeon Point software framework support this?

Otherwise, we’ve also thought of putting a second EEPROM on the Blade dedicated to the non-intelligent RTM. This EEPROM would be connected to the Mgt I2C bus, what do you think?

Cheers,

Fatih

Dear Fatih,

I am afraid that I am not knowledgeable enough to answer your question. I propose to wait until Stefan comes back.

Cheers,
Ralf.

Hello Fatih,

Knowing that we will have a non-intelligent RTM, therefore without MMC, the IPMB-L bus is not used in this case.

So you don’t have any I2C sensor devices on the RTM either? A non-intelligent RTM can have these, but they are handled by the IPMC instead of an MMC.

Our question is: can we connect IPMB-L directly to the RTM’s EEPROM and does the Pigeon Point software framework support this?

If there is no need for an I2C bus to the RTM, the this should work.

Otherwise, we’ve also thought of putting a second EEPROM on the Blade dedicated to the non-intelligent RTM. This EEPROM would be connected to the Mgt I2C bus, what do you think?

I believe this should also work, but we would like to confirm this with PigeonPoint support first. As I said before, you are the first user of a non-intelligent RTM.

cheers,

Stefan

Hello Fatih,

we confirmed with PigeonPoint: the EEPROM with the RTM FRU information can also reside on the front blade. It can be attached to any of the local I2C busses of the IPMC. If you already have an EEPROM on the board with enough space, this can even be shared with the RTM FRU information by using an address offset.

BTW, I am available to look at the IPMC part of the hardware design once it is done.

Best regards,

Stefan

Hello Stefan,

Thanks for the clarification. We have decided to add a second EEPROM to our board.

Cheers,

Fatih

Dear Support Team,

I wish you a happy new year 2025.

I’m coming back to you because we are about to start production of our non-intelligent RTM boards.

Have you had time to include the settings for non-intelligent RTMs in the XML schema?

If not, could you describe us how to set the necessary #define statements?

Cheers,

Fatih

Dear Support Team,

I’m coming back to you again, have you made any progress on this topic?

Cheers,

Fatih

Hello Fatih,

I am working on this, however I need to know which IPMC pins are connected to the RTM to finalize it. Are the schematics of the main blade and the RTM available?

cheers,

Stefan