Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
Do we know who added the 14443a support to the FPGA code? Is he on this forum?
I've been trying to compile the FPGA from source (I know it's not strictly required) using Xilinx's latest webpack and the compilation fails:
ERROR:Pack:1107 - Unable to combine the following symbols into a single IOB
component:
PAD symbol "pck0" (Pad Signal = pck0)
BUF symbol "pck0_IBUF" (Output Signal = pck0_IBUF)
A generic IO component of type IOB was chosen because the IO contains symbols
and/or properties consistent with input, output, or bi-directional usage and
contains no other symbols or properties that require a more specific IO
component type.
I've been tearing my hair out on this as this generic error is not very useful. This seems to be related to the user constraints file, as the source compiles when I remove the pck0 to PIN 36 constraint but of course that is a must since we actually want pck0 to be on PIN36.
Has anyone been able to compile the FPGA source?
What changes to the source were required if any?
What tools and versions did they use?
Any other gotchas?
Offline
Oh thanks for that pointer SD, it worked so the project compiles now. Weird that JW 's sources compiled without that "fix" even through we're all using Xilinx's compilers.
I've been having some fun with ModelSim-XE and running some of the modules through the simulator and looking at the waveforms. I love ModelSim and this is about as much as I can do untill I actually build my Proxmark hopefully in a couple of weeks. The PCBs are on their way to me as I type from what I heard...
Offline
Hello d18c7cb. It seems like you solved this problem, but the solution is not in this post. Can you please tell me what solution you ended up finding, or can someone else suggest how to fix this error? It seems to be a mapping error in Xilinx.
Thank you in advance.
Offline
wow, talk about bringing a dead thread back to life... 10 years..
Offline
Pages: 1