Shop OBEX P1 Docs P2 Docs Learn Events
Issues with 2 new Propeller 1-2-3 A9 Boards - Page 2 — Parallax Forums

Issues with 2 new Propeller 1-2-3 A9 Boards

2»

Comments

  • rayman, I have overwritten the P1 with a copy of PX.spin that I found in an A7 post. I,ll try the copy that chip just posted even though I think they are the same version.

    Chip, will do. Thanks
  • RaymanRayman Posts: 14,641
    They probably are the same since I don't remember ever programming mine...
  • RaymanRayman Posts: 14,641
    edited 2017-01-30 19:36
    If you're able to program the P1 with PX, I'd recommend trying that top.rbf file for P1V.
    Then, see if it identifies with the Prop Tool.

    That should eliminate the possibility that FTDI driver somehow doesn't like Chip's new serial interface mode for P2V...
    Nobody else seems to have had an issue with it, but you never know...
  • ozpropdevozpropdev Posts: 2,792
    edited 2017-01-31 00:17
    Here's another test image you can try for the A9 board.
    http://forums.parallax.com/discussion/162984/p123-a9-board-test-image

    Its a P1V that tests all the leds, headers, DAC's and buttons .
    It also outputs test text @ 116200 baud on the serial port.

    Edit: Propeller Tool F7 "Identify hardware" should detect "Propeller chip version 200 found on COMx."
  • cgraceycgracey Posts: 14,152
    Chuck and I talked and it turns out one of his boards has what looks like a power supply problem and the other is working, after we reprogrammed the on-board Prop1. We're going to send him a replacement for his bad one. Meanwhile, he's got one that works and has v14 loaded onto it.
  • Nice!
  • RaymanRayman Posts: 14,641
    Any idea why my two new boards wouldn't recognize on the first couple tries?

    Something about the new serial interface?
  • cgraceycgracey Posts: 14,152
    Rayman wrote: »
    Any idea why my two new boards wouldn't recognize on the first couple tries?

    Something about the new serial interface?

    I don't know.
  • RaymanRayman Posts: 14,641
    Well, the good news is that it worked every time after that.
    Don't think I've seen that kind of behavior before though.
    Still, something to watch out for...
Sign In or Register to comment.