Hello,
- We followed the instruction in setting up the putty but we cannot open the terminal
- Also tried to update the firmware, but we cannot access the mcumgr client, but we downloaded everything needed
What do we need to do?
Hello,
What do we need to do?
The first thing you need to do is tell us what converter you’re using, how it is connected to UbiSwitch, and what revision of UbiSwitch you have.
Please share that information.
The converter we’re using is the waveshare USB to RS232/485/TTL.
The converter is connected in the UART of the Ubiswitch, TX from Ubiswitch connected to the RX of the converter and RX from Ubiswitch connected to the TX of the converter. 3.3V connected in the VCC and GND to the GND of the converter. The converter is in 3V3
The revision of the Ubiswitch is BB-UD1-B-1
You should not connect the 3.3V from your converter to UbiSwitch. 3.3V is an output from your converter, and it’s also an output from UbiSwitch. Let’s hope you didn’t kill anything on the board.
I can’t see from your photos, did you set the converter to 3.3V?
Finally do you see this converter come up as a COM port in your PC, and do you select that in your serial program? What serial program are you using, and what baud rate settings do you have.
You gave me the revision of the baseboard, but I need the revision of the module. Unplug the module and look for the text printed on the bottom. It will be either BB-UBS-B-1 or BB-UBS-A-1.
Also, can you tell me if you see a red light turn on, on the module, for five seconds, after you power it up. This confirms the firmware is running correctly.
The revision of the module is BB-UBS-B-1
The converter is in 3.3V
And there is a red light turn for five seconds when it is power up.
Please answer my other questions.
Show me what you see on the terminal when you turn ubiswitch on
What are all those characters after “ubiswitch”? Are you typing that, or does it just appear that without any user input?
It just appeared when I power up the Ubiswitch but when I tried it again it is just the second image.
This sounds like a loose cable. Show me how your cabling is done.
Also, type a command like below and show me what the response is.
port 1 show conf
TX from Ubiswitch to RX of the converter and RX from Ubiswitch to the TX of the converter. The Ubiswitch and converter is in the same ground.
Well, it’s working. You are reading port 1.
I suspect the issue was a loose wire. Check your wiring, then try power cycle a few times to make sure the issue has gone.
Okay. Thanks for the help!
Hmm, is this documented in the CLI guide somewhere? Because it seems to me many people would connect the power line. I did for a while. But then I figured it is inconvenient because only the STM and not the switch get power. And when I connected both UART power and standard power, disconnecting just the standard power led to rebooting of just the switch chip and not of STM. So I ended up using only main power and disconnected the UART power. But I don’t think it was in the docs (I actually had some feedback regarding this that I’ve sent via email).
Also, the UART-picoblade cable you supply has 4 wires. That would suggest you’re supposed to connect them all.
Yeah, you’re right.
I think I’m probably coming at this from a lot of pre-learned knowledge. I know from experience that some UART converters (most, actually) output a 3.3V to the target, whereas some need a voltage reference to be fed in to set the voltage level for RX and TX. I think I just assume that that’s common knowledge, and I guess it’s not.
I’ve updated the CLI guide, and datasheets of both baseboards to add this information.
Thanks for the suggestion