Boot sequence (SoftwareInit.Init()) (TEP107) renders problems (for example on TEP122 requirements)

[GoogleCodeExporter]

What steps will reproduce the problem?

There is unpredictable problem to use other software components in SoftwareInit 
(like call to (probably) uninitialized Resource.Request()). 
Problem is in order of calls that is not defined ("TOS programming book" in 
chapter "4.4. Multiple wirings").

TEP122 requires that "The EUI-64 node identifier MUST be available before the 
Boot.booted() event is signalled." The statement is not satisfiable and I got 
two errors:
- I have ID on shared SPI bus (yes can be emergency pooled without 
arbitration). 
- I have ID on shared I2C/TWI bus that use interrupt transfers and interrupt is 
disabled during SoftwareInit (atomic).

Please provide any additional information below.

Discussion started here:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2012-February/053886.h
tml
http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2012-February/005076.
html

Can "TinyOS 2.0 Core Working Group" suggest resolution ?
The additional initialization layer between SoftwareInit and Booted can be 
needed (with interrupt enabled). 

M.C>

Original issue reported on code.google.com by M.Cerv...@computer.org on 15 Mar 2012 at 11:37

[GoogleCodeExporter]

The boot sequence TEP (107) has some suggestions. E.g., don't handle 
interrupts, rather spin on interrupt flags.

Original comment by philip.l...@gmail.com on 28 Mar 2012 at 3:36

[GoogleCodeExporter]

Original comment by philip.l...@gmail.com on 28 Mar 2012 at 3:36

• Changed state: Done