search

ucsdsysnet / sparsdr

68 stars 10 forks source link

Ethernet does not work #34

Open lobart opened 1 year ago

lobart commented 1 year ago

Hi How i can turn on ethernet on sparsdr?

samcrow commented 1 year ago

Can you please explain more about what you are trying to do?

Are you using a USRP N210 or a Pluto?

lobart commented 1 year ago

@samcrow hi I am using Pluto plus I build firmware after applying patches, and I try to start eth connection by ssh over usb, but there are not any devices eth0

samcrow commented 1 year ago

That is a surprising problem. Our patches should not change anything about USB or networking.

Does everything work using a normal image on the Pluto?

The pages linked from the Pluto quick start guide might help: https://wiki.analog.com/university/tools/pluto/users/quick_start

lobart commented 1 year ago

@samcrow Yes, i got v0.33 plutosdr-fw and apply patches from https://github.com/plutoplus/plutoplus/tree/master/patches Then i apply patches from this repo, then i build firmware and copy .frm files to PlutoSDR. And block compressing pluto source run with next error. image I attached plutos dmesg and building log vivado. vivado.log dmesg.log

samcrow commented 1 year ago

Thanks for the details; this makes more sense now.

I've only tested SparSDR with a normal Pluto and based on the normal firmware from Analog Devices. The Pluto+ looks interesting, but since I've never tried it I may not be able to help very much.

These lines from the dmesg log look important:

ad9361 spi0.0: ad9361_dig_tune_delay: Tuning RX FAILED!
cf_axi_adc: probe of 79020000.cf-ad9361-lpc failed with error -5

cf-ad9361-lpc is the IIO device that software uses to read received samples. That is the same in the normal firmware and the SparSDR firmware. Because it failed to start, the software can't receive any signals.

If you run iio_info on the Pluto, it will show you all the IIO devices. I expect that cf-ad9361-lpc will be missing.

I would suggest trying this:

  1. With the normal Pluto firmware from Analog Devices, see if cf-ad9361-lpc gets initialized correctly
  2. With the Pluto+ patches but without the SparSDR patches, see if cf-ad9361-lpc gets initialized correctly
  3. With the Pluto+ and SparSDR patches, see if cf-ad9361-lpc gets initialized correctly

That should help tell if there is a hardware problem, a problem with the Pluto+ patches, or a problem caused by both sets of patches.

lobart commented 1 year ago

@samcrow Thanks for your answer! Results:

  1. cf-ad9361-lpc gets initialized.
  2. cf-ad9361-lpc gets initialized.
  3. I found a vivado compile time error. Then i can't test your third version. I think there are conflict with pins mapping in vivado project. vivado.log
lobart commented 1 year ago

@samcrow I applied only hdl patch and built firmware. eth0 is lost. But cf-ad9361-lpc is initialized.

lobart commented 1 year ago

@samcrow dmesg logs with sparsdr and plutoplus sparsdr_dmesg.log

samcrow commented 1 year ago

It looks like the Pluto+ and SparSDR patch sets have some conflicts. If you apply the SparSDR HDL patch but not the other SparSDR patches, SparSDR will not work. You need to resolve the conflict that causes the Vivado compile error.

I wish I could help more, but I don't have a Pluto+ device or enough time to solve these problems. Good luck with the debugging.