I am trying to connect openOCD to BeagleBone via onboard FTDI JTAG Emulator on Windows 7 x64. I have installed the ftdi driver 64bit that came with BeagleBone. when i connect the BBone to windows, USB Serial Converter A and B shows up along with COM port.
the hardware id of device-managers shows up as:
USB\VID_0403&PID_6010
I have downloaded openOCD 0.6.1 with both 32 & 64 bit binaries and ti_beaglebone.cfg script and the VID PID matches as above.
I have tried executing:
openocd-x64-0.6.1.exe -f board/ti_beaglebone.cfg
But it doesn't recognize the FTDI at all and shows up following lines:
Open On-Chip Debugger 0.6.1 (2012-10-07-10:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 16000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Warn : unable to open ftdi device (trying more): device not found
Error: unable to open ftdi device: device not found
in procedure 'init'
I have tried both 32 and 64-bit binaries of OpenOCD and no luck.
Any help would be appreciated
Thanks
Related
I am following this webpage to install nvidia GPU drivers in my fedora 34 64 bit system but it prompts me with an error of unable to load nvidia-drm kernel module while installing. The nvidia driver I used is Quadro RTX 4000 version, 470.74
The log during installation is here.
https://pastebin.com/5GbYcMgp log for nvidia fedora installation
Help of any sort will be appreciated!
So i have one embedded platform Zedboard upon which i am able to run the Xilinx Linux.Also in mine board i have enabled the wifi interface and also i have busybox application in mine root file system and when i typd the command
busybox
it shows the msg
BusyBox v1.22.1 (2016-11-01 12:04:21 GMT) multi-call binary.
Now i have one Ubuntu PC. From this Ubuntu PC i can ping mine Zedboard.
Could somebody tell me how to transfer some file form Ubuntu PC to this embedded platform Zedboard using tftp protocol step by step as well as necessary settings that need be enabled prior to the communication in the Ubuntu PC.
Regards
Aditya
I think This link will help you. I used this tutorial to setup the TFTP server and successfully worked with loading binary files to Beagleboneblack with U-boot bootloader over TFTP from my host PC.
I am using 64 bit ARMV8, on Kernel 3.18 based android device.
I am trying to use kgdb using kgdboc on Serial port. When I try to enable the kgdboc, it gets failed (Error -19).
echo ttyS1 > /sys/module/kgdboc/parameters/kgdboc
Please help me to resolve this issue.
I have a Virtual Smart Card Reader driver. It installs correctly at my PC (Windows 7 x64). But installation fails when I install it at another Windows 7 x64 PC. Of course I install them in the same way:
devcon install <inf> <hwid>
I compared setupapi.dev.log files and found the difference at very first line:
Successful sessions at my PC always starts from
[Device Install (Hardware initiated) - {892EDE5E-BE49-443c-A0B3-005D74F2D69C}\ScFilter\1&3908c5bd&9&01]
Failed sessions at another PC always starts from
[Device Install (UpdateDriverForPlugAndPlayDevices) - root\BixVirtualReader]
I had another Virtual Smart Card Reader at Divice Manager. But I switched it off before the installation of new driver.
I have working
kernel debug setup on old host computer with Windows Xp. On the new computer i
get preinstalled Win 7. I have installed PCI to Firewire card (usb-5pci3pfw).I
have installed WinDDK (7600.16385.1).
So I go to
C:\WinDDK\7600.16385.1\Debuggers and run as administrator windbg.exe
(6.12.2.633)
Choose File
> Kernel Debugging > 1394 > and select channel like on target and get
this message:
Using 1394 for debugging
Checking 1394 debug driver version.
Could not find C:\Windows\SysNative\drivers\1394kdbg.sys.
Cannot install a 32 bit driver on a 64 bit host.
Please run the 64 bit native version of this debugger to
upgrade to the latest version of 1394kdbg.sys.
Kernel debugger failed initialization, HRESULT 0x80004005
"Unspecified error"
I expect that
WinDbg will make install of the 1394kdbg.sys driver.
Yes in C:\WinDDK\7600.16385.1\Debuggers\1394 directory there 1394kdbg.sys and
1394dbg.inf.
In inf file
there install section only for 32 bit.
I try to add
64 bit section and install driver but it doesn't helps.
Does somebody know the right way to
install kernel debugging on Win 7 64 bit Host?
You have to install and use the x64 debugging tools.
These should be part of the Windows SDK.
So yes install of "Debugging Tools for Windows (x64)" did help.
I downloaded Windows SDK as Christopher wrote.
Selected install of debug tools, i did have some problems during installation because i have installed Visual Studio Compilers so i use Help from Here
Then Windows SDK copy installation .msi files here:
"C:\Program Files\MicrosoftSDKs\Windows\v7.1\Redist\Debugging Tools for Windows"
In this folder:
dbg_amd64.msi - (64 bit version of debuging tools)
dbg_ia64.msi - (for Itanium processors)
dbg_x86.msi - (32 bit version of debugging tools)
i install "dbg_amd64.msi" and get 64bit debugging tools folder here:
"C:\Program Files\Debugging Tools for Windows (x64)"
now in 1394 subfolder there "1394kdbg.sys" and "1394dbg.inf" for 64bit.
so now i connect my host win7 64bit computer over firewire to target.
run "C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe" as administrator
Choose File > Kernel Debugging > 1394 > and select channel like on target
and get finally
Using 1394 for debugging
Checking 1394 debug driver version.
Could not find C:\Windows\system32\drivers\1394kdbg.sys.
Attempting 1394 debug driver installation now. "i get pop up to install drivers"
Driver installation successful.
Retrying 1394 channel open.
Opened \.\DBG1394_INSTANCE10
What is interesting when i did install "Windows Drivers Kit 7.1.0"
i didn't found 64bit version of debugger in "C:\WinDDK\7600.16385.1" folder.
Installation of 1394 kernel debugging on Target side for winxp x86:
Open a CMD window
attrib -s -h -r c:\boot.ini
notepad c:\boot.ini
Add these lines:
[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows" /fastdetect /debug /debugport=1394 /channel=10
Reboot the machine
Installation of 1394 kernel debugging on Target side for Windows Vista up:
Read Here