OBEX code samples
info
Posts: 31
What do you use to open the files in OBEX? Notepad, Wordpad or browser displays continuous block of text impossible to read. Somehow the code sample formatting got lost on OBEX.
Comments
Propeller IDE software:
http://www.parallax.com/downloads/propeller-tool-software
If you are having a problem where the file in the OBEX shows up as a .SPIN file, select all, then paste it in the Propeller Tool that Beau linked to.
Somehow the OBEX got broken where it just displays a SPIN file instead of downloading it. ZIP file should download correctly.
Forgot, that works too!
Sorry for being pest, but I can not make it happen. When I click on file it opens in browser as block of text. When I right-click, it wants to save as html (not spin). When I open the saved file in the Propeler Tool, it is the same block of text on light yellow background.
So much for learning programming. No go. I wonder why do we jump on new "improved" things like html 5 and other programs that just crash in older browser and display differently in every brand or make of browser. What can html 5 do better for a website than html 3 or 4? OK, that's kinda unrelated to my problem, I'm just venting frustration, but I'm on world's biggest manufacturer of SBC website and I can't open simple text file. That's not good. I really wanted to use the Propeler chip in a design for simple reason. It is programmable in 3 languages, Assembly, Spin and FemtoBasic. That's hard to beat. (If I just could read the sample programs and learn something).
right click on the SPIN file in the OBEX and "save link as", select the destination and it will save it as a SPIN file.
I will put another log on the fire for Parallax to fix that. Stick with us, we will get it done.
Then it will save the html file as .spin or .zip that can be used.
.
Now I just need to delete all the code samples I saved and download them using the 3-step process. The funny thing is that all this code is already in the Propeler's ROM, but there are no hooks to use it. If I remember correctly, DOS had the feature. BIOS calls that were fully documented, so the programmer was able to optimize program to fit on 512 byte floppy disk sector and use BIOS calls to make nearly impossible and unbelievable tricks. Today even reading and writing the i2c eeprom requires lot of code. That's where the OBEX samples are real life saver.