The Industrial Raspberry Pi Forum

Hi, we got a failed RevPi connect 2019-03-14-revpi-stretch that returns no memory block with lsblk when connected to linux host.

When this happens, what would be the next step to diagnose the problem?

- flash image if possible (probably not as no phys memory is visible from OS)
- factory reset with some special procedure

Would you give us some insight how we handle the case?

Best,
- Josh

This is the self update to narrow down the root cause analysis.

I was able to locate the problem on built-in Raspberry Pi compute module 3+ 32GB by swapping it with the same module from another unit that worked fine. So it's somewhere in the OS bootstrap that won't complete.

Under the given condition how could I run diagnostics to know where it failed? The unit was working fine when shipped but returned due to solid A3 light. Otherwise we will hard-reset the module and initiate the fresh install.

In any case I would like to know how I should make the RevPi unit back to work.
- joshnn

This is from rpiboot that yields no accessible drive letters from Windows. Another screenshot after running rpiboot from device manager. Without USB mass storage accessible from OS I firstly want to hear some specialist's insight if this hardware is good enough for eMMC flash attempt.
- joshnn

Replaced Compute Module 3+ with the equivalent and it was recognized as USB Mass Storage Device. Seems our case was broken storage on built-in CM3+ possibly after a few months of field use.

I got the second RevPi Connect+ returned from a field deployment that has the same point of failure - storage not recognized as Mass Storage Device. I am wondering if CM3+ (32GB) fails as easy as this often.

Hi joshnn, I am devastated to hear this. I will contact you via email.