Thoughts on the development of Web AI (kendryte K210)

Thoughts on the development of Web AI (kendryte K210)

In order to better take forward and use Web AI hardware, it should be taken into account and consider the basis of long-term development of the surrounding facilities, if in the future as products to non-professional people to use, you should be concerned about the focus of a number of product defects and needs pain points.

• This product should not particularly obvious defects, if a defect exists, it should also provide a solution.
• This product should be concerned utilize open source warehouse and related peripheral facilities, not to deviate from the mainstream.
• This product should enlarge its own advantages and use, evaluate and develop applications to improve expectations of users.

Cited open source warehouse

Up to now, the K210 related to the main warehouse are as follows, all have good potential:

Source Repository

• https://github.com/sipeed/MaixPy
• https://github.com/kendryte/kendryte-freertos-sdk
• https://github.com/loboris/MicroPython_K210_LoBo

Application development information

• https://github.com/mushroom-x/K210_Tutorial
• https://github.com/sipeed/MaixPy_DOC
• https://github.com/sipeed/MaixPy_scripts

For user-developed IDEsupport

In theory, we should be able to introduce more people to the development of basic development environment should be able to properly use the current Web AI affect the general users in the design flaw serial MaxiPy IDE, although the future can give support for it, but it must be established in better IDEon a selective basis, the future can be based on other editors to develop plug-ins or rewritten IDE.

• Theoretically a situation when hardware repairs serial port can be used temporarily MaxiPy IDEinstead of the general development of the occasion.
• However, MaxiPy IDEno file management function, which requires the use of rshellor mpfshellsuch basic tools, you can also use vscodesome of the micropythonsupport tools, easy to upload files to the internal storage dependencies for calls.

Therefore we need a clear demand, exactly what you want IDE, whether the official should be based on the idea to do, or is divided version maintained, should seek to make the best results with the least cost.

In fact still have to return to point possible to assess the needs of the user demand, the current individuals evaluated for one out of habit, and dedicated IDEshould meet the following basic functions.

• Version can be determined and connecting WebAIhardware.
• It can be obtained relatively easily and out of the box.
• Python meet the basic code editing features.
• Able to manage internal documents, such as upload and download or delete files.
• Preview function to support aspects of AI, or video, GUI design, too, it is the need for a frame buffer.
  • 
• From this perspective, there is not enough under the circumstances manpower, or conservative, to use maixPy ideexcessive as well, such as the above-mentioned functions have a corresponding code solutions, we can consider integration into a new IDEorder to replace it .

Comprehensive verification of hardware resources

Currently personally I think there is a problem

The first, as RD was not MaxiPythe official version control verification, which is problematic (unaware of their peers will not do), because we are doing is based on the proven program development, should not be used immature hardware in the hardware develop, easy to slow down the progress of software development.

The second is the use of hardware should determine the scope of what the user might need, market research should not be under insufficient to make a selection, perhaps because there is only this one? In particular, to avoid the possibility of misunderstanding, after all, the hardware could not be applied to all scenarios, then the time should be relatively clear this hardware basic parameters and accurate hardware attributes.

Third, unit testing should establish as early as possible, whether it is supplied to the plant capacity measure, or provide developers do hardware checks are very helpful, is running further micropythontesting framework.

Fourth, in the distance before the final version, firmware, hardware resources relevant code should be relatively correct, to prepare for the development and factory firmware consideration.

Follow the development of basic Web BIT

If you press product line planning point of view, should be to iterate the previous features, such as the further integration of the previous code resources, and Sync to develop Web BIT among integrated product thus formed is conducive to future product architecture reused, from the future of the entire product line, is advantageous.

Effective project communication is necessary

Say.