Shop OBEX P1 Docs P2 Docs Learn Events
Where is Pnut v34n and how do I get it? — Parallax Forums

Where is Pnut v34n and how do I get it?

JonTitusJonTitus Posts: 193
in Propeller 2
I have found example software for the Propeller-2 posted on this forum with the note "PNut v34n". The Propeller-2 Developer Site shows Pnut v33L. Where do I find the v34n version? Have I missed something obvious? I have a Propeller-2 chip on a Parallax P2 EVAL Board and have used FlexGUI to create and run programs. I would like the have the latest release of Pnut, too. Thanks. --Jon

Comments

  • whickerwhicker Posts: 749
    So propeller.parallax.com needs some updating. Scroll down in this same Propeller 2 forum area and you'll find it.
  • Cluso99Cluso99 Posts: 18,069
    You need the latest v34s here
    forums.parallax.com/discussion/171196/pnut-spin2-latest-version-v34s/p1
  • evanhevanh Posts: 15,916
    edited 2020-05-31 01:47
    v34L is the last release without the hubexec regression in pure Pasm2. Chip has been preoccupied with Spin2 development.
    zip
    zip
    PNut_v34L.zip
    281K
  • Cluso99Cluso99 Posts: 18,069
    edited 2020-05-30 20:26
    evanh wrote: »
    v34L is the last release without the hubexec regression in pure Pasm2. Chip has been preoccupied with Spin2 development.
    What do you mean “hubexec regression” please?
    I can still use pnut v34s to compile pasm only programs with or without hubexec.
    Am I missing something?
  • evanhevanh Posts: 15,916
    Symbol addresses for long branching (20-bit immediate) from hubexec to hubexec is messed up.

  • evanhevanh Posts: 15,916
    edited 2020-05-30 23:09
    Looking at Pnut's lst file, the twelve high bits of the symbol addresses much have meaning. It's notable that all the hub addresses have $fff at the top. Eg: first two here are in cogRAM, the second two are in hubRAM 
    ...
TYPE: DAT_LONG        VALUE: 00800020          NAME: LOCTEST1
TYPE: DAT_LONG        VALUE: 00900024          NAME: _MAIN
TYPE: DAT_LONG        VALUE: FFF00110          NAME: LOCTEST2
TYPE: DAT_BYTE        VALUE: FFF00450          NAME: LOCTESTHUB
...

    EDIT: Seems to be the same for all Pnut versions. Maybe something in the handling of these has changed. :shrug:

  • evanhevanh Posts: 15,916
    edited 2020-05-30 23:40
    Not surprisingly, it affects LOCs to hub symbols when in hubexec as well. There is a +748 byte offset added to the target symbol address.

    Doesn't affect numerical immediate addresses. Only referencing symbols in hubRAM and only when referenced from hubexec and only for 20-bit immediate encodings. So CALL #, JMP #, and LOC #.

  • Cluso99Cluso99 Posts: 18,069
    edited 2020-05-31 00:19
    Thanks Evan. I had forgotten about those and they are likely to cause problems because my calls/jumps are likely to be large and cause the 20bit addressing to be used. I've had all sorts of issues in the past that i've never been able to pin down, what with all the other addressing problems I've had.
    Anyway, since I cannot live with the spin2 problems in pnut, I'm back to total pasm and fastspin is much better there because of conditional compilation and include files.
  • evanhevanh Posts: 15,916
    I've attached the v34L zip file to my first post.
Sign In or Register to comment.