P2-ES Board Support
Jeff Martin
Posts: 758
The limited-run P2-ES Rev B boards are available November 2019.
Visit the P2-ES product page for more information.
History: The P2-ES Rev A boards were built and shipped out in December 2018.
This thread is your official place to receive and give support for this product.
Please keep non-support topics for the P2-ES in the Parallax P2 Eval Board thread.
In addition, you can visit the Propeller 2 product page and also can help curate the Propeller 2 Repository by sharing code examples, documentation, and links to resources you and your fellow community members create.
Visit the P2-ES product page for more information.
History: The P2-ES Rev A boards were built and shipped out in December 2018.
This thread is your official place to receive and give support for this product.
Please keep non-support topics for the P2-ES in the Parallax P2 Eval Board thread.
In addition, you can visit the Propeller 2 product page and also can help curate the Propeller 2 Repository by sharing code examples, documentation, and links to resources you and your fellow community members create.
Comments
I know that Parallax is diligently working on spin 2 and other language tools are being developed by several of the dedicated customers, I suspect that these will be as easy to set-up and use as everything for the P1 has been, however not having programmed the FPGA 's, I am at a loss for what I will need to start programming the evaluation board.
I have a board on order that I haven't the faintest idea of what tools are available to program it. I have most of the documentation. I know what's on the board, I've looked at the sample code etc. but I still don't know how I will get code compiled and downloaded into the prototype board.
Could you provide links to information specific to setting up the software tools I will need to start working with my P2-ES when it arrives?
Unlike P1, P2 will run code from HUB or COG. Makes getting started with PASM pretty reasonable. One could load one of the example programs and just add to that. Pnut is really lean. But it does offer the basic, write it, then hit F10 to run flow.
Then we have the tools Dave Hein and Ersmith have made. My FPGA boards got water damaged. I have not used either yet. Both appear capable ofsubstantial programs.
I am pretty sure that gets us C, SPIN, BASIC, PASM.
Peter made Tachyon Forth. A small version if it is contained in the P2 ROM. A fuller featured one is a quick load from sdcard.
I know that I'm missing something that should be obvious, but I've been looking for the past 30 minutes and NONE of the searches in OBEX, Parallax Home, resources, etc. have given me a clue about where I can get pnut.exe.
Even GOOGLE SEARCH didn't bring up any references to Pnut.exe (other than back to Parallax) which seems pretty odd.
I know I'm not the big brain that most of the people who have been doing FPGA work are... but I feel pretty stupid not even being able to FIND it. I'll probably be the only one actually purchasing one of the P2-ES who DOESN'T know... but just in case, can you (anyone) help me find where to get it?
I would just go ahead and link one, but I'm not sure which one matches the Rev a silicon at this point. My fpga boards got damaged, and I myself am waiting for an evaluation board.
In those distributions, there is pnut.exe, and a few sample programs to work from, all in pasm.
Lol, plz try not to feel stupid. Yours are the first of a ton of questions we all are going to ask. No worries just onward!
I just asked Chip if he would do this, he replied he would. So I think the best thing to do is just stand by.
There are other ways to program the P2 (& appear to be cross-platform supported in source), but the above will give you a start (i.e. read the other P2 threads for info on p2asm, fastspin, etc...)
dgately
Go Team, Go!
I've gathered together some tools for programming the P2 FPGA and bundled them with a very simple IDE as "spin2gui". You can find the most recent release at:
https://github.com/totalspectrum/spin2gui/releases
This should also work on the P2-ES, but obviously we haven't had a chance to test it yet. In the meantime, it does work on P1 as well, so you can test it out there (under Commands > Configure Commands... hit either "P2 defaults" or "P1 defaults" to switch between the two processors).
The compiler included with spin2gui is called "fastspin", although someday that name should change, because it now supports not only Spin but also BASIC (see docs/basic.md) and a little bit of C.
Eric
Thanks for the link to "spin2gui". I have downloaded and installed it. I am anxiously awaiting for my P2-ES board.
Regards, zappman
I was able to override by going into the advanced settings of the FTDI driver in Device Manager and ignoring a warning about possible conflicts, but we should just be able to pick any port.
Once Spin 2 is done, something better will be the target.
For now, we just need to set a low com port.
Was typing in ">" and " " and got nothing... Finally noticed in the Taqoz thread that you have to hit the ESC key to get that prompt.
Or, from the docs, you can type “> Prop_Chk 0 0 0 0”+CR
to get the prop version.
Maybe too late, but my suggestion would be to return something, maybe an underscore or anything when CR is typed after a "> " combo.
Personally, I'm not a big fan of the "0 0 0 0". I hope somebody is really going to need that one day to make it worth while...
I know Chip said some led pins are floating and so sensitive to touch...
I'm not sure yet why P60 and P61 leds come on at boot.
Really not sure why touching P60 turns P61 led off...
Anyway pin headers might be used as an input device
Can do simple things like "60 blink" to make P60 led start blinking...
Nice when first starting out, to make sure it's alive...
There are a couple of small caps added around P60 and P61 to help with boot pathway. These shouldn't be needed on production silicon. They might have something to do with those leds coming on at boot, or it could be related to boot code checking the flash or uSD
These should flash on while the boot code is determining if booting from either.
Getting ready to connect to VGA, but one small mistake will fry my P2 (at least I think that is what would happen)...
Pros: The 5V enables addons to have their own LDOs for higher current addons, and 5V is needed for USB slaves (for example).
In the context of this Eval board, the desire was to bring out all possible signals and power rails for user experimentation. Sure, with that people should take care. I think people are used to that though?
Not just the clockset but also the DAC settings.
Fortunately, ozpropdev already figured this out and it's in cluso's VGA 1080p example.
Vsync pin also needs changing from 0 to 4
Looks like DIRA also needs 4 bits set.
What is with dacmode? doesn't seem to match documentation...
My summary in the original topic - https://forums.parallax.com/discussion/comment/1450406/#Comment_1450406
And reposted in tricks&traps - https://forums.parallax.com/discussion/comment/1452036/#Comment_1452036
EDIT: Oh, I see a typo in the BIT_DAC mode line "%TT = R1x" should be "%TT = %1x" ....
Docs say "%101xxDDDDDDDD = DAC mode, %DDDDDDDD: DAC output level"
but, I think this is wrong as it seems the "xx" bits decide output strength
EDIT: There, I've just changed the first line to start with %PPPPPPPPPPPPP
That helps, thanks.
Maybe VGA support needs a thread...
I think the VGA driver is in this mode:
But, can't decipher that...
It's a pin config without any smartpin mode. If you want to do a SETDACS instruction then that is the needed prep. Streamer output to DACs has same pin config.
I assume the proper way will be to use a COGID to fill %SSSS with.
It would be good to have Cluso's tricks and traps topic linked from your opening post - https://forums.parallax.com/discussion/169069/p2-tricks-traps-differences-between-p1-reference-material-only/p1
Thanks,
Terry
does that solve?