how to solve this error for UBL tool in windows 8.1 pro

manojroy123 9 months ago

How to solve the above UBL error.

Parents

0 manojroy123 9 months ago

how to solve the above error.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 beacon_dave 9 months ago in reply to manojroy123

Is that with a USB-UART serial cable direct to the EVAL board bypassing the Landungsbruecke board ?

Is the UART cable still using COM3 and showing up ok in Device Manager ?

Is your UART set at the correct BAUD rate etc for the EVAL board ?

Is Tx/Rx wired the correct way around ? Tx -> Rx / Rx <- Tx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 manojroy123 9 months ago in reply to beacon_dave

I am using the microcontroller board that is provided by the TMC-9660-3PH-EVAL to perform that operation. I don't have USB to UART serial cable.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jc2048 9 months ago in reply to beacon_dave

"I'm guessing that up until now that has been 5V from the USB via the Landungsbruecke interface ?"

No. This is doing the selection on the TMC9660 board for the +VCC_IO

So it comes set for +3V3, derived from the internal buck if the motor supply is there, or +3V3 derived from the USB supply from the application processor board if not. (There's a linear regulator on the TMC9660 board to take the +5_USB down to +3.3V_USB.)
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 beacon_dave 9 months ago in reply to manojroy123
You've already done that back here:

https://community.element14.com/products/roadtest/f/forum/56322/how-to-solve-this-error-for-ubl-tool-in-windows-8-1-pro/231436

The problem is that it appears to be getting an unrecognised response back when it is expecting the device ID value.

You could perhaps try the standard fault-finding stuff like:

snoop the COM port to see what data is being sent/received

check any driver configuration settings on the virtual COM port in Device Manager

look at the Python code to see what it is doing where the error occurs

try rolling back, the PyTrimamic code example used ubltools_1.0.1

try re-flashing the firmware

try rolling back the firmware

try getting it up-and-running on an up-to-date and supported OS first
Cancel
Vote Up +2 Vote Down

Sign in to reply

Verify Answer

Cancel
0 beacon_dave 9 months ago in reply to Jan Cumps

I'm guessing that up until now that has been 5V from the USB via the Landungsbruecke interface ?
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 beacon_dave 9 months ago in reply to Jan Cumps

I'm guessing that up until now that has been 5V from the USB via the Landungsbruecke interface ?
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 jc2048 9 months ago in reply to beacon_dave

"I'm guessing that up until now that has been 5V from the USB via the Landungsbruecke interface ?"

No. This is doing the selection on the TMC9660 board for the +VCC_IO

So it comes set for +3V3, derived from the internal buck if the motor supply is there, or +3V3 derived from the USB supply from the application processor board if not. (There's a linear regulator on the TMC9660 board to take the +5_USB down to +3.3V_USB.)
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel