PNut_v33?

RossH · 2019-11-02 23:09

I have PNut_v32i.exe, which is the latest version I can find. But this version cannot load my P2 EVAL (RevB) board. Which is a bit odd, because p2load and payload both do so quite happily.

Is there a PNut_v33 somewhere?

Thanks

Ross.

ozpropdev · 2019-11-02 23:13

You need 33k for RevB

RossH · 2019-11-02 23:14

Thanks!

Parallax needs to update propeller.parallax.com!

Ross.

ozpropdev · 2019-11-02 23:24

To be honest I can't remember exactly where I even got the latest Pnut from.
It might have been from FPGA testing...

evanh · 2019-11-03 00:47

Yep, it comes with the FPGA files - the v33 files were only in a google drive link from https://forums.parallax.com/discussion/169695/new-fpga-files-for-next-silicon-version-5th-final-release-contains-new-rom/p1

RossH · 2019-11-03 01:00

evanh wrote: »

Yep, it comes with the FPGA files - the v33 files were only in a google drive link from https://forums.parallax.com/discussion/169695/new-fpga-files-for-next-silicon-version-5th-final-release-contains-new-rom/p1

Thanks.

I really hate the fact that it is so hard to find the latest, definitive information about the Propeller 2. It makes everything three times harder than it should be

cgracey · 2019-11-03 01:04

RossH wrote: »

evanh wrote: »

Yep, it comes with the FPGA files - the v33 files were only in a google drive link from https://forums.parallax.com/discussion/169695/new-fpga-files-for-next-silicon-version-5th-final-release-contains-new-rom/p1

Thanks.

I really hate the fact that it is so hard to find the latest, definitive information about the Propeller 2. It makes everything three times harder than it should be

Sorry. As soon as PNut.exe comes out of flux, I'll make a cohesive place for everything. Maybe I should just post a link to the v33 PNut in the "New Silicon" thread that also has links to the doc's.

RossH · 2019-11-03 01:09

cgracey wrote: »

RossH wrote: »

evanh wrote: »

Yep, it comes with the FPGA files - the v33 files were only in a google drive link from https://forums.parallax.com/discussion/169695/new-fpga-files-for-next-silicon-version-5th-final-release-contains-new-rom/p1

Thanks.

I really hate the fact that it is so hard to find the latest, definitive information about the Propeller 2. It makes everything three times harder than it should be

Sorry. As soon as PNut.exe comes out of flux, I'll make a cohesive place for everything. Maybe I should just post a link to the v33 PNut in the "New Silicon" thread that also has links to the doc's.

Yes, good idea. Also, you should put a link on propeller.parallax.com, which currently has PNut_v32i.exe only.

Ross.

cgracey · 2019-11-03 01:16

RossH wrote: »

cgracey wrote: »

RossH wrote: »

evanh wrote: »

Yep, it comes with the FPGA files - the v33 files were only in a google drive link from https://forums.parallax.com/discussion/169695/new-fpga-files-for-next-silicon-version-5th-final-release-contains-new-rom/p1

Thanks.

I really hate the fact that it is so hard to find the latest, definitive information about the Propeller 2. It makes everything three times harder than it should be

Sorry. As soon as PNut.exe comes out of flux, I'll make a cohesive place for everything. Maybe I should just post a link to the v33 PNut in the "New Silicon" thread that also has links to the doc's.

Yes, good idea. Also, you should put a link on propeller.parallax.com, which currently has PNut_v32i.exe only.

Ross.

Agreed.

Seairth · 2019-11-17 03:20

I just got caught by this early today. propeller.parallax.com still needs to be updated as Ross said above.

VonSzarvas · 2019-11-17 08:52

@cgracey
For the docs update I have a question...

Is PNUT 33k backward compatible for RevA chips?

ie. should we list 32i for RevA (ES silicon 1)
and 33k for RevG (ES silicon 2)

or just 33k for both silicon.

Edit: All ok. Docs and site updates in progress with the team.

Publison · 2019-11-17 09:17

I have been using 33k for my Rev A ES. Works fine.

ozpropdev · 2019-11-17 09:47

You should use 32i with RevA.
If you use 33k for RevA it won't error on the RevB PTRX[index] changes.

Publison · 2019-11-17 09:48

Good to know. Have not gotten to that point yet.

pilot0315 · 2019-11-17 20:18

@cgracey

Yeah please put up a link. I got caught up with not knowing about Pnut 33 and the latest Flexgui 4.0.3. Now all is working.
BTW I like the new board. A lot cleaner. I now get to hang my Rev A on the wall.

VonSzarvas · 2019-11-17 20:58

Thanks for the info. I've already added the detail to the P2 Eval docs. Links at product pages and propeller.parallax.com will be updated soon.

cgracey · 2019-11-17 22:10

The latest is v33L. I posted a link to it the other day, somewhere. It is like v33k, except it allows the serial ports to go above COM9, up to COM99.

Let me find it....

cgracey · 2019-11-17 22:13

Here is v33L. This (or v33k) is needed for Rev B silicon:

https://drive.google.com/file/d/1W4_O8garuXfxYGz80bLm81kBuby5WeI9/view?usp=sharing

VonSzarvas · 2019-11-18 05:26

Thank you Chip. 33L is heading to propeller.parallax.com today!

Jeff Martin · 2019-11-18 19:43

I updated the propeller repo (so thus the propeller.parallax.com site) to include the v33k and v33L files.

Publison · 2019-11-18 20:15

cgracey wrote: »

Here is v33L. This (or v33k) is needed for Rev B silicon:

https://drive.google.com/file/d/1W4_O8garuXfxYGz80bLm81kBuby5WeI9/view?usp=sharing

I guess the question is if 33L will work for RevA or do we use 33i forever on that platform?

cgracey · 2019-11-18 20:17

Publison wrote: »

cgracey wrote: »

Here is v33L. This (or v33k) is needed for Rev B silicon:

https://drive.google.com/file/d/1W4_O8garuXfxYGz80bLm81kBuby5WeI9/view?usp=sharing

I guess the question is if 33L will work for RevA or do we use 33i forever on that platform?

Yes, for rev A silicon, you must stick with v33i.

evanh · 2019-11-19 03:21

v32i

cgracey · 2019-11-19 04:20

evanh wrote: »

v32i

Whoops. It would be v32i.

ozpropdev · 2019-11-19 05:30

In V33k I get

a = %1011 >< 5
TYPE: 4B   VALUE: 0000001A   NAME: A

and in V33L I get

a = %1011 rev 5
TYPE: 40   VALUE: 00000034   NAME: A
..and
a = %1011 rev 4
TYPE: 40   VALUE: 0000001A   NAME: A

cgracey · 2019-11-19 05:42

ozpropdev wrote: »

In V33k I get

a = %1011 >< 5
TYPE: 4B   VALUE: 0000001A   NAME: A

and in V33L I get

a = %1011 rev 5
TYPE: 40   VALUE: 00000034   NAME: A
..and
a = %1011 rev 4
TYPE: 40   VALUE: 0000001A   NAME: A

I made the REV operator use MSB# instead of the number of bits. In P2, the PASM instructions all use MSB#, so I thought the operators should use MSB#.

evanh · 2019-11-19 06:48

Not sure I like that one, Chip. It doesn't translate to an instruction at all and the first thing we did with the HUBSET components like that was translate them all back to representative quantities. - https://forums.parallax.com/discussion/comment/1452025/#Comment_1452025

cgracey · 2019-11-19 06:52

evanh wrote: »

Not sure I like that one, Chip. It doesn't translate to an instruction at all and the first thing we did with the HUBSET components like that was translate them all back to representative quantities. - https://forums.parallax.com/discussion/comment/1452025/#Comment_1452025

There seems to be no perfect solution, but where 32 bits are involved, it's nice to fit the range to 5 bits.

ozpropdev · 2019-11-19 06:58

So
a = %1011 rev 5
should then return a value of $d000_0000?

evanh · 2019-11-19 07:10

Question: How to do a RES like declaration for hubram within an ORGH block?

PS: I can just hard code the addresses if there isn't a solution.

cgracey · 2019-11-19 09:59

ozpropdev wrote: »

So
a = %1011 rev 5
should then return a value of $d000_0000?

(%1011 rev 5) returns $00000034.

Think of bit 5 being the MSB, then reverse it:

%001011 --> %110100

PNut_v33?

Comments