Shop Learn
PNut/Spin2 Latest Version (v35i - DEBUG-Display-Only Mode via Command Line) - Page 39 — Parallax Forums

PNut/Spin2 Latest Version (v35i - DEBUG-Display-Only Mode via Command Line)

1333435363739»

Comments

  • Wuerfel_21Wuerfel_21 Posts: 1,449
    edited 2021-02-18 16:54

    Using PropTool 2.5, I can't seem to compile code that contains any OBJs with debugging enabled. (Yes, I do have an _CLKFREQ set)


    Highly helpful message.

  • cgraceycgracey Posts: 13,406
    edited 2021-02-18 19:59

    Wuerfel, I think Jeff was making DEBUG the default situation, but there were some ramifications he didn't consider.

    For now, try putting a '_clkfreq = 10_000_000" in every object to satisfy the 10 MHz requirement. That'll probably solve the problem, but we will fix the tool.

  • JonnyMacJonnyMac Posts: 7,419
    edited 2021-02-18 22:14

    Just updated to 2.5.0. Debug windows pop up then immediately disappear. I am running Chip's examples, not my own code.

  • AribaAriba Posts: 2,440

    @JonnyMac said:
    Just updated to 2.5.0. Debug windows pop up then immediately disappear. I am running Chip's examples, not my own code.

    I think they don't disappear, but go into background. If you make the PropTool Window smalller, you see the windows. For sure that's nor how it should work.

    Andy

  • JonnyMacJonnyMac Posts: 7,419

    Thanks, Andy, that was it. I tried Alt-Tab to find them earlier, but they're actually part of the main app so that wasn't helpful.

  • cgraceycgracey Posts: 13,406

    I talked to Jeff this evening and he found a few things which he fixed, but there is still something left to solve. He'll be back on it tomorrow.

  • @JonnyMac - this started happening to me too, late in development (like the last few hours before release). I didn't know what caused it but now I think I do, so I'll try to resolve that.

  • Jeff MartinJeff Martin Posts: 662
    edited 2021-02-20 03:02

    @Wuerfel_21 @JonnyMac @Ariba - I've fixed both of these issues in the v2.5.1 release.

  • cgraceycgracey Posts: 13,406

    I just posted a new v35i which has a command-line DEBUG-only mode that is useful for presenting DEBUG data and displays from applications that have been programmed into the flash. Your application could spit out DEBUG commands from a non-critical cog and if you ever wanted to tune in and see what it's doing, just do this command line:

    PNut_v35i -debug {CommPort if not 1} {BaudRate if not 2_000_000}

  • I frequently get a "Communications stalled due to system problem" after an F7 or F11 in the new Prop Tool 2.5.1.

    Not always, but quite a bit. I will get the attached messagebox twice after a compile & download with F11.

    The code still seems to download and run.

    I went back to the 1.3.2 version of the Prop Tool with the same hardware and I get no errors.

    I have repeated this on the following...

    • 32812 Proto Board Rev A
    • 32810 Proto Board Rev C
    • 32123 Flip Rev A
    • Propeller Pro Dev Board Rev A

    I've done it with a few different USB cables and both direct from my laptop's USB ports as well as through a 7 port hub. All with the same results.

    I'm running Windows 10 Pro 64 bit with 64GB Ram.

  • Thanks @JimFouch2 . I checked with Jeff, and he's currently working on a fix for this situation. Expect a new release soon!

  • JonnyMacJonnyMac Posts: 7,419
    edited 2021-03-05 16:48

    [deleted] See Jeff's post (below)

  • @JimFouch2 said:
    I frequently get a "Communications stalled due to system problem" after an F7 or F11 in the new Prop Tool 2.5.1.

    Thanks! We've had a few reports of this and even more this week. Yesterday I determined the cause of the problem and am working on the fix today. There's a logged issue for it here.

    I can confirm that in most cases the error condition is bogus and the Propeller was actually programmed successfully. You can see more detail in the issue above, but in summary, the Propeller Tool is sending the proper payload but is "timing out" too early (after end of payload but before Propeller can respond).

Sign In or Register to comment.