[En-Nut-Discussion] RFC: "conflicts" statement in configurator scripts

Harald Kipp harald.kipp at egnite.de
Thu May 26 14:56:05 CEST 2011


Hi Ulrich,

On 5/25/2011 9:05 PM, Ulrich Prinz wrote:

> I hit that NutConfig part several times, where Nut/OS tries to read out
> a memory just to detect its own name. I had to modify that part as my
> Cortex CPUs use the last flash page for this instead of external memory,
> but I still leave it to a users choice to select any external memory if
> he prefers.

Same here. If a board is completely quiet after starting a Nut/OS
application, in most cases it hangs in the nvmem routines

The other problem is, that nvmem drivers are not always trivial to
implement (e.g. Atmel's EFC). It is a real burden for new platforms to
have this provided before Nut/OS will start running the application.

Thus, I'm dead set on removing this requirement in the next release.
Even the network parameters (IP, MAC etc.) may be done in the
Configurator in an early state.

Regards,

Harald



More information about the En-Nut-Discussion mailing list