el00
Member level 5
Hello, I developed a board with an FPGA and a 1GB PHY. The 1GB autonegotiation is OK, and the board is only transmitting data in streaming, there is no need to receive in this application.
The stack is not a standard TCP one, but it is a reduced customized stack that only sends packets blindly, without checksum.
What happens is that we get some errors (10% of data are corrupted) in the transmission, therefore we think that the problem is in the RGMII interface.
Now, my qyestion is: what hardare tools are necessary to debug such an hardware? Suppose that we want to buy a 6GHz scope, not on purpose for this, but also for other reasons so that we invest the money in something that is useful for other lab jobs, would it be the best choice or there might be some more dedicated hardware?
What is normally done in these sistuations? It's the first time we develop for Gigabit, and give the shortage we cannot make too many tests, and evaluation boards are out of stock.
However, for this particular chip we have some stock, but before repeating the same mistakes we need to understand what is going on. Thanks.
The stack is not a standard TCP one, but it is a reduced customized stack that only sends packets blindly, without checksum.
What happens is that we get some errors (10% of data are corrupted) in the transmission, therefore we think that the problem is in the RGMII interface.
Now, my qyestion is: what hardare tools are necessary to debug such an hardware? Suppose that we want to buy a 6GHz scope, not on purpose for this, but also for other reasons so that we invest the money in something that is useful for other lab jobs, would it be the best choice or there might be some more dedicated hardware?
What is normally done in these sistuations? It's the first time we develop for Gigabit, and give the shortage we cannot make too many tests, and evaluation boards are out of stock.
However, for this particular chip we have some stock, but before repeating the same mistakes we need to understand what is going on. Thanks.