This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001442] LPC17XX bit band macro proposal

Please do not reply to this email. Use the web interface provided at:

--- Comment #4 from Ilija Kocho <> 2012-01-13 15:45:20 GMT ---
(In reply to comment #3)
> (In reply to comment #2)
> > Perhaps the macros (especially for RAM but others could be considered) could
> > have generic stem CORTEXM rather than LPC17XX. Could they be applied at
> > architecture level?
> I've checked on the ARM site: 
> - on Cortex-M3, bit banding is described as a feature always available (the
> word 'option' is not used) :
> - on Cortex-M4, bit banding is described as an optional feature:
> eCos uses 'cortex-m' to describe the architecture generally and does not make
> difference between M0/M3/M4, etc. Now maybe all chip manufacturers will
> implement bit band?

Actually there is info on sub-architecture: CYGHWR_HAL_CORTEXM (in

> However if bit banding is provided, it's always at the same place, it seems
> that it has been designed mostly for peripherals registers or for peripherals
> that maps into RAM, like the GPIO pins in the LPC17XX.

What I mean is: The macros can be used by every Cortex-M member that implements
bit banding so they should be generic (within Cortex-M) rather than bonded to a
specific product line. Then, they should reside in arch. level header.

> > 
> > Also, could we consider defining a USER_SECTION for bit-band area? Then we
> > shall have an easy way to put objects there by just __attribute__ing.
> > USER_SECTION can be added to present ldi scripts without breaking
> > compatibility.
> This is necessary if one wants to use bit band for RAM, for instance to place
> device descriptors or buffers at location that allow bit banding.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]