It's coming along, but going through lots of iterations. It's on its way to being complete. As soon as we have it done, we will post a picture.

Iterations are very common on PCB designs

If there is room, could you include a SON16 footprint, for the NAU7802 ?

That's a low cost i2c 2 Ch 24b ADC, that could be used to calibrate/prove any of the DAC's and ADC's in P2, as well as monitor Current draws.
(includes temperature sensor) Digikey shows good stock levels.

It's coming along, but going through lots of iterations. It's on its way to being complete. As soon as we have it done, we will post a picture.

Iterations are very common on PCB designs

If there is room, could you include a SON16 footprint, for the NAU7802 ?

That's a low cost i2c 2 Ch 24b ADC, that could be used to calibrate/prove any of the DAC's and ADC's in P2, as well as monitor Current draws.
(includes temperature sensor) Digikey shows good stock levels.

Every eight pins come out to a 2x6 header. We can make all kinds of little add-on boards. That's where that part should go.

It's coming along, but going through lots of iterations. It's on its way to being complete. As soon as we have it done, we will post a picture.

Iterations are very common on PCB designs

If there is room, could you include a SON16 footprint, for the NAU7802 ?

That's a low cost i2c 2 Ch 24b ADC, that could be used to calibrate/prove any of the DAC's and ADC's in P2, as well as monitor Current draws.
(includes temperature sensor) Digikey shows good stock levels.

Every eight pins come out to a 2x6 header. We can make all kinds of little add-on boards. That's where that part should go.

It's coming along, but going through lots of iterations. It's on its way to being complete. As soon as we have it done, we will post a picture.

Iterations are very common on PCB designs

If there is room, could you include a SON16 footprint, for the NAU7802 ?

That's a low cost i2c 2 Ch 24b ADC, that could be used to calibrate/prove any of the DAC's and ADC's in P2, as well as monitor Current draws.
(includes temperature sensor) Digikey shows good stock levels.

Every eight pins come out to a 2x6 header. We can make all kinds of little add-on boards. That's where that part should go.

That's a great way to make prototyping a project easier. I did something similar to the first Propeller (Protoboard) I purchased. Brought all the I/O, Gnd, +3.3V, and +5V out to 2x8 pin headers so peripheral boards could be connected by a short ribbon cable or plugged in. Made prototypes much neater and more reliable. Still use it as my main prototyping board.

David,
It's ~140 chips. There are also ~1500 dies on the uncut wafers.

140 is plenty for me but what are the rest of you going to do?

That 140 does not sound like very many, but Chip said something earlier about OnSemi 'business model' not wanting to release more.
To me, that stance seemed somewhat confused thinking, as it is in OnSemi's long term interest to have P2 ramp as quickly as possible. To do that, maximum bug-shakeout is needed, along with code-evaluation for device design-in selection for 2019.

Or maybe that was code for OnSemi wanted more $$ to release more packaged devices, and Parallax wanted to save some money ?

Something like this. Initially, it seemed that we'd have around 1K chips, but we're packaging less since we're going for another round. This means we'll have around 100 boards made.

What to sell them for? Don't know that it even matters. It's not as if 100 boards will help us start to recover the investment, especially with the PCB non-recurring engineering costs, machine setup, etc. The purpose of these 100 PCBs is to get a solid start on the development tools, code examples, and really shake out the chip's behavior.

What to sell them for? Don't know that it even matters. It's not as if 100 boards will help us start to recover the investment, especially with the PCB non-recurring engineering costs, machine setup, etc. The purpose of these 100 PCBs is to get a solid start on the development tools, code examples, and really shake out the chip's behavior.

I think 100 PCBs should be enough for the early adopters.

The 100?/140?/160? parts need to split across 2 PCB designs that are active, and you may need some means to ration & limit totals, if just 100 in total.
For some P2 tests (like fast serial links), and for backup 'slip insurance' & second opinion checks, means many users will like to have 2 boards.

If your focus is explicitly on "get a solid start on the development tools, code examples, and really shake out the chip's behavior", then you may need to filter out those who (for example) wanted to start product development and design start evaluation.

On that angle, I'm surprised garryj who has been doing the USB code development, did not get one of the very first lot. USB has to be vital to P2, surely ?
garryj mentions things like " In general, USB 2.0 parts work well, but 3.x parts can be finicky, which I think may be related to the current 80Mhz ceiling." in other threads. ie FPGA platform is sounding wobbly, whilst a real P2 allows elastic clock movement to check that aspect.

On that angle, I'm surprised garryj who has been doing the USB code development, did not get one of the very first lot. USB has to be vital to P2, surely ?
garryj mentions things like " In general, USB 2.0 parts work well, but 3.x parts can be finicky, which I think may be related to the current 80Mhz ceiling." in other threads. ie FPGA platform is sounding wobbly, whilst a real P2 allows elastic clock movement to check that aspect.

Agreed, USB is of utmost importance. You might be overestimating our ability to manage this process, at least at this point. While Chip has been busy with engineering, I've actually been out of the office a few weeks. And the rest of the team - they have been putting all efforts into our educational programs. Without these efforts, there would be no P2 (by now, forum members are likely tired of me pointing this out). We will identify and take care of the key contributors, including garryj. Thanks for pointing this out to us.

But when I get back next week I will be turning my attention to the Propeller 2's planning and integration into our product line. From finances to who gets these boards and where information is hosted, I expect that we'll get quite organized in the coming weeks.

If your focus is explicitly on "get a solid start on the development tools, code examples, and really shake out the chip's behavior", then you may need to filter out those who (for example) wanted to start product development and design start evaluation.

Yep, which is why I've resisted putting my name on the unofficial list each time that I saw someone understandably express interest. While the squeaky wheel gets the grease, I'm not a tool developer or a driver creator, so I'd rather see "my" board go to someone that can "hit the ground running" and contribute to testing the chip, characterizing it, or developing the ecosystem (programming tools or drivers), such as garryj like jmg mentioned. As another example, if someone is porting over an SD card driver, such as Kye's with sub-directory support, that's something that could benefit lots of folks (I believe that Cluso99 has done some work in that regard). Of course, cool products or applications that utilize the P2 could also help the P2 garner attention and gain momentum, but the time for such things will come. If good things come to those that patiently wait, here's hoping that better things come to those that impatiently but willingly wait (the camp that I'm in). Anyway, I think things are happening in an orderly way and will continue to do so as more chips/boards become available. For example, it certainly made sense for a couple of test chips to go "down under" where a lot of development activity has taken place. So, one way or another, it's all going to work out pretty well, and Parallax will help see to that. But the nerve of you folks asking for two! Shame on you! No soup for you! Ha-ha.

If your focus is explicitly on "get a solid start on the development tools, code examples, and really shake out the chip's behavior", then you may need to filter out those who (for example) wanted to start product development and design start evaluation.

So, one way or another, it's all going to work out pretty well, and Parallax will help see to that. But the nerve of you folks asking for two! Shame on you! No soup for you! Ha-ha.

Man, I hope you're joking... I can speak of myself, but be sure "the nerve of asking for two" was done in the perspective of getting 1500 chips packaged and put on boards.
I'd be more than happy if I can't get one, or even zero if that means that it goes in "better" hands.
By better I mean not only recent, but also historical contributors, should they decide to ask for one (COME ON JEFF LEDGER, GET ON THE LIST! )