Programming the PSoC

[PortugazD.Ace]

Does anyone have any idea how to program the PSoC from the kit of parts. Or how to use it? If anyone has any information on the matter, please post.

[jhersh]

Originally Posted by PortugazD.Ace

Does anyone have any idea how to program the PSoC from the kit of parts. Or how to use it? If anyone has any information on the matter, please post.

You can use it in one of two ways (or both I guess if you buy another one)...

It can be used on the classmate Driver Station to provide access to custom I/O such as buttons, knobs, LEDs, etc on your driver console. You must use the official provided firmware if you wish to use it this way.

It can also be used on the robot in any custom way you choose (i.e. a sensor interface for any special sensors you decide to use). You must make your own design and firmware for it in this use case. The easiest way to interface it with the cRIO is probably with I2C, though there are many other ways that are possible.

[PortugazD.Ace]

custom firmware???? Umm, can you put that in plain english?

[jhersh]

The PSoC board has a processor and some reconfigurable mixed-signal logic fabric on board. Basically, you would need to write your own code to run on the board if you use it on the robot.

The expected use case for 99% of teams is that it will be used with the driver station to wire up buttons.

[Geek 2.0]

Originally Posted by jhersh

The PSoC board has a processor and some reconfigurable mixed-signal logic fabric on board. Basically, you would need to write your own code to run on the board if you use it on the robot.

The expected use case for 99% of teams is that it will be used with the driver station to wire up buttons.

Are we allowed to write our own code for it? I was under the impression that we had firmware given to use by FIRST that we had to use. Didn't see anything in the rules about it.

[Joe Ross]

Originally Posted by Geek 2.0

Are we allowed to write our own code for it? I was under the impression that we had firmware given to use by FIRST that we had to use. Didn't see anything in the rules about it.

See <R60N>

[Geek 2.0]

Originally Posted by Joe Ross

See <R60N>

...How can the FirstTouch NOT be used as a part of the Operator Console?

[EricVanWyk]

Originally Posted by Geek 2.0

...How can the FirstTouch NOT be used as a part of the Operator Console?

It can be used on the robot as a piece of custom electronics. In that case, you are allowed to reprogram it as you see fit.

[jhersh]

Didn't I say all this yesterday? ...in the second post?

[PortugazD.Ace]

BTW, how would I connect it via I2C?

[jhersh]

Originally Posted by PortugazD.Ace

BTW, how would I connect it via I2C?

If using it on the robot, you just pick two of the pins, map them to an I2C peripheral in the PSoC and then wire it up to a digital sidecar.

[PortugazD.Ace]

Wha????

[Alan Anderson]

If you didn't understand any of that, you probably shouldn't try anything so advanced just yet. You can work on programming the board in the off-season if you like.

[PortugazD.Ace]

Thanks for the encouragement. |(

[Jason Law]

Hi -

From the past few posts, I am under the impression that I do not need to connect or do anything with the PSoC board if we choose not to use it for any of the above things. Is that correct? In other words, I am asking if it is required to be used and connected to the Classmate PC. I read the control system documentation and did not see anywhere that it said that I needed it. Please tell me if my interpretation of these things are correct.

Thanks.