Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Thanks for making this repository. I think the arduino compatibility could be more important for large scale adoption of the k210 boards of Sipeed than micropython is.
However, there are some issues.
After installing maixduino as described here, I get the following errors:
During starting the arduino IDE:
I noticed that in the json only the kflash version 1.0.0 is mentioned in the tool section, could that be an issue? On the other hand, both 0.4.1 and 1.0.0 are installed in the Maixduino/tools/kflash directory.
When compiling the mas_basic example I get the following error:
Searching the internet shows that this is some gcc error, and thus probably caused by the compilers. Repairing this seems to be tricky, so I used my separately installed toolchain that I know is working. This was achieved by adding the following lines at the appropriate lines in board.txt:
I get a lot of compiler warnings, but it does produce a .bin file.
At first uploading did not work while no error message was produced. After switching the MAIX Go board off and on, and waiting a while, uploading did succeed. There is, however, no visible output. Not in the IDE (of course, but the other kflash versions I used automatically started a minicom) and not in the arduino serial monitor. Starting an external serial monitor (cutecom) does show a small portion of the output (about 5 lines), but then stops.
does produce the correct output.
Hopefully some of these issues can be repaired, or maybe you can tell me what I should do differently.
The baud rate is set correctly. Changing it does not make it work.
If I upload the sketch and then open the serial monitor it shows nothing. If I then close the serial monitor and open it again it shows about 10 to 20 lines of the output but does not continue. If I close and open it again, it shows newer output but again only some lines without continuing.
I added a Serial.flush() after the printing statements in loop(). This did not help.
It seems like the arduino serial monitor and cutecom are able to read a buffer with output, but not read directly from the device.
Then I tried to use minicom and I noticed something odd:
but immediately the minicom terminal started showing the serial output, and kept on going! It seems like my script changed some settings that allowed minicom to read data from the device.
I tried the same with the other terminal programs:
And nothing further happened.
If I open cutecom and then start the script, cutecom stops and closes the device and my script starts producing output.
Hopefully this gives you a hint of what might be wrong.
Thanks in advance!
I tried on a new one ubuntu18, no error occurred!
If can not find lib.so like
These way may resolve your serial problem
then need to logout or reboot!
I installed the latest Arduino IDE, added the toolchain path to .bashrc, and did the usermod command. It now compiled and uploaded without a problem (except for the compile warnings). Thanks!
Unfortunately, the serial is still not working. I did observe something strange. I did some further testing, now also using minicom. When I start minicom (with all correct settings) it does not show the serial output. If I leave minicom open, and in another terminal I issued the following statements, I get interesting results:
Python gives an error, and minicom starts showing output. But for
python does not stop but gives no output and minicom also does not start showing output.
So dtr and rts need to be 0. Serial.tools.miniterm probably first sets the dtr and rts and then finds out the serial port is already in use and stops with an error. Thanks to setting dtr and rts to 0, minicom can finally read the serial port.
I haven't yet burned open-ec. Maybe I will give that a try.