I had problems trying to read the Google Docs Instruction Set even when printing off on 24"x36" pages.
I have taken the XLS files to a more readable letter size for my desk reference.
Good idea. And here's my version. I think the bit encoding is not so important except for compiler developers. For me as beginner the verbose description is more helpful.
I just group the columns after the description and then collapse that to hide it. If I print the result out then there are 8 pages.
Here's a screenshot.
It will report 0 for no compiler error or 1 for compiler error.
You can add -r to also download and run. Download won't happen unless compilation was successful.
Chip: Is it possible to change the errorlevel value to the offending line # in the code -- that would make bug hunting with external editors a bit easier.
However, I think one'd probably want the file name the error is in, too.
Agreed, but PNut is Chip's workspace, and never really intended for big public use -- so I will take little changes if I can get them. Since many projects are multi-file, your suggestion makes sense. Would also love to have Ctrl-Z working for those, "I didn't mean to do that!" pastes.
Comments
https://drive.google.com/file/d/1W3sVAx9TeI9mCRsaywBB7_SIYmX8zYpU/view?usp=sharing
To just compile your PASM code:
To also download your PASM code:
To compile from a batch file, make a batch file like this:
It will report 0 for no compiler error or 1 for compiler error.
You can add -r to also download and run. Download won't happen unless compilation was successful.
Good idea. And here's my version. I think the bit encoding is not so important except for compiler developers. For me as beginner the verbose description is more helpful.
Here's a screenshot.
Chip: Is it possible to change the errorlevel value to the offending line # in the code -- that would make bug hunting with external editors a bit easier.
However, I think one'd probably want the file name the error is in, too.
Especially, if could be in format similar to FastSpin, OpenSpin, etc...
Or, maybe we need OpenSpin2...
And more - https://forums.parallax.com/discussion/comment/1494165/#Comment_1494165
And that came from the new overview of the custom pad ring schematic - https://forums.parallax.com/discussion/comment/1494131/#Comment_1494131
https://github.com/parallaxinc/propeller/tree/master/libraries
https://drive.google.com/file/d/1iTA4dwbntgaUVnpt0-9pDcFCVSsvCUnU/view?usp=sharing
https://drive.google.com/file/d/1iTA4dwbntgaUVnpt0-9pDcFCVSsvCUnU/view
P2 DVI/VGA driver by Roger Loh
forums.parallax.com/discussion/170676/p2-dvi-vga-driver/p1
KiCad v5 for P2X8C4M64P - schematic symbols and footprint etc
forums.parallax.com/discussion/172007/kicad-p2-stuff#latest
P2 Fonts
https://forums.parallax.com/discussion/167894/a-rom-font-compatibile-8x8-font
http://forums.parallax.com/discussion/comment/1503884/#Comment_1503884
Added 11 Nov 2020:
Chip finalising the SincX smartpin modes, Jan 2019 - https://forums.parallax.com/discussion/comment/1459931/#Comment_1459931
26 Nov 2020:
HubRAM read latency - https://forums.parallax.com/discussion/comment/1511074/#Comment_1511074