Ardumower future PCB: Unterschied zwischen den Versionen
Aus www.wiki.ardumower.de
(→Flashing the CPU) |
(→Running new code on the CPU) |
||
| Zeile 19: | Zeile 19: | ||
=Running new code on the CPU= | =Running new code on the CPU= | ||
Running new code on the new CPU should be simple for end-users. Some ideas: | Running new code on the new CPU should be simple for end-users. Some ideas: | ||
| − | * For debugging purpose, a serial connection (TX/RX) should be available | + | * For debugging purpose, a serial connection (TX/RX) should be available running new code, debugging |
* For end-users, a small binary (SD card) should be available for download | * For end-users, a small binary (SD card) should be available for download | ||
Version vom 22. Januar 2016, 13:08 Uhr
Inhaltsverzeichnis
Abstract
Not really a future PCB, but some ideas for a future Ardumower HW/SW architecture...
Architecture
- existing MCU (Mega) board for the controlling (actuators), sensing (sensors) - basically, current Ardumower PCB
- new CPU board for high-level control (brain)
- commuincation interface and protocol (based on RS232 interface and session protocol)
- additional (plug&play) IDE (including compiler & drivers) for the new CPU board
- Java interface?
CPU hardware support/drivers
- For the driver side, ChibiOS could be a very nice start . It's an RTOS with high integration of hardware drivers , FATFS integration, LWIP etc... http://www.chibios.org/dokuwiki/doku.php?id=chibios:matrix
IDE/compiler for CPU
The IDE and integrated compiler should be plug&play (like Arduino IDE).
- emBlocks (integrated compiler for many CPUs including Rasperry PI, STM32, etc.)
- chibistudio (modified Eclipse)
Running new code on the CPU
Running new code on the new CPU should be simple for end-users. Some ideas:
- For debugging purpose, a serial connection (TX/RX) should be available running new code, debugging
- For end-users, a small binary (SD card) should be available for download
