Hello, All!
Please, help me resolving problem with umdesk:
1. uhd_find_devices work:
-------------------------------------------------- -- UHD Device 0 -------------------------------------------------- Device Address: type: umtrx addr: 192.168.135.35 name: UmTRX serial: 75
2. But uhd_usrp_probe fails:
linux; GNU C++ version 4.7.2; Boost_104900; UHD_003.004.000-unknown
-- Opening a UmTRX device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Error: resolve: Service not found
I think the problem around eeprom(because led ZPU && FPGA is on), how i can reset it's value to default?
Best regards, alex korolev nik135@mail.ru
Alex,
Could you provide the complete command line you use for uhd_usrp_probe? Googling tells us that "resolve: Service not found" error is a result of passing an unsupported address type to a resolver.
On Fri, Jan 17, 2014 at 1:16 PM, alex korolev nik135@mail.ru wrote:
Hello, All!
Please, help me resolving problem with umdesk:
- uhd_find_devices work:
-- UHD Device 0
Device Address: type: umtrx addr: 192.168.135.35 name: UmTRX serial: 75
- But uhd_usrp_probe fails:
linux; GNU C++ version 4.7.2; Boost_104900; UHD_003.004.000-unknown
-- Opening a UmTRX device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Error: resolve: Service not found
I think the problem around eeprom(because led ZPU && FPGA is on), how i can reset it's value to default?
Best regards, alex korolev nik135@mail.ru
Alexander,
i run "uhd_usrp_probe" without any arguments.
"usrp_burn_mb_eeprom --key=ipaddr" return same error.
previously these tools will work .
transceived also don't work:
Config Settings Log Level............... NOTICE Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 Channels................ 1 Samples-per-Symbol...... 4 External Reference...... Disabled Diversity............... Disabled
-- Opening a UmTRX device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes ALERT 3046254816 06:17:41.8 UHDDevice.cpp:608:open: UHD make failed, device type=umtrx,addr=192.168.135.35,name=UmTRX,serial=75 ALERT 3046254816 06:17:41.8 osmo-trx.cpp:364:main: Failed to create radio device
Shutting down transceiver...
Is there a way to reset the eeprom saved values to it's default values?
ps. in my example of umdesk ethernet led in front side is not working. How i can turn it on?
Пятница, 17 января 2014, 13:54 +04:00 от Alexander Chemeris alexander.chemeris@gmail.com:
Alex,
Could you provide the complete command line you use for uhd_usrp_probe? Googling tells us that "resolve: Service not found" error is a result of passing an unsupported address type to a resolver.
On Fri, Jan 17, 2014 at 1:16 PM, alex korolev < nik135@mail.ru > wrote:
Hello, All!
Please, help me resolving problem with umdesk:
- uhd_find_devices work:
-- UHD Device 0
Device Address: type: umtrx addr: 192.168.135.35 name: UmTRX serial: 75
- But uhd_usrp_probe fails:
linux; GNU C++ version 4.7.2; Boost_104900; UHD_003.004.000-unknown
-- Opening a UmTRX device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Error: resolve: Service not found
I think the problem around eeprom(because led ZPU && FPGA is on), how i can reset it's value to default?
Best regards, alex korolev nik135@mail.ru
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
С уважением, alex korolev nik135@mail.ru
Alex,
On Fri, Jan 17, 2014 at 2:17 PM, alex korolev nik135@mail.ru wrote:
i run "uhd_usrp_probe" without any arguments.
Please make sure that it is using correct UHD library.
If you're using an Ethernet switch - try changing it. Some people reported issues with some switch models. You could also try changing an Ethernet card - we had issues with some JMicron based NICs.
UmTRX doesn't support 100Mbit cards and supports only a subset of 1GbE specs, so some cards and switches may be confused.
What may help to debug the issue is a Wireshark capture of what happens on this Ethernet connection.
"usrp_burn_mb_eeprom --key=ipaddr" return same error.
previously these tools will work.
What have you changed for it to stop working?
Is there a way to reset the eeprom saved values to it's default values?
No, there is no way to reset to defaults, other than writing values again.
Which values did you change?
ps. in my example of umdesk ethernet led in front side is not working. How i can turn it on?
This LED is not implemented yet. This is for a future software upgrade. :)
Alexander,
Пятница, 17 января 2014, 16:50 +04:00 от Alexander Chemeris alexander.chemeris@gmail.com:
What may help to debug the issue is a Wireshark capture of what happens on this Ethernet connection. ok, i try this.
previously these tools will work.
What have you changed for it to stop working?
./usrp_burn_mb_eeprom --key=gpsdo --val=internal
this command will success, i'm reboot device and uhd_usrp_probe and usrp_burn_mb_eeprom broke.
ps. where i can read about dbg port?
Regards,
alex korolev nik135@mail.ru
On Fri, Jan 17, 2014 at 6:30 PM, alex korolev nik135@mail.ru wrote:
Пятница, 17 января 2014, 16:50 +04:00 от Alexander Chemeris alexander.chemeris@gmail.com:
previously these tools will work.
What have you changed for it to stop working?
./usrp_burn_mb_eeprom --key=gpsdo --val=internal
this command will success, i'm reboot device and uhd_usrp_probe and usrp_burn_mb_eeprom broke.
Ok, this is a known issue. We have to disable this setting for UmTRX completely, as it doesn't make sense. I'll give you some guidance a bit later.
ps. where i can read about dbg port?
USB debug port is a virtual UART port with 230400 baud rate. Connect it to your Linux and you will see a serial-to-USB device. Usually it's /dev/ttyUSBx.
On Fri, Jan 17, 2014 at 7:02 PM, alex korolev nik135@mail.ru wrote:
Ok, thanks. explain me please, gps sync always active? and test_pps_input must always work?
Yes, GPS sync is activated automatically as soon as it receives a GPS signal.
ps. where i can read about dbg port?
USB debug port is a virtual UART port with 230400 baud rate. Connect it to your Linux and you will see a serial-to-USB device. Usually it's /dev/ttyUSBx.
I can use usual USB cable?
Yes, you should use a normal micro-USB cable.
-
alex korolev -
Alexander Chemeris