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

[Ole Reinhardt]

Hi all,

I just spend two days in hunting an abort exception right on boot time.

The problem was quite simple:

The configurator script dev.nut includes a configuration for AT49BV
Flash chips even if the CPU does not have an external bus.

This config defines the FLASH_CHIP_BASE macro which again is used in
at91_efc.c and is defined there only if not defined in any other place.

In short: As it is just defined for the AT49BV chips, this macro is not
redefined to the settings needed for the internal flash of some AT91
chips.

I solved the problem in renaming the 

FLASH_*** constants in at91_efc.c into EFC_*** constants.


But now my RFC:

I would suggest to add a "conflicts" statement (in oposit to the
requires statement) into the configurator scripts that allows to define
conflicting configuration options.

So we could say AT49BV does conflict with MCU_AT91SAM7X512 for example.

Any further ideas?

Regards,

Ole

-- 

Thermotemp GmbH, Embedded-IT

Embedded Hard-/ Software and Open Source Development, 
Integration and Consulting

http://www.embedded-it.de

Geschäftsstelle Siegen - Steinstraße 67 - D-57072 Siegen - 
tel +49 (0)271 5513597, +49 (0)271-73681 - fax +49 (0)271 736 97

Hauptsitz - Hademarscher Weg 7 - 13503 Berlin
Tel +49 (0)30 4315205 - Fax +49 (0)30 43665002
Geschäftsführer: Jörg Friedrichs, Ole Reinhardt
Handelsregister Berlin Charlottenburg HRB 45978 UstID DE 156329280