Yes I have defined the Gpio as output in the mask register ________________________________ From: Nick Foster <bistrom...@gmail.com> Sent: Friday, April 26, 2019 1:24 PM To: Chatterjee, Pratik Cc: Jonathon Pendlum; usrp-users@lists.ettus.com Subject: Re: [USRP-users] RFNOC GPIO Remapping
Have you defined that GPIO as an output in the mask register? On Fri, Apr 26, 2019 at 9:01 AM Chatterjee, Pratik via USRP-users <usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: Hi Jonathan, I have a question regarding fpga and rfnoc. I am trying to set a 1'bit value on one of the registers in my noc_block and send the value out the remapped gpio pins. I haven't been able to see the value on my gpio pin. Although declaring the register in the custom gpio file I do see the output. Appreciate any insights as to why such a thing is happening. Thanks, Pratik ________________________________ From: Chatterjee, Pratik Sent: Sunday, February 3, 2019 9:31 PM To: Jonathon Pendlum Cc: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: Re: [USRP-users] RFNOC GPIO Remapping Thank you Jonathon for your help. I had modified some sections of the file x300_db_fe_core.v which was causing the error. I was able to compile an unmodified image without error. ________________________________ From: Jonathon Pendlum <jonathon.pend...@ettus.com<mailto:jonathon.pend...@ettus.com>> Sent: Saturday, February 2, 2019 7:02 PM To: Chatterjee, Pratik Cc: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: Re: [USRP-users] RFNOC GPIO Remapping Hi Pratik, That error generally means that the RFNoC block did not response to a command packet. That happens when the block is not correctly connected to the crossbar or the clocks are not connected. In this case it is the Radio Core RFNoC block, which by default is correctly connected unless modified. Did you make any modifications to the Radio Core RFNoC block I/O, either in the source file or the instantiation in x300_core.v? Also as a sanity check, are you able to build an unmodified image that works without that error? Jonathon On Sat, Feb 2, 2019 at 3:10 AM Chatterjee, Pratik via USRP-users <usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: Hello, I am using an X310 and I need to monitor a signal out of GPIO from my custom block. Going through the archives I prefer the option to disconnect the fp_gpio lines from the radio core to my custom block. So I snapped the fp_gpio lines going in gpio_attr to a custom module in db_control to observe the signal. The image compiled fine. But when I probe the device, I get the following error [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.HEAD-110-g6af6ac32 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] No GPSDO found [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D00000000000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1315 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1309 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) terminate called after throwing an instance of 'uhd::io_error' what(): EnvironmentError: IOError: [0/Radio_0] sr_write() failed: EnvironmentError: IOError: Block ctrl (CE_01_Port_40) no response packet - AssertionError: bool(buff) in uint64_t ctrl_iface_impl<_endianness>::wait_for_ack(bool, double) [with uhd::endianness_t _endianness = (uhd::endianness_t)0u; uint64_t = long unsigned int] at /home/delta3/rfnoc3/src/uhd/host/lib/rfnoc/ctrl_iface.cpp:155 Is there something more than just disconnecting the lines. Any help will be appreciated. Thank you, Pratik _______________________________________________ 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ettus.com_mailman_listinfo_usrp-2Dusers-5Flists.ettus.com&d=DwMFaQ&c=nE__W8dFE-shTxStwXtp0A&r=nAy51XlmgASUaOVvQRwfzA&m=RR0Os5pOuCIFj6RSiDpZtCwhN0ZWVBCgbpYNNYRpB_w&s=MRtcta--pJI7gdHy2M-FnhudvzuDwYFEpapAOuyL0Ns&e=> _______________________________________________ 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ettus.com_mailman_listinfo_usrp-2Dusers-5Flists.ettus.com&d=DwMFaQ&c=nE__W8dFE-shTxStwXtp0A&r=nAy51XlmgASUaOVvQRwfzA&m=RR0Os5pOuCIFj6RSiDpZtCwhN0ZWVBCgbpYNNYRpB_w&s=MRtcta--pJI7gdHy2M-FnhudvzuDwYFEpapAOuyL0Ns&e=>
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com