Re: EM100Pro-G3 sporadically stops working

Corvin Köhne <[email protected]> Wed, 6 Mar 2024 13:20:46 +0000
Newsgroups	gmane.linux.bios
Message-ID	<[email protected]>
On Mon, 2024-03-04 at 14:43 +0100, Corvin Köhne wrote:
> Hi,
> 
> I'm currently having some issues using the new EM100Pro-G3 and would
> like to know if someone has seen such issues before and may have a
> solution.
> 
> The EM100Pro-G3 sporadically stops working properly. I can reproduce
> the issue within a few minutes by running the following steps in a
> loop:
> 
> 1. power off the board
> 2. em100 \
> 	--device EMxxxxxx \
> 	--stop \
> 	--set <chip> \
> 	--download <rom> \
> 	--verify \
> 	--start
> 3. power on the board
>    * the board is configured to netboot a linux
> 4. wait until linux is reachable by ssh
> 5. goto 1
> 
> After some iterations, the board isn't able to boot any more. Even if
> I
> power cycle the board, it doesn't boot. It doesn't even reach it's
> first POST. Reloading the ROM into the EM100 (repeating step 2),
> solves
> the issue.
> 
> I'm currently trying to gather more information about the issue. What
> I
> do know right now:
> 
> 1. Reloading the ROM without physically touching anything solves the
> issue. 
> 2. It doesn't matter if I connect the USB connector + power adapter
> or
> only the USB connector to the EM100Pro-G3.
> 3. I've recently exchanged the EM100Pro-G3 with the older EM100Pro-
> G2.
> The board is running fine for several hours right now without any
> issues.
> 4. If the board is unable to boot, `em100 --device EMxxxxxx --trace`
> does return some data.
> 
> I don't think it's a physical issue, e.g. signal integrity issue, as
> I'm not touching the whole system (see 1 + 2). I also don't think
> that
> it's a sporadic issue of my ROM file as it's working with the old G2
> (see 3). Maybe the ROM isn't loaded correctly into the EM100 which
> causes it to return wrong data (see 1 + 4)?
> 
> As said, the board is currently connected to a G2. I'm going to keep
> this test running for a while. If I can't reproduce the issue on the
> G2, I'm going to switch back to the G3 and try to gather some more
> information. What I'm going to check next is if the ROM returned by
> `em100 --device EMxxxxxx --upload <rom>` matches the desired ROM.
> 
> Any help how to debug or solve this issue is highly appreciated!
> 
> 

Hi,

I've forgot adding the firmware versions of my EM100 in case it
matters:

MCU version: 3.10
FPGA version: 3.018
Hardware version: 0
SPI flash database: EM100Pro_4.3.22

Meanwhile, I've used `em100 --device EMxxxxxx --upload <rom>` to
compare the loaded ROM to the expected ROM. They are the same.

I've also tried to compare the FPGA register of the functional and non-
functional state of the EM100 using `em100 --device EMxxxxxx --debug`.
I can't see any relevant differences.


-- 
Kind regards,
Corvin

_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
signature.asc (application/pgp-signature, 833 B)