WSL Minicom Hangup?

General
1

Unsure if this is the best place to put this, but I am very new with this stuff. I got a Bus Pirate 6 and trying to get setup with JTAG and OpenOCD. I was following a tutorial that was going through using minicom.

I am using WSL on my windows computer and using USBIPD to pass the Bus Pirate through. WSL sees it and I have setup minicom -s with the correct device path which lets me open minicom.

Issue is that I can’t do anything in minicom other than the ^A commands. It doesn’t take in any inputs or show the Bus Pirate console options in minicom. I can use Putty on windows to use Bus Pirate, but OpenOCD has been a pain to try and get that working on windows as I haven’t been able to compile a version that supports Bus Pirate. MSYS2 says it doesn’t support Bus Pirate when trying it.

Alternatively if someone happens to have an already compiled OpenOCD 12.0 that for windows with Bus Pirate enabled, I’d gladly use that solution.

Any and all help is appreciated!

2 Likes
2

Hey, welcome :slight_smile:

What tutorial are you using?

Which firmware are you using in the Bus Pirate?

The new modern Bus Pirates support JTAG and SWD through ported alternate firmwares. DirtyJTAG for urjtag, and the pico probe port for SWD with openOCD.

If the tutorial is for the old v 3.x hardware, that kind of OpenOCD protocol isn’t implemented in the main firmware yet. It probably won’t be, as it’s much easier and faster to be a clone of other well developed devices already supported by the software you want to use.

1 Like
3

ohh gotcha. yeah i was using this as it was recommended on a reddit post from a year ago

are there any new tutorials I should be looking at? I am currently on the latest firmware posted about 8hr ago

1 Like
4

Oh yeah that’s a 10 year old post.

I’m not at a big computer at the moment, but if you search dirtyjtag or pico probe my recent ports should be at the top.

What is your target? I’m working on JTAG now so it’s a good time to figure out the best solution.

1 Like
5

It is a home automation control system called Savant. I have one of their host hardware and trying to find the JTAG ports on here, so part of this process is for JTAG pin discovery.

I have found the UART, but second question here is how would I go about sending commands? In bridge mode I can read the outputs and during boot it has a countdown to press any key to stop their auto boot, but it seems that bridge mode doesn’t let me type? Or is it just that it doesn’t show the inputs in console?

1 Like
6

A couple of quick thoughts about the UART:

  • Are you sure you have the correct RX connection (on the Savant)?
  • The device may not echo, you’d have to turn that on in your terminal
  • You might need pullups enabled ) enable them with capital P before running bridge

For finding JTAG, I know @ian was working on getting BlueTag included in the build. blueTag (JTAGulator alternative) port to Bus Pirate

1 Like
7

Hi there! I am very new with all of this so it’s very likely I don’t have the correct RX

IMG_8517
IMG_8517378×504 86.5 KB

I am using these 3 pins on J1 and have found the left to be ground, the right to be TX, and then assumed the middle is the RX.

3.3v on the right pin and 1.2v on the middle

1 Like
8

Did you try turning on pullups? Seems like the right pin, based on that connector.

Do you have the Vin connected to 3.3v on the target?

1 Like
9

i just tried with pullups but no dice on sending that command.

I am unsure about the Vin? I only see a Vout on the Bus Pirate and the io0-7 and gnd? The target device is plugged into wall for its own power

from left to right it is gnd, io4, io5 on J1

1 Like
10

Sorry for the confusion. I said Vin, but yes, it is labeled Vout. The pin is either Vout or ref Vin.

Check this out about pullups: Onboard Pull-up Resistors | Bus Pirate 5 Firmware

I recently worked on a target DUT that didn’t have pullups on board for the UART.

Use the W command to turn on the power supply, set it for 3.3V (I assume that’s what the target is using). Then use the P to turn on pullups and try again.

4 Likes
11

ahh yup! that got me working with UART!

3 Likes