Propeller 2 Cheat Sheet (Google Doc)

mindrobots

I'm not sure if this is of use to anyone but I find it easier (sometimes) to try and visualize the architecture as I sit and play computer.

I started out with a paper version which moved to a Google Spreadsheet (as Corporate America knows, if you can't capture it in a Spreadsheet, it ain't worth capturing!!)

Read-only web version of Cheatsheet

I'm still dredging the threads to find the gems buried in the forum. I see the sections growing as I stumble upon tips/tricks/hints/etc.

Any feedback would be appreciated. Let me know if it's not worth continuing also.

78rpm

mindrobots, I like that, nice and colourful.

When you said a spreadsheet I thought you meant simulated instructions where you type two values in a field, for say an add instruction, then get the result in cell below. And a different rsult for the ADDS instruction depending on the operands.

I say go with it. It may not be everyone's cup of tea, but to some it will be of help. Certainly as a "cheat sheet" it can be good. Is it compatible with wallpaper print programs, or do I need to go in search of blu-tac?

potatohead

This is useful.

ctwardell

Thanks mindrobots!

This is enough to get me to start poking around with my nano.

C.W.

User Name

Definitely useful! Thanks for searching threads and consolidating info for lazy bones like me.

Just as soon as I get a little P1 project wrapped up, I will dust off my Terasic board and put it to good use. Wish I could play with the color space converter for PSK. Alas, I only have a Nano.

mindrobots

Thanks, everybody!

User Name, as they always say, "two COGs is better than none!!" (they have notoriously bad grammar)

Drop me a note if anyone wants to contribute...."collaboration means never having to say you're sorry"

evanh

Mindrobots,
HubRAM does start at address $0 even if that space is often avoided. It's only the HubExec code space that must start from $400 and up.

Cluso99

mindrobots,
Looking Good!

mindrobots

Evanh, good point about HUB RAM, I knew that but I usually ignore that space. I'll fix up! How lazy we get when there's so much memory!!

evanh

Peter Jakacki

Nice job, how does that come across as the more easily accessible "published" HTML version I asked, so I tried <HERE>. That's only temporary as I leave that for you to publish and link.

Do you mind if I include a link to your document from the assembly instruction set manual?

mindrobots

Thanks, it looks nice as HTML! I hadn't really looked at much more than draft mode as I typed stuff in.

Please, feel free to link to it. I think the docs complement each other well!

The visual layout of the processor helps me think. I can see using this as a design and planning aid template.

Peter Jakacki

Cool, but if you go to File...Publish to the Web.. etc in the Google Docs menu and give us the link then that html copy will always be refreshed from your master document automatically. The other plus is that it's read-only without any Google Doc menus too.

mindrobots

Ok, i'll put the html link out here in the morning. It's bedtime now.

mindrobots

Peter, here's a link to the web version of the cheatsheet: https://docs.google.com/spreadsheets/d/1wQ6gwGFXRr22bM7S5PZaukQL9LrnEU5oqh3p8ZntNO8/pubhtml

mindrobots

I've added a new tab - "Instruction Examples" and I'm starting to collect code snippets on how to use some of the instructions and various notes and gotcha's that are scattered through the forum threads.

This one is a GREAT PLACE FOR CONTRIBUTIONS!!! As you come up with any tricks or traps, toss a few lines of code into the spreadsheet to help out the next poor soul that tries something new.

I've also linked to Peter's document from here for more complete documentation of the instruction set.

Feedback is always welcomed and encouraged!!