Fred,
On a quick overview I saw there were two pressure sensors on the board. One for MAP & one for BARO. Is there a specific reason for using both? I am in the middle/nearing completion of designing a system (Scary similar to FreeEMS - So I don't contaminate this thread, I'll post some details as soon as I figure out where on the forum it's appropriate & get a little free time.) & my current code just samples the MAP sensor on bootup & stores it off as BARO. This obviously makes the the assumption that car isn't running, or the starter isn't even engaged at board bootup (both of which are of course detectable) I was going to log each bootup reading so I have a known ballpark (fallback BARO) in case I detect an out of bounds at boot, or if the watchdog resets and the ECU re-inits while engine is in fact running.
I had thought one could probably even get a BARO ( a little noisy perhaps) anytime someone goes WOT. That would give me a reason to floor it while climbing Pikes Peak.

"But officer, my lambda was going to shit!. I had to punch it. "
I do like the concept of having two sensors. You could at least compare the two at bootup to prove that the more critical MAP sensor isn't drifting/broken or othewise behaving oddly.
A #define would allow someone to build without the second sensor for *some* cost saving. Apologies if this has already been thought of/implemented, ect.
Anyhow, great work so far by all!
Lenny