Hi all, What protection does eCos provide for MMU-less micro controllers, for example when a process want to do memory altering outside its permitted allocation area, and for that matter to protect itself (the OS)
I have some simple questions regarding the HAL layer of eCos after reading A Massas book on eCos. Redboot and eCos use the same HAL. If redboot is compiled for ROM mode it produces a binary image that is structured as defined on page 187, which include a HAL layer and device drivers. Now if you compile the eCos default template, it results in a library that contains the HAL and device drivers as well? Resulting in 2 identical sets of HALs and device drivers? Is this correct, or do I have the integration of it incorrect? And is it possible to end with one HAL and device driver set? According to the my interpretation and the Example application chapter in the book the libraries produces by compiling the eCos default template are implemented(imported) into the example programs and can then be copied onto the chip via redboot and the ymodem. I want to know if something similar to the following is possible and how. I want to load ecos and a couple of applications and be allowed at a later stage to upgrade 1 or more of the applications without having to load eCos with it again as shown in the example provided (I will have very limited bandwidth and connection time to do upgrade). I want to use reboot(purely as a bootloader), what optimization can be done (with regards to Compiler settings and feature removal) once the development is done and the system is to be built for production purposes ie no debug. I removed the g option from the compiler options and it reduced the image size significantly, any other recommendations? Thanks in advance, any advice welcome. Regards, Hendrik Meiring -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
