Electronics > Repair

CMU200 Rohde & Schwarz hangs during BaseDiscoverOptionsBegin

<< < (9/9)

sardonyx:
I have a few questions. Does anyone know the pinout of the main connectors and two additional unpinned ones on this board? Is it possible to move the TXDSP board on the main board to the left or right? It seemed to me that this was possible. But I haven't tried it yet

How do you know if the FPGA is showing signs of life? (I've never encountered them). The complexity of all debugging manipulations lies in the fact that there are no extension cords to place the DIG board on the table...

RaspII:
Hello all,
hope this post is still active.
I also have the boot problem (Error #1095, overlay.c) sporadically.
Sporadically means if the error is available I have to boot for up to 10 times until error is gone.
If the error is not avialable I can boot several times without any issue.
So I checked IDE cable, but no issue there.

Some more information:

* I own this device since 2024-12-20
* the error occured the first time after replacing HDD with SDD. So my idea was to swap SDD with HDD again. First tests with replaced HDD shows the CMU-200 boots without any error (but only few tests done)

Im wondering about the HDD itself. It's an Fujitsu MHW2060AT which should have the size of 60GByte.
But when connecting this HDD to a Windows10 PC the system shows 2GB  of HDD is used,  25,94GByte unused. That means about 33GB are missing (not shown?, hidded?).

The 1:1 copied SSD (64GB) shows 2GB used and 57,63 unused (as expected).

I don't have an idea why there is a different usage (HDD/SDD) but I have the feeling this could be the reason for the overlay.c error.

 
 

squadchannel:
Is it Win2K/9x or WinCE?
if it is FAT16, the maximum partition capacity is 2GB, which seems normal. I think the problem maybe bad sectors, etc.

I missed it "bar" photo, it is FAT16, so 2GB is normal.

let's backup with the DD command and then think about it. First, the backup.

if there is a firmware updater for CMU200, it may be possible to extract and restore system from updater file.


Well, I calmed down and looked over this topic.

It is very likely a hardware failure.
If it happens from time to time, it is likely that the problem is not in the HDD, but in the memory, etc.

power supply is also a strong possibility.

RaspII:
I did the backup with the "HDD Raw Copy Tool". What exactly do you mean with the "DD Command" ? Edit: do you mean the Linux DD command? (I did all my work on a Windows10 PC so far)
As far as I know I don't own a firmware updater for CMU200.

In regard to HW issue: yes, the HW is really a candidate.
Nevertheless I'm wondering that I never got this bug with the HDD, originally shipped with the CMU-200 (Up to now I have about 30 boot cycles without any error. Maybe the SDD is more sensible in regard to stable power supply... 

RaspII:
I did some more tests.
Added a new SDD (SanDisk X110 mSATA 32GB ,same mSATA to PATA Converter).
With this SSD every boot ended with Error #1095, overlay.c  (could not achive one ok boot cycle).
After going back to the orignal HDD (see above) no more error.
So I'm now pretty sure, that the SSD itself or mSATA to PATA converter is the root cause for Error #1095, overlay.c.
Does anybody knows what this "overlay.c" is made for?
73 

Navigation

[0] Message Index

[*] Previous page