Situation is that we made the stm32 and PC computer communication, communication way is HID, but there is a very strange situation is
Upper machine and lower machine, close the upper machine, after using this process everything is normal,

But!!!!! Sometimes shut down after half an hour to open the PC at this time although can connect the machine, but all not a line to send and receive data, then restart the computer
Or to plug the USB can be back to normal,

And as long as every time open the gap between the PC and the last closing not too long will not appear this kind of problem, very strange!

This problem is very headache and occasional sometimes 2 hours is not a problem, don't know if you have met this kind of situation

CodePudding user response:

Could it be suspend, can be caught and have a look

CodePudding user response:

What is suspend bosses? Because the circuit board is made of the outsourcing company, both sides are now looking for a reason,

I don't understand of embedded underlying suspend refers to the CPU circuit board hang up usb? That how to prevent not suspended?

CodePudding user response:

refer to the second floor Joshua_88 response:

bosses suspend is what? Because the circuit board is made of the outsourcing company, both sides are now looking for a reason,

I don't understand of embedded underlying suspend refers to the CPU circuit board hang up usb? That how to prevent not suspended?

So stm32 program was not written by you that is not good to solve, the upper only by Bus Hound Bus data monitoring, see is the top didn't sent out, or the underlying didn't back,
Hung is a USB device, and host it doesn't matter,

CodePudding user response:

When I do this thing, communications directly plug usb just pause and plug in again, did you not make wrong processing,

CodePudding user response:

refer to 4th floor to help you I her reply:

I do this thing, direct plug usb communication just pause and plug in again, did you not make wrong processing,

Is not the first time that I didn't plug USB is only the PC software is closed, the back open again again have probability can't send and receive, but if the time between the two open there would be no problem as long as not too long
1 open the PC - PC waiting for 5 minutes off on PC - off PC waiting for 5 minutes on PC - off PC
2 on PC - off PC waiting for 30 minutes to open the PC - PC waiting for 30 minutes off on PC - off PC

Repeated sequences 1 no matter how many times will not have a problem, because of the short idle time
Sequence 2 there is a probability problem

CodePudding user response:

reference poetryTang reply: 3/f

Quote: refer to the second floor Joshua_88 response:

bosses suspend is what? Because the circuit board is made of the outsourcing company, both sides are now looking for a reason,

I don't understand of embedded underlying suspend refers to the CPU circuit board hang up usb? That how to prevent not suspended?

So stm32 program was not written by you that is not good to solve, the upper only by Bus Hound Bus data monitoring, see is the top didn't sent out, or the underlying didn't back,
Hung is a USB device, and host it doesn't matter,

Bosses USB device is the value of circuit board on which device? Or what?

CodePudding user response:

USB communication, PC's USB Host (Host), a machine under side is USB devices (Device), here is the STM32 circuit, MCU has USB peripherals, through the programming to realize all kinds of USB function, such as the HID communication, so the problem mainly in the equipment, the Host can't do something, only to monitor the data on the bus

CodePudding user response:

refer to 7th floor poetryTang response:

USB communication, PC's USB Host (Host), a machine under side is USB devices (Device), here is the STM32 circuit, MCU has USB peripherals, through the programming to realize all kinds of USB function, such as the HID communication, so the problem mainly in the equipment, the Host can't do something, only to monitor the data on the bus

Who can help me analysis this paper analyzes the reasons of what we phenomenon is the

1 open the PC - PC waiting for 5 minutes off on PC - off PC waiting for 5 minutes on PC - off PC
2 on PC - off PC waiting for 30 minutes to open the PC - PC waiting for 30 minutes off on PC - off PC

Repeated sequences 1 no matter how many times will not have a problem, because of the short idle time
Sequence 2 there is a probability problem, then it is ok to put the USB plug, or restart the computer can also solve (restart computer won't restart the power of the circuit board)

Key to this bug again harder this time, I two consecutive days no problem, and our equipment is two-way communication circuit board message to PC, PC will send message down a machine

CodePudding user response:

Also points master-slave two-way communication, the host to send, from the machine, the machine can't take the initiative to send to the host, no real bad concrete analysis, but you use bus hound can monitor host exactly have sent out, the data from the machine to have returned, can know what's the problem

CodePudding user response:

references 9 f poetryTang response:

also points master-slave two-way communication, the host to send, from the machine, the machine can't take the initiative to send to the host, there is no real bad concrete analysis, but you use bus hound can monitor host exactly have sent out, the data from the machine to have returned, you know what is the problem the

Today I cut to the packet so

CodePudding user response:

Is that all, feel no enumeration success, program can open it, or see the device manager