Closed hfutball closed 2 years ago
Are SOP0 and SOP2 closed?
Are SOP0 and SOP2 closed?
I confirmed that sop0 and sop2 are closed. I tried another board iwr1843. The flash writing is normal. There may be some problems with the board used before, but the configuration cannot be sent successfully.
Have you removed jumper from SOP0 after flashing, and restarted the power?
I have solved this problem and completed the reproduction with your help , thank you for sharing such a perfect source code.
Hello vilari-mickopf and hfutball. When I see your problem, I find that the problem is the same as mine.
I'm also using 1642, but when I turn off SOP0 and 2 in Ubuntu, I can write.bin files to flash and execute start normally. However, flash cannot be executed in Windows.
After I wrote the.bin file to flash in ubuntu system, I directly executed the start command in Windows system and found that sending the configuration file failed.
I am very sorry to bother you and look forward to your reply.
Have you removed SOP0 after flashing?
It's been removed
I have no win on my pc, so this is only tested on linux. I remember testing it once on windows few years ago, and it worked, but i do remember that data and cli ports have been in reverse order, so i've added this to console's mmwave_init method:
if platform.system() == 'Windows':
ports.sort(reverse=True)
Maybe there is no consistency with the order of detected ports in win, so you can try and comment that. If that's the case, then you will have to connect your board manually every time (there is connect option).
Also, i will push a lot of changes soon (probably beginning of august) so there might be some fixes for your issues.
Also, just to be sure, you have reseted the board after removing sop0?
After I removed SOP0, I reset both the data cable and the power cable.
I'll try it now, manually connecting the port.
I changed True to False, can do flash, and can do start and send configuration files
if platform.system() == 'Windows': ports.sort(reverse=False)
Thank you very, very much for your answer.
Yup, order of detected ports in windows is unreliable then. This means flashing will probably work as well on win with this change.
There is not much that can be done by me in terms of making connection automatically. For cases like this i have implemented connect
option in console which will let you manually select port/rate for cli/data. I will add some small q/a section, explain this issue and how it can be solved.
Actually, in new version of the code i am checking the baudrate of the connection, and if detected baudrate is different than selected one, i warn the user about it. However, this auto rate detection can only be done for open ports, and before sending sensorStart
command to the board, data port is closed. But still, if ports are reversed, it should be detected that selected baudrate for cli is not good, and that can indicate this issue, stop autoconnection, and force the user to connect manually.
Yes, there is a lot of uncertainty about automatic connection. Different devices have different problems. Manual connections avoid this problem to some extent.
The previous problem has been well solved with your help. Thank you very much. Now there are two new problems. The configuration file cannot be sent to the board. I use iwr1642 and mmwave sdk 03 05 00_ 04, which is slightly different from what you use, so do I need to change the configuration file.
In addition, during flash operation, the console only displays' Ping mmwave ', and the version information should be displayed according to the code.
Such as' get version...
Thanks again! hfutball