Mity CPU Platforms » MitySOM-5CSX Altera Cyclone V

Hi Atef,

Thank you for the thorough debug details.

1. Have you successfully used this development kit before? Or are these the symptoms you are experiencing after first receiving this development kit?
2. Could you provide the serial of both the SOM and development board which are experiencing these issues?

There appears like there are multiple issues going on from your boot log. The I2C bus is unhappy as well as the FPGA is failing to load. My guess is since the FPGA doesn't load it is causing the Kernel to hang on start-up.

I would try the following to further debug:

1. I would first try to just re-seat the SOM module. Take the SOM module out of the DIMM connector and put it back in. See if this helps resolve any issues. If it does not, proceed to step 2 below.
2. I would try to swap the SOM modules between development kits to see if the issue tracks the SOM.

- Mike

​[https://res.public.onecdn.static.microsoft/assets/mail/file-icon/v2/photo_16x16.png]1000008159.jpg<https://sascailabs-my.sharepoint.com/:i:/g/personal/atef_dorai_cailabs_com/EfLXHLTfMzNHoDiG-PRr9sMBAmPRqgLMED5K8e0Jwf8zUg>​
​[https://res.public.onecdn.static.microsoft/assets/mail/file-icon/v2/photo_16x16.png]1000008160.jpg<https://sascailabs-my.sharepoint.com/:i:/g/personal/atef_dorai_cailabs_com/ESJeeg5Wq4JFifEO2VQ9xGcB1qkrmHPL_BrOS1egONcK6A>​
Hi Mike,

Thnaks for your quick reply.
Here’s what I’ve tried and what I’m seeing:

*
Reseated the SOM in the DIMM connector → same behavior as before.
*
Swapped SOMs between kits → when I install the good SOM into the known-problematic carrier, the binary runs and I get the expected results.
*
For the original kit with issues, this behavior has been present since we received it. I moved on to using the second kit because it works as expected.

I’ve attached the serial numbers for both the SOM and the development kit.
Given the above, could you advise on the next steps to reset/recover the SOM (if there’s a recommended procedure)? If a reset isn’t applicable, can we proceed with an RMA for the affected unit?
Thanks again,
Atef DORAI

[My Logo]

[https://storage.letsignit.com/5aabe32dd0815b00057fdca2/generated/effects_cb05164a06bdf24c4b230354c985dd9f4cf37435b339759bd001a6b4.png]<https://cloud.letsignit.com/collect/bc/64abf1e9cb21ef2b89a0417e?p=yle9ZRCDvqnpSy3PfzIFzu8hB_PIIEYM5S8vWCBVu1zL3yU0Oa7N3tYhHc2hNgFidkH7w4fX_Y8Bym0pABHndUeJLeCbA6VjiBw4QljAIyOR6RsDsSiPy5I-Qbe0z6RkjCUJhf49y_oC3F0EgRmfyA==>

[https://storage.letsignit.com/5aabe32dd0815b00057fdca2/generated/effects_9abbd9edcbe0df6504030656de400259bd8661d97228952db2fedef8.png]<https://cloud.letsignit.com/collect/bc/64abf1e9cb21ef2b89a0417e?p=yle9ZRCDvqnpSy3PfzIFzu8hB_PIIEYM5S8vWCBVu1zL3yU0Oa7N3tYhHc2hNgFidkH7w4fX_Y8Bym0pABHndeU_z5ON46A5aOWtw6zRNVyvy0pX9yNRttpPsNkQHYPOH_CUFPvdeeb__ZkqPQWhYxQTTmPUjJGaiVnQ6FKPiPw=>

[Youtube]<https://cloud.letsignit.com/collect/bc/64abf1e9cb21ef2b89a0417e?p=yle9ZRCDvqnpSy3PfzIFzu8hB_PIIEYM5S8vWCBVu1zL3yU0Oa7N3tYhHc2hNgFidkH7w4fX_Y8Bym0pABHndeU_z5ON46A5aOWtw6zRNVxMxf3QTRvTdBXORCpMWFyh0_RDSINO3GDsWERPHSeQKHKvDS1mA5HkX7A9qxE2Jqg=>

Atef Dorai

FPGA Development Engineer

+33 (0)6 77 14 21 42

1 Rue Nicolas Joseph Cugnot

35000

Rennes

France

Hi Atef,

It sounds like based on your findings the SOM module is the issue. It looks like you may have tried to reply to this post via email, which I do not think works for attachments. Can you either reply again and type the serial numbers as text or attach your files directly to the forum post.

There isn't necessarily a reset procedure for the SOM, as nothing is actually stored on the SOM itself (with the exception of the EEPROM which stores the serial / module number information). But your I2C bus to that EEPROM doesn't appear to be working anyways. I will follow up with you on steps for RMA after I've received the serial number for the module.

- Mike