P2 Evaluation Board - Accessory Set 64006-ES

13»

Comments

  • Oh, nice, thank you Roy.

    Are there already schematics of them boards available as of you knowledge?

    Sadly I started this stupid electronics interest at a time where my eyesight already was dwindling and the hands seem not as precise as before. I have a hard time soldering thru hole components, this SMD stuff I could not even place, let alone solder.

    Currently I have my p2 sitting next to the PPDB using jumper wires, so I really like the offered boards.

    Enjoy!

    Mike
    I am just another Code Monkey.
    A determined coder can write COBOL programs in any language. -- Author unknown.
    Press any key to continue, any other key to quit

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this post are to be interpreted as described in RFC 2119.
  • Docs and schematics are in editing at the moment. I'll see about getting those schematics at least posted here today.
  • Attached here are the Schematics in pdf format, which are available ahead of launch.

    The user guide is available here, with commenting enabled. As with the P2-EVAL docs, please feel free to add notes beside anything you see needs improving, or ask questions if anything is unclear !

    https://docs.google.com/document/d/1FTGV1Mn1hwayEaKut5Ej6vmWdjirVlP9TQqyA0wRs34/edit?usp=sharing

  • Very nicely done!
    Any idea when the boards will be available for purchase?
  • Great instructions. I would recommend putting a picture of each board in the section that talks about it, you did it already for a couple of the boards.
  • Does anyone remember what thread it was where someone proposed a "standard" placement for each accessory board? I like the idea of everyone there being a standard so that all (many) of the demo programs we write will "just work" on anyone's setup without having to re-order board or rename pins in the code.
    David
    PropWare: C++ HAL (Hardware Abstraction Layer) for PropGCC; Robust build system using CMake; Integrated Simple Library, libpropeller, and libPropelleruino (Arduino port); Instructions for Eclipse and JetBrain's CLion; Example projects; Doxygen documentation
    CI Server: http://david.zemon.name:8111/?guest=1
  • DavidZemon wrote: »
    Does anyone remember what thread it was where someone proposed a "standard" placement for each accessory board? I like the idea of everyone there being a standard so that all (many) of the demo programs we write will "just work" on anyone's setup without having to re-order board or rename pins in the code.

    yes, me

    @Ahle2 brought this up and I made up some with reasoning

    http://forums.parallax.com/discussion/comment/1463262/#Comment_1463262

    Enjoy!

    Mike
    I am just another Code Monkey.
    A determined coder can write COBOL programs in any language. -- Author unknown.
    Press any key to continue, any other key to quit

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this post are to be interpreted as described in RFC 2119.
  • Having a CON defined base pin at the beginning of each "driver" is fine by me. I like the flexibility to choose where I place the accessory boards.
    "There's no huge amount of massive material
    hidden in the rings that we can't see,
    the rings are almost pure ice."
  • I think we should have both -- definitely drivers should be able to change their basepins, but if there's a convention on which boards (usually) get plugged into where then the defaults will work for most people.

    I liked @msrobots ' suggestion, with one caveat: all of the existing VGA drivers seem to use basepin=0, I think because in the FPGA the DAC is hard-coded there. So it probably makes sense to plug the AV board into the pin 0 group.
  • yeah and have that long board + vga and/or audio and/or coax left out of the P2 with all them wires between me and my keyboard.

    No all driver should support a BasePin so they are adaptable.

    My primary list was because I have a very small workspace so I wanted the most stationary wires on the top and right, having PC-USB on top and right.

    but its just a proposal for presetting a BasePin in demos.

    Enjoy!

    Mike
    I am just another Code Monkey.
    A determined coder can write COBOL programs in any language. -- Author unknown.
    Press any key to continue, any other key to quit

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this post are to be interpreted as described in RFC 2119.
  • Has anyone made a keyboard USB driver for the P2? I'd like to get my embedded basic interpreter working without a connection to a PC. I have VGA code that works with Rayman's VGA adapter board but I need a way to connect a keyboard.
  • I will admit to being wrong about the "just specify basepin" thing in one respect -- in Spin2, every blasted reference to the pins has to be split between OUTA/OUTB and DIRA/DIRB depending on whether you're in the top or bottom 32. That is a real nuisance when writing general purpose use-any-pin code. I can understand why you have to be aware that you can't do something like OUT[24..37], because of the pin 32 barrier, but with banks of 8 surely there should be a way to make common code that works on any basepin?
  • Here - https://forums.parallax.com/discussion/comment/1463841/#Comment_1463841
    I haven't got as far as trying it out myself. I wrecked my P2ES when I went to try.
    "There's no huge amount of massive material
    hidden in the rings that we can't see,
    the rings are almost pure ice."
  • The enclosure is pretty good. The only thing I have found that the engineering of the enclosure did not have the data of the accessory boards dimensions. If any body wants I can have the enclosure re re done. Give me your thoughts on this. Please give me your design ideas.
    Thanks.
    Send me a direct message please,
  • pilot0315 wrote: »
    The enclosure is pretty good. The only thing I have found that the engineering of the enclosure did not have the data of the accessory boards dimensions. If any body wants I can have the enclosure re re done. Give me your thoughts on this. Please give me your design ideas.
    Thanks.
    Send me a direct message please,

    just use a nail file and round up the corners of the accessory boards, take 2-3 min each, you do not need to remove much.

    Enjoy!

    Mike
    I am just another Code Monkey.
    A determined coder can write COBOL programs in any language. -- Author unknown.
    Press any key to continue, any other key to quit

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this post are to be interpreted as described in RFC 2119.
  • localroger wrote: »
    I will admit to being wrong about the "just specify basepin" thing in one respect -- in Spin2, every blasted reference to the pins has to be split between OUTA/OUTB and DIRA/DIRB depending on whether you're in the top or bottom 32. That is a real nuisance when writing general purpose use-any-pin code. I can understand why you have to be aware that you can't do something like OUT[24..37], because of the pin 32 barrier, but with banks of 8 surely there should be a way to make common code that works on any basepin?

    In BASIC you can use output(x) for any 0 <= x < 64, and under the hood it gets converted to OUTA or OUTB as appropriate (similarly for direction() and DIRA/B, input() and INA/B). But sometimes this can result in a fair amount of "hidden" code, so I don't know if it's appropriate for Spin.

    For single pin output Spin2 does provide dir_(), dirl_(), dirh_(), and drvnot_(). (See the "New intrinsics" section of the spin.pdf document that comes with spin2gui.
  • P2 next respin is going to provide DRVx/TESTP/etc with basepin + group of pins :smiley:
    My Prop boards: P8XBlade2, RamBlade, CpuBlade, TriBlade
    Prop OS (also see Sphinx, PropDos, PropCmd, Spinix)
    Website: www.clusos.com
    Prop Tools (Index) , Emulators (Index) , ZiCog (Z80)
  • This is simple compared to the STM chip where there are only 16 pins per group and multiple groups that are memory mapped and require several instructions just to set a pin.

    Mike
  • I didn't expect the HDMI cable from my monitor to be providing power...
    But, when connected to my Eval board (with nothing else connected, except my HyperRam board) an WS2812 LED on HyperRam board lit up.


    Seems I have 2.2 on the 5V supply, 2.5 V on 3.3 V supply and 3.2 V on either the pin labelled 1 or the one labelled 2 (seems to change each time).

    So, it's providing some power, but not enough to power on the board...
    Interestingly, I also see +5V on SCL and SDA holes but zero on the 5V hole.

    Prop Info and Apps: http://www.rayslogic.com/
  • roglohrogloh Posts: 1,054
    edited 2019-05-11 - 23:00:55
    Current Mirror Logic (CML) receivers used by HDMI need a 50 ohm pullup resistor to VCC on each differential pair input for typical termination. Seems like that is what would be feeding back into your Eval board and through P2 protection diodes etc.

    The 5V on SCL/SDA is strange. I would expect the monitor would(should?) use the 5V provided to it over HDMI for the i2c pullups but maybe it doesn't need to and simply uses some internal 5V instead.
Sign In or Register to comment.