Yes, it's P1.0 and P1.1. However, those pins are only made available on the debugger header, so I wouldn't expect any add-on board you've made to affect them. The only other possibility is the Reset pin, which is on the Arduino header. Is it possible that you're affecting that pin somehow?

You can use the USB target port as a USB-UART to send data, OR you can use the USB debug port to send data as well. If you're using Arduino, there's no debugging mode, just USB-UART upload. If you're using PSOC Creator, the debugger is automatically recognized.

Thought I'd give you a heads up to check full connectivity on these. I think these might be in ding and dent because they were manufactured as 2 layer boards and not 4 layer boards. Make sure you have all 4 layers before trying to get parts to make it work :)

You're right. The target is bootloading over USB, so you're free to use the debugger for other purposes; it has a bootloader of its own, as well (although not one compatible with AVRDude).

I had a similar problem, and believe I somehow got into Mass Storage mode. What I did to fix it was to power the board from the target (not Debugger) micro USB. It wouldn't work when powered from the debugger port. Then I pressed and held the target reset button for 5-10 seconds. When I released the button, and reconnected to the debugger port, the board connected as normal.

While I don't see people using this as a simple Arduino replacement, I can see people starting with the Arduino configuration and code and then modifying it. If you need 30 analog pins you can write your Arduino code, open the Arduino configuration, remove the stuff you don't need, add more analog pins and be done. It might take a bit of effort for the Arduino IDE to understand what you mean by A30, but being able to use all the prebuilt libraries for the pins you want is a nice feature. Just my $0.02

There probably isn’t much point in using Arduino-compatible APIs

I would have to disagree with you there. While an Arduino style environment would certainly not be the best API for this chip in a consumer product, like a oscilloscope thingy. An Arduino API does however perfectly suit the role SparkFun is aiming the board at.

At the moment, it's Windows only. Hopefully that will change soon.

22pf is acceptable. [This part(http://www.digikey.com/product-detail/en/C1608C0G1H220J080AA/445-1273-1-ND/567670)] from Digi-Key will be adequate.

Future versions of the board will have through-hole pads for those parts.

Perhaps, but unknown at this time pending future sales and engineer availability.

I'd like to make a number of add-ons for it: a full-size protoshield (to supplement the normal Arduino one which works well with the FreeSoC2), per-port protoshields, and an SD card add-on that could connect to one of the 2x10 headers.

Okay, this is an ESR issue with the output capacitor on the 3.3V supply.

We'll fix it in future boards; in the meantime, if you remove C8, that will fix the problem.

Here's a picture showing the capacitor that needs to be removed.

Note that the analog subsystem draws from the 5V regulator, so it shouldn't be affected by this issue.

Same here. Got the email and whacked the scope on it and can confirm what TDDGuru says. Removed C8 as pictured in SFUptownMaker's comment and confirmed it to be clean afterwards. Thanks for the heads up, SF!!!! Just out of curiosity, what regulator is that for the 3v3 rail?

Yes, actually. That's very odd. Let me see what I can figure out.

There are downsides to that. The Arduino standoff positioning collides with headers, for instance.

There aren't many Mega shields- basically, just the protoshield. The Mega pin placement is poorly designed: the ration of data pins to power and ground pins is too low.

In other words, these were carefully considered design elements.

I think what you are seeing are the locking header footprint that we use to keep the headers stable in the selective solder machine. The headers are actually on straight.

This is just my observation on the pictures. I have not ordered one of these.

After a fashion. I'm not sure yet what the terms of the license are, nor where Cypress stores it.

Ideally, it'll soon be on GitHub. If I can't get the official version up on GitHub and managed by Cypress, I'll get the 2.11 version that's on there right now, at least.

I re-wrote the SPI, Wire, and Servo libraries so they'll work with it.

I know from testing that the WiFi library provided by Arduino works at least well enough to use a couple of the examples, and that our APDS-9960 and MicroOLED libraries work, too.

It all depends on how the library was written. If it was written entirely in "Arduino", it should work. However, if the author used any processor-specific resources, registers, assembly language, or anything like that, it probably won't work.

The Cypress prototype board is priced well under the cost of the chips on it. It's unlikely they will welcome quantity orders for it, such as you might need if you were going to build 100 of something. The two PSoC chips alone on this board would cost over $35 in single quantity and $30 in quantity 100 so the price of the complete board seems fair.

Doubtful. I think, physically it would fit in there, but the holes aren't going to line up with the stand off screw holes, and the ports in the end for cables almost certainly won't be in the right place.

Fair question. If you plan to use it in the Arduino IDE only, it's got more I/O, more memory, and is faster than most other comparable boards. The Due is faster and has more memory, but it runs at 3.3V which excludes a lot of shields.

Once you move into Creator, though, the possibilities explode. The onboard analog circuitry allows you to do a lot of really great stuff onboard, for instance, things that would normally require a lot of external active circuitry.

Or, for the programmable digital circuitry, you can implement a custom hardware I/O interface. For example, there's a module that allows you to interface NeoPixel-type LED strips without having to bit-bang and cycle-count I/O, which frees up a tremendous amount of processing power.

Asking "why" is IMHO, among the more enlightened questions. I kind of shook my head when I saw this product on cypress.com and came here. $49 is a big wad of money. I just replied above and remarked about the amazing options for embedded development for small $. I'd think a likely next step from Arduino is ChipKIT's Uno32 and uC32. Microchip's mpeide is familiar to Arduino ide users and their boards have TONS of RAM, extra uarts, and run at 80MHz.

Next step up are when we open our minds to alternatives to Arduino IDE. After mpeide, I believe Cypress's windows tools are the next friendly, then NXP's toolchain, and I haven't been able to make Ti's Launchpad toolchain work yet (gave up after a couple hours).

Cypress' PSoC data blocks are a game changer. I'm an EE with embedded experience and this new dimension is mind blowing to me. And starting at $4? I bought 4 just because.

Nope, sorry.

That was a conscious choice on my part. The downside of the mega is that the data:power pin ratio is really poor. The extra I/O headers on the FreeSoC2 all provide two extra grounds and two extra VCC pins for each port, and if sales of this go well, we'll start releasing extra boards that can be hung off those 2x6 headers.

I essentially did that, as well.

If you visit the Arduino support repository, you'll find a project called "Uno_blocks". That project has a sketch.cpp file included in it, and if you write Arduino code in there (in the setup() and loop() functions), you'll find it works just like Arduino.

The only real difference is that the Arduino IDE creates function prototypes for you, and Creator won't do that, so if you write new functions you have to remember to create the prototypes as well. All your old friends are there, though- Serial.write, digitalRead and digitalWrite, etc.

Yes, the PSoC combines an ARM processor, a programmable/configurable Analog front end, some programmable logic (more like a PLD than a full blown FPGA), as well as a programmable 8-bit datapath. The native development environment includes has Verilog synthesizer buried in it, if you really need it, but most of the time, you are expected to simply instantiate a soft block from their list of existing blocks that combines PLD , datapath and analog resources.

In any case, the Arduino part simply sounds like they ported the Arduino libraries to the board. The Arduino environment already supports an ARM processor.