1,多完善资料手册,文档。
2,出一些实际案例,更容易上手。
3,中文中文٩( ‘ω’ )و
- 可以在wiki添加更多入门实用例程,例如点灯,舵机控制,语音,点屏等,方便刚来的初学者或者想要快速上手做应用的
- 可以针对开发板编写类似rpi pico的getting-started-with-pico这样的简单入门文档
- 硬件生态有待完善,例如duo的底板,以及摄像头应用
- 可以在wiki提供更多关于芯片的细节描述
发布的板子上手难度似乎有点大,需要更多的入门教程和芯片相关的文档,当然最好是本土化的中文文档
希望可以出一个入门教程吧,例如点个灯什么的,先用起来再说。
1.希望资料更加完善,包括中文文档;
2.多出一些例程;
3.DUO底板别球球再鸽了;
4.我知道抽不中我,那么Mars什么时候开售?
希望Milk-V官方多出一些教程,玩嵌入式,一种是玩内核和外设,另一种是玩应用,玩应用需要建立像树莓派一样的生态,不然门槛太高,另外可以激励开发出新玩法的玩家。鼓励这些玩家将相关功能做成易于调用的API,RISC-V冲冲冲
Only just got my hands on the MilkV Duo so only scratched the surface.
Some initial observations:
The SD Card blocks the ethernet, so it seems at first glance to be difficult to have both SD card and ethernet.
No wireless capabilities is a bit of a shame – hopefully in the future see a board with this!
However, so far I’m very excited and now need to start planning some projects! Keep up the good work! 加油!
1、底板得上进度了呀。现在飞线联网太麻烦了
2、没啥文档资料。上手全靠论坛大佬分享
3、求求給个能玩摄像头,买也可以,快上架吧
试下回复,刚才一直回复报错,测试回复。。。。
- 核心板的GND应该与铺铜采用十字连线,GND引脚散热太好,烙铁焊接太麻烦。
- 官方的预编译镜像太少。
- 官方自己公布和测试的功能太少了,基本都靠用户自己造轮子。
- 官方资料基本都是库,用户造轮子也比较累。
- 这个论坛的回复有问题,经常报下面的错误。
An error occurred: Body seems unclear, is it a complete sentence?
官方资料过少,生态也需要完善,不能只推板子,不做教程;
板子再强大,没有完善的生态,也是白瞎;
希望多出一些官方教程,我也不想让手里的板子吃灰,奈何自己水平不够,只能靠论坛大神的分享
希望文档和实例工程多一些,才能更好的参考和开发。
中奖!
用户自己绘制拓展板子并公开,这些项目不够集中,要是官方有所指引更方便资源的利用。
Currently the Duo board lacks extensive documentation and examples, additionally adding support for frameworks such as the Arduino IDE would help to develop popularity.
呜呜呜,把duo这个56脚的主控换成那个有DSI的88脚的主控吧…
这款处理器的资料较少,缺乏相应的教程,入门难度相对较高,除此之外,缺少ai模型的优化,在进行ai计算时,表现不如预期。
1、 希望提供一些有趣实用并且容易实现的示例吧,例如语音识别。如果duo配套摄像头出了可以给一个yolo示例
2、 资料开放度仍然不够,目前CV1800B还有很多强大的特性没有用上,希望开放更多资料包括TPU,外设,以及小核的开发等
3、 Pioneer对于一般人有点贵了,以后可以出一个最低成本的廉价主板
Excellent product! The details and specifications are well thought and designed. The next “B” version upgrade should have 2.5GB Ethernet.
Duo 增加SPI NOR FLASH 启动的相关文档
The content of the reply should be about the current shortcomings of Milk-V or suggestions for Milk-V
First suggestion: ensure that every board you make has dedicated storage for the “bootloader”, for example SPI Flash. Mis-using the main user storage (SD card, eMMC) as the startup source for the CPU is the main thing making the ARM platform hard to understand to newcomers. Computers should not be made to look dead when booted without storage attached.
Relatedly, for making things easier for end-users: while all LEDs should be software-controllable, at least one should be inverted such that the default state when the power is applied is ON. This way, it is easier to ascertain that the hardware is being powered correctly. The next startup stages can turn it off and turn on another LED as needed, or different various schemes can be used (e.g. RGB LED) for helping end-users out.
Finally, I do not know if it is or not already the case, but here goes: work with mainline projects. This means working directly, hiring (funding) developers to add support for the hardware in Linux and U-Boot at the source, and not on forked vendor BSPs. Relying on mainline support would elevate Milk-V above the crowded space of SBC-class hardware nicely.
Cheers!