Well i just ordered a BBv2? from exp-tech.de , and 2xOLS buffers for my OLS'es :-)
I'm going to use the BB primarily for ARM-SWD.
Is there a "quickstart guide" , im 98% linux based , and cant use the .exe's
/Bingo
On Linux you're in luck :) Are you trying to use OpenOCD with the ARM, or the manufacturer's software? Install openOCD and have a look at an example configuration file for your core and a jtagkey type programmer (the default type the Bus Blaster emulates).
Here's the software tutorials:
http://dangerousprototypes.com/docs/Bus ... r#Software (http://dangerousprototypes.com/docs/Bus_Blaster#Software)
I also moved this to a new topic.
Thanx Ian
I got my BB yesterday , hope i get some sparetime in the weekend
I'll give SWD (and OOCD) a go , even though i just got the onboard st-link to work with CodeBlocks and the texane driver.
Does anyone know if i need a patch for oocd or is the kt-link in the mainstream code ?
Is the jtagkey emu ... The device from "switzerland" ?
Does that one do SWD ?
I have succesfully run standard arm-jtag with oocd & Just a "plain" FT-2232H
/Bingo
Ps: Found a BB "Jtag example here" , Jtag not SWD
http://www.nabiltewolde.com/programming ... very-with/ (http://www.nabiltewolde.com/programming-the-stm32f4-discovery-with/)
For the completeness of BB under Linux i'll post the url to the Urjtag build thread
viewtopic.php?f=37&t=4771 (http://dangerousprototypes.com/forum/viewtopic.php?f=37&t=4771)
And the Xilinx CPLD programming with xc3sprog thread
viewtopic.php?f=37&t=5076 (http://dangerousprototypes.com/forum/viewtopic.php?f=37&t=5076)
/Bingo
When connecting to a linux (here mint 14.1) the modem manager is locking the two ttyUSBxx devices for up to a minute annoying thing (prob Bill G inspired)
Feb 15 10:21:07 x200-1 modem-manager[1039]: <info> (ttyUSB0) closing serial port...
Feb 15 10:21:07 x200-1 modem-manager[1039]: <info> (ttyUSB0) serial port closed
Feb 15 10:21:07 x200-1 modem-manager[1039]: <info> (ttyUSB1) closing serial port...
Feb 15 10:21:07 x200-1 modem-manager[1039]: <info> (ttyUSB1) serial port closed
The solution is to tell the modem manager to "FSCK off" :-)
Get the file from here : http://n1.taur.dk/77-mm-usb-serport-blacklist.rules (http://n1.taur.dk/77-mm-usb-serport-blacklist.rules)
Drop it into /etc/udev/rules.d/
And do a : sudo udevadm control --reload-rules
Now all i have to do us make the tty's (vid:pid) user accesable so i don't have to use: sudo jtag
Maybe someone can chip in ...
/Bingo
Thanks, that's a handy udev file to keep around.
I have been wondering about this for some time, now I know.
Seems like libswd is having a hard time @oocd ,so don't count on KT-link as your swd jtag dongle right now
/Bingo
Does anyone know if i need a patch for oocd or is the kt-link in the mainstream code ?
Is the jtagkey emu ... The device from "switzerland" ?
Does that one do SWD ?
I thought kt-link is supported, but not sure about the SWD. sounds like SWD is still a problem.
Jtagkey does not do SWD. It is the very common interface designed (I believe) by Amontech.