Activity for Johnichan
-
Johnichan created ticket #138
dr command hex conversion is wrong
-
Hey, I the problem was fixed by using version 2055. I used digilent HS3 successfully using the command "cable DigilentHS1 pid=0x6014 vid=0x403 interface=0"
-
Hey, I the problem was fixed by using version 2055. I used digilent HS3 successfully using the command "cable DigilentHS1 pid=0x6014 vid=0x403 interface=0"
-
https://sourceforge.net/p/urjtag/git/ci/c0770d4bb0638d838b0cbd946cc37195850e1f7c/ was the version digilent hs1.( Not #1502)
-
Let me tell my background before getting into the issue. I am a hardware designer, occassionally get into BGA soldering issues, which i use urjtag to debug. I learned C code only for urjtag modifications and compile. I am not an expert in the same. Now I recently wanted to use a urjtag fordebugging a bga soldering issue and as in design side, i don't get professional DFT tools. I try to manage with urjtag or topjtag(Still trying to make it working in eval period). I got digilent HS1 cable and wanted...
-
Bingo.. I installed PYFTDI just for driver and then run jtag on sudo Johnz@pi4bp2Ram4GB:/home $ sudo /usr/bin/jtag UrJTAG 0.10 #2007 Copyright (C) 2002, 2003 ETC s.r.o. Copyright (C) 2007, 2008, 2009 Kolja Waschk and the respective authors UrJTAG is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for UrJTAG. warning: UrJTAG may damage your hardware! Type "quit" to exit,...
-
libusb libftdi problem in rpi4b bookworm arm64
-
Let me try Debian on a Pi before worrying toomuch about cygwin drivers
-
Does not looks good even after fixing the above issue by changing config.guess from automake 11.7 & adding popt to the cygwin https://stackoverflow.com/questions/23210522/undefined-references-cygwin-posix-to-win32-path-list-and-cygwin-posix-to-win32 $ make Making all in admin make[1]: Entering directory '/cygdrive/f/urjtag/drvr/ioperm-0.4/admin' if gcc -DPACKAGE_NAME=\"ioperm\" -DPACKAGE_TARNAME=\"ioperm\" -DPACKAGE_VERSION=\"0.4\" -DPACKAGE_STRING=\"ioperm\ 0.4\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"ioperm\"...
-
Thanks for quick response. Thinking that ioperm is very old, I thought it will never considering ioperm is very old. Now it goes upto little more and waiting for checking the maximum length of command line arguments... Let me see it after an hour or a retry. I found the stackoverflow to use x86_64-unknown-linux-gnu $ ./configure --build=x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk...
-
Tried IOPERM from openwince but failed config.guess timestamp = 2002-01-02 uname -m = x86_64 uname -r = 3.4.9-1.x86_64 uname -s = CYGWIN_NT-10.0-19045 uname -v = 2023-09-06 11:19 UTC /usr/bin/uname -p = unknown /bin/uname -X = hostinfo = /bin/universe = /usr/bin/arch -k = /bin/arch = x86_64 /usr/bin/oslevel = /usr/convex/getsysinfo = UNAME_MACHINE = x86_64 UNAME_RELEASE = 3.4.9-1.x86_64 UNAME_SYSTEM = CYGWIN_NT-10.0-19045 UNAME_VERSION = 2023-09-06 11:19 UTC configure: error: cannot guess build type;...
-
It compiles to exe, but breaks for ioperm.
-
cygwin64 is asking cygioperm which is not part of cygwin64
1
