Posts made by say

@cek

Here is a screenshot of the server log file:

@Li-YiFan

Hi Li-YiFan,

Here is a screenshot of the Visual Studio Code terminal window after running server.py. It has the same output as Server_win32_1.1.1. The DOS command window disappears very quickly after running Server_win32_1.1.1, so the picture is blurry.

@cek

Hello cek,

I downloaded the EEPROM bin file and ran the server file you sent me with the log. I cannot attach them here. How do I send these files to you?

@Li-YiFan

Hi Li-YiFan,

I downloaded the IMU Server Ready-To-Use (Windows) using the Chrome browser and installed it as shown above. I still cannot connect to the IMU using ANS. After opening ANS, when I run Server_win32_1.1.1, a DOS console window opens briefly as shown here:

It gives the message as shown: "Cannot configure port, something went wrong. Original message: .."

How should I correct this problem?

@cek

Hi cek,

I performed the steps above exactly as listed. Here is a screenshot of the ST-LINK Utility after successfully uploading the bin file, locking the sectors, and restarting the IMU:

I immediately saw good data over HTerm on COM14:

However, I still cannot connect to the OpenIMU Monitor at developers.aceinna.com/devices/record-next

What next steps should I take?

I cannot get any data from the IMU over HTerm.

After establishing communication with the ST_LINK Utility, I tried to connect to each of the 5 COM ports using HTerm while the ST-LINK/V2 debugger LED is flashing alternately green and red. I could not get any data from the IMU over HTerm.

I also disconnected the IMU with the ST-LINK Utility and then again tried to connect to each of the 5 COM ports using HTerm while the ST-LINK/V2 debugger LED is constant red. I could not get any data from the IMU over HTerm.

@cek

Hi cek,

I installed the EEPROM bin file which you sent to me exactly according to the instructions under section 5 of the link above, starting at location 0x08000000, with a size of 0x30000. I set the 6 Option Bytes afterward and restarted the IMU board. I could not get the IMU to connect. I repeated the procedure again. I still cannot connect to the IMU with the OpenIMU Monitor. What should I do?

@cek

Hi cek,

Here's another screenshot of the HTerm data with the data type set to Hex and the data scrolled back to the beginning. The first few bytes do indeed read 55 55 7A 31 as you can see.

@cek

Hi cek,

Here's a screenshot of the data from HTerm on COM14:

The last 6 Pages (58-63) are write protected when I first open the Target > Settings > Option Bytes window.

My Serial Number from the label on the OpenIMU330BI EVK is:
1927300441

@Li-YiFan said in Cannot connect to OpenIMU330BI EVK:

if you follow the link https://forum.aceinna.com/topic/75/update-openimu330bi-new-firmware and get

Hi Li,

I followed the link you provided: https://forum.aceinna.com/topic/75/update-openimu330bi-new-firmware

The webpage at the link provided above shows a set of screenshots for the ST-LINK program. I was not able to find the data package 55 55 7A 31 XX XX anywhere in that webpage. Can you verify that you sent me the correct link?

@cek

I changed USB ports twice, restarting the operating system each time. The ST-Link is directly connected to the USB hub without a USB hub, which it has been all along. Using the Target > Option Bytes utility in ST-Link v4.5.0, I set Pages 58-63 to have Write Protection as shown in Li YiFan's link above. The screen shot from the ST-LINK > Printf via SWO viewer utility in St-Link is shown below. It does to indicate the baud rate. How else can I check the baud rate and observe the hex displaying mode?

I recently purchased an OpenIMU330BI EVK. After dozens of attempts, I cannot connect to the OpenIMU Monitor at https://developers.aceinnna.com/devices/record-next.

I downloaded the "IMU Server Ready-to-Use (Windows)" on my Windows 10 computer. I also updated the firmware on the OpenIMU330BI to OpenIMUBI_1.1.1 using the STM32 St-Link Utility. When I run Server_win32_1.1.1, COM7, COM1, COM8, and COM9 are successfully checked, then I get the message "Cannot configure port", and the terminal window suddenly closes.