How to develop a monitor in embedded system?

[flylionking]

a monitor:
it can monitor hardware activity, can load/flash firmware, can execute simple commands(read/write memory, debug printf.etc.)

pls provide information about this to me.
Thanks in advance.

 

[akouz]

Use Forth, such as SwiftX: https://www.forth.com/embedded/index.html
It has all the functionality you wanted

 

[flylionking]

I can't study forth.
It's unpractical.
I want to know how to develop it personally.

 

[eltonjohn]

There are several Open monitors for the 51 .. just browse the net ,I think if you study one of them ,you could modify it to suit your needs .
https://www.pjrc.com/tech/8051/paulmon2.html
**broken link removed**
Search the net man ..there is a lot of this stuff

 

[akouz]

I can't study forth.
It's unpractical.
I want to know how to develop it personally.

Do you want to develop Forth yourself without studying? 8O
I think it is much more practical to study and use existing implementations rather then try to re-invent the wheel.

 

[flylionking]

eltonjohn, thank you!
OK. What key words do I search?

 

[flylionking]

I can't study forth.
It's unpractical.
I want to know how to develop it personally.

Do you want to develop Forth yourself without studying? 8O
I think it is much more practical to study and use existing implementations rather then try to re-invent the wheel.

Study forth, it needs more energy and money, time.
Otherwise, I don't know how much forth can help me.

 

[eltonjohn]

The 8051 is one of the oldest micros .so chances are that you will find more of developed stuff ..so do "

Monitor 8051

 

[dainis]

For 32 bit CPUs look Micromonitor by Mr. Ed Sutter:
**broken link removed**

MicroMonitor is an embedded system boot platform centered around an extensible embedded flash file system called TFS. With TFS in the monitor, things like XMODEM and TFTP (also in the monitor) can now refer to files instead of address space. The whole boot-up strategy is driven by the content of one or more files that can be scripts or executable images. The file system is accessible at the command line and through an API accessible by the application. The API provides a flexible means of reading and writing files in flash, plus the TFS implementation provides power-safe runtime defragmentation as the flash fills up. A network-accessible, MicroMonitor-based embedded system provides a firmware development project with immediate network boot (DHCP/BOOTP), file based maintainability, in-field upgrade and in-system diagnostics. The firmware assumes a CPU with linear address
space and is not suitable for a microcontroller simply because of the large feature set.

Mr. Sutter offers his sources under Lucent's Open License. Micromonitor supports many CPU architectures, including all of the Cogent Computer Development Boards. The sources build with GNU X-Tools on Windows and Linux host platforms.

 

[flylionking]

Thanks, dainis.
I am reading Ed Sutter's book "firmware demystified".
His Micromonitor is OS independency.
If use RTOS, is it easier?