On 09/28/2018 09:33 AM, Jason Meyer wrote:
Yes, I’m seeing the same behavior with a standard image as with my
custom image.
Jason
So, I'm wondering if something is dropping ethernet frames during the
upload to the device, resulting in a corrupt image.
On Sep 27, 2018, at 8:31 PM, Marcus D. Leech <mle...@ripnet.com
<mailto:mle...@ripnet.com>> wrote:
On 09/27/2018 07:09 PM, Jason Meyer wrote:
The command produces output as if there is no issue. It shows the
progress of the image being loaded, and at the end states that the
process was a success and to power-cycle to see the changes made.
However when I power-cycle, I am unable to communicate with the USRP
until I load the FPGA image via JTAG. This has happened with 3
different USRPs.
Jason
Does the "cannot communicate with the device" happen even after
loading a standard image?
On Thu, Sep 27, 2018 at 6:40 PM Marcus D. Leech <mle...@ripnet.com
<mailto:mle...@ripnet.com>> wrote:
On 09/27/2018 06:34 PM, Jason Meyer wrote:
Hi Marcus,
I am using UHD v3.11.1.0. The command format I've used is:
uhd_image_loader --args="type=x300,addr=192.168.10.2"
--fpga-path="/usr/local/share/uhd/images/<fpga_image>.bit"
Does the command produce any output?
How are you confirming that it's reverting to a previous image?
Except for broken hardware, this should "just work". But you've
mentioned the same behavior on multiple X310s.
Jason
On Thu, Sep 27, 2018 at 5:28 PM Marcus D. Leech via USRP-users
<usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>> wrote:
On 09/27/2018 03:46 PM, Jason Meyer via USRP-users wrote:
> Hello,
>
> I have been working with multiple X310 USRPs and
attempting to load
> custom FPGA firmware onto the motherboard EEPROM using the
> uhd_image_loader command. The command appears to be
successful, but
> the FPGA fails to load the image on reboot. The image
functions just
> fine when I program it through JTAG and Vivado Hardware
Manager, but I
> would like to store it in EEPROM to avoid needing to
re-program every
> time I reboot the radios. The same error has occurred on
multiple
> motherboards, and continues to occur when I use
uhd_image_loader to
> load an image retrieved from uhd_images_downloader.
>
> What options do I have for debugging the EEPROM?
>
> Thank you,
> Jason Meyer
>
>
This should "Just Work(tm)"
How exactly are you using uhd_image_loader, and what
version of UHD are
you using?
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
