I was checking Kickstarter today and found this: https://www.kickstarter.com/projects/land-boards/pisoc?ref=home_recs.
The project incorporates PSOC 5LP from Cypress on a custom hat. What do you think?
I was checking Kickstarter today and found this: https://www.kickstarter.com/projects/land-boards/pisoc?ref=home_recs.
The project incorporates PSOC 5LP from Cypress on a custom hat. What do you think?
During forget me not design challenge Christian have sent rpisoc boards that uses i2c of RPI for communication.. And powerful APIs are available for access multiple blocks of psoc5lp...
The board could be useful, but US$55 plus ship is way expensive -- more than the RasPi base board. As others have pointed out upstream, you can get a $10 Cypress board that performs the same functions, though it doesn't directly plug onto RasPi and block air flow.
As I have said many times over the years, I really like PSoC4/5 technology but I won't use Windows-based software unless someone pays me to do it. Cypress provides the technical references needed to program everything in PSoC4/5 except the routing. Until the routing information is published, you're stuck using PSoC Creator on a Windows machine. There are no open-source tools available like IceStorm for the Lattice iCE40 FPGAs.
I am the original designer so I have a biased opinion. Hoping maybe I can answer some of the questions/objections above.
Is it worth the money?
It is a bit pricey at $50 (for early backers). The PSoC chip goes (as noted) for around $7. The PCB costs a few dollars (in the under 100 volume), the connectors and hat EEPROM cost another few dollars. It costs around $10 additional to assemble and test the card. So the selling price of $50 is around 2-3x the costs. That's high if it was made in volume and purchased from China. It's not. We build them in my living room. I am going to build around 50 or so of these cards (maybe 100 of them if the Kickstarter goes well) so there's not all that much economy of scale involved. In the end I might end up with $1000 or so profit which will go into my next project.
Why hook up all of the Raspberry Pi GPIO lines?
Think about this one a bit. If you want an input pin connected just connect it inside the PSoC to one of the I/O pins. Same goes for output pins. Just route them through the PSoC. What about Bi-directional pins? Someone mentioned One Wire. The Pi really stinks at interfaces which have specialized timing. You get a packet in on the Ethernet and all of a sudden you are preempted - ouch. That's where the beauty of the PSOC comes in handy. The ARM processor inside the part does a great job in those situations. Try handling the timing of a chain of NeoPixels with the Pi. It's not a great bit-banger. The ARM CPU in the PSOC is great at bit-banging.
Is this just a Marketing Ploy?
Hardly, I'm horrible at Marketing. I just put up projects that I do for myself. If someone else made the card for $30 or $35, I'd buy it and not build it. I think an entire University class could be built around this card. Can you imagine the possibilities of breadboarding a fairly complex design with minimal breadboarding?
But I can just buy the $10 Dev Kit from Cypress!
Of course you can. We did too. That's what got us interested in the part to begin with. Is it a Raspberry Pi Hat or is it a breadboarding tool? If you want to do breadboards, it is just fine. If you want to build something beyond a breadboard that's another story.
Where's the innovation in this project?
That was a real challenge. Took me a couple of weeks of solid Engineering time to figure out just how to program a PSOC from a Raspberry Pi. You see the limitations of the Pi are the unpredictable timing. The Pi doesn't make a great bit-banging programmer. If someone else had already figured out how to program the part, I would have just used their code. Nobody did, though. Took pouring through the Application notes and the answer was there. But not easy to figure out. And what did we do with the answer? We put it up on our github site for all to see. Some clever stuff there? Surely someone else will come along and say that they would have done it better/differently. But they didn't do it. We did.
Doug at Land Boards, LLC (just a guy and his sons who do stuff together).
Hello Doug,
despite the fact that it is my opinion that this post was the worth you wrote it just for first after the presentation article of your project, I consider one of your point of special interest:
It is a bit pricey at $50 (for early backers). The PSoC chip goes (as noted) for around $7. The PCB costs a few dollars (in the under 100 volume), the connectors and hat EEPROM cost another few dollars. It costs around $10 additional to assemble and test the card. So the selling price of $50 is around 2-3x the costs. That's high if it was made in volume and purchased from China. It's not. We build them in my living room. I am going to build around 50 or so of these cards (maybe 100 of them if the Kickstarter goes well) so there's not all that much economy of scale involved. In the end I might end up with $1000 or so profit which will go into my next project.
IMHO this changes the perspective as (at least by my point of view) the kickstarter phenomenon - and all related backing sites like indiegogo etc. - has none or very low trustability to my eyes. The product - as the facts are - remain almost expensive but probably the most important aspect is that there is no mention of the building details nor the possibility to hack the original version, opening at least a part of the project (or, better, the entire design idea). I think anyway that, maybe with the help of this community a way to make it cheaper with the same reliability can be found.
To be honest I saw the video presentation in your kickstarter page and this was almost evident the discordance with the Kickstarter presentation standard of the other electronic projects / gadgest: all the other are so nice and perfectly done that the first question I ask to myself is always the same: if these guys invested so much creating a presentation of something that does not exists, why don't they save their money and make the project the same? Just the opposite of your case.
About the second point of special interest, where you explain your reasons routing all the 40 PI pins, this sounds reasonable to me but frankly I'd like to have some more details. But I am almost sure that your post got a boost to this discussion and these things maybe clarified soon. If you like this, obviously.
Enrico
I don't know. I think I'd feel guilty charging 2-3 times cost for something that I knew was very similar to a dev-board that was one-fifth of the cost unless there was significant value-add.
Especially if you're targetting university classes - in that case isn't it better for them to save money and use the dev-board for a fifth of the cost?
I understand that you went to effort to port a programmer to the 'Pi, but Cypress Semi created the code that it was based on. Many of us here have ported code and share it
for free too.
I still don't get why you'd connect all the Pi's I/O to your project. The reasons mentioned would all still apply even if you just connected two or three I/O between the two boards.
Doug
Well done for fronting up and answering the questions posed.
We've seen many others simply hide and hope the questions go away and the other backers don't see them.
I understand the need to ensure you dont loose money, but I do question any add-on which costs a lot more than the board it's going on without adding significant extra hardware.
I have the same issues with Freedom Boards and they are a large corporate who could produce a simple prototype board for a few $.
Your breadboard v Hat comment is right, but this site is about Engineers and makers so that argument will always appear unless the cost makes it go away.
Good luck
I won't be backing it ... because I don't have a use for it.
Mark
Trying to understand - but not agreeing - I think that the question is to route (if I am not wrong he means managing pass-through) the PI on the PSoC. The point is that this is an apparent benefit, as the most powerful machine (that in all my project drives the PSoC) is just the Raspnerry, not the PSoC itself.
About the cost, I should say that what I have explained about the cost in my previous post is valid except the multiply factor; btw I suppose that this depends on the fact that the creator is anyway in a commercial perspective where his job (done at home if I am not wrong) is valuable and part of the product cost.
Enrico
Hi Enrico!
Everyone may implement it differently I suppose, but personally I'd route it all using a few pins, e.g. SPI or UART. For example, there might be 5 million phones in London, but there are not 5 million fiber-optic cables connecting London to NY.
I also get the time is valuable issue, but (personally, I don't expect others to feel the same way) I don't like projects that have a risk that others could be unaware that near-similar functionality products are available at far lower cost. It is the same reason I dislike supermarkets that offer a 500gm bar of soap at a higher cost than two 250gm bars of soap, i.e. relying on people not noticing, and the people that are affected the most are those who are poor at sums. I'm not saying that is occurring here intentionally, it is just an example. Supermarkets do it intentionally as far as I am concerned.