schelleg
commented
8 years ago Hi Cathal,
This would occur if pmod.tcl or _iop.py is out of sync with what is on repository. those files work together to "find" IOPs. Let me know if that helps issue
On Mon, Apr 25, 2016 at 12:15 PM, cathalmccabe notifications@github.com wrote:
I have rebuilt the bitstream, and the SDK projects. I copied the new pmod.bit to the board, and the new SDK bin projects.
When trying the notebooks to test I get the error at the bottom. This is for the ALS, but I get the same error for all the other peripherals.
Has something changes with the IOP .py? I don't understand what is happening with this code, or what it is trying to do.
ValueError Traceback (most recent call last) in () 6 7 # ALS sensor is on 1st PMOD labeled JB ----> 8 my_als = PMOD_ALS(1) 9 my_als.read()
/usr/local/lib/python3.4/dist-packages/pynq/pmods/pmod_als.py in init(self, pmod_id) 64 65 """ ---> 66 self.iop = _iop.request_iop(pmod_id, ALS_PROGRAM) 67 self.mmio = self.iop.mmio 68 self.log_interval_ms = 1000
/usr/local/lib/python3.4/dist-packages/pynq/pmods/_iop.py in request_iop(pmod_id, mb_program) 191 if (iop_name not in ip_names): 192 raise ValueError("No such IOP for PMOD ID {}." --> 193 .format(pmod_id)) 194 195 gpio_names = PL.get_gpio_names()
ValueError: No such IOP for PMOD ID 1.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/Xilinx/Pynq/issues/48
Graham
cathalmccabe
I have rebuilt the bitstream, and the SDK projects. I copied the new pmod.bit to the board, and the new SDK bin projects.
When trying the notebooks to test I get the error at the bottom. This is for the ALS, but I get the same error for all the other peripherals.
Has something changes with the IOP .py? I don't understand what is happening with this code, or what it is trying to do.
ValueError Traceback (most recent call last)