The new release of NX is absolutely great. It features many subtle design changes the experienced user would appreciate.
http://www.acuityinc.com
Tuesday, July 27, 2010
Monday, March 17, 2008
Getting Started
This first post is a sort of catch-up to highlight some of the many Propeller related community developments that have occured recently. As time progresses from here, the idea is to just post up new developments, one post at a time blog style for a quick check-in to see what's new, then jump off to follow the relevant link if it's of interest.
This blog started as a proof of concept kind of "what if?" response to the "Propeller Magazine" thread discussion in progress here. Please post comments, flames, whatever on that thread please.
This week, DeSilva takes a step backward and forward at the same time, with his dual announcments of a break from answering questions, and his work on a new Propeller book project.
From time to time, by popular demand, the Indexed Propeller Manual link has been reposted. Read it here.
FPGA degugger enabled version of Propeller II? The suggestion came up! Join the discussion here.
Parallax has announced another design contest! This time, it's for the uOLED-96-Prop device. The objective is to get images stored on a micro-SD card into the device for display.
PropGFX lite continues to see aggressive development. For those who have not kept up with this design, it's essentially a GPU that is powered by a Propeller chip. The news this week is about the soon to be released command reference for the onboard GFX tool kit, shipped with the device on EEPROM.
Jasper_M contributed a HUB memory manager.
Lots of incremental news on the LMM (large memory model) assemblers, C Compiler, and assemblers. Here's a grab bag of links, along with brief summary:
That's it for now! From here on out, it's individual posts, each highlighting a development of note.
This blog started as a proof of concept kind of "what if?" response to the "Propeller Magazine" thread discussion in progress here. Please post comments, flames, whatever on that thread please.
Propeller news can be sent to opengeek@gmail.com.
This week, DeSilva takes a step backward and forward at the same time, with his dual announcments of a break from answering questions, and his work on a new Propeller book project.
From time to time, by popular demand, the Indexed Propeller Manual link has been reposted. Read it here.
FPGA degugger enabled version of Propeller II? The suggestion came up! Join the discussion here.
Parallax has announced another design contest! This time, it's for the uOLED-96-Prop device. The objective is to get images stored on a micro-SD card into the device for display.
PropGFX lite continues to see aggressive development. For those who have not kept up with this design, it's essentially a GPU that is powered by a Propeller chip. The news this week is about the soon to be released command reference for the onboard GFX tool kit, shipped with the device on EEPROM.
Jasper_M contributed a HUB memory manager.
Lots of incremental news on the LMM (large memory model) assemblers, C Compiler, and assemblers. Here's a grab bag of links, along with brief summary:
- Ale has progress on his LMM assembler. He's working on some formatting issues at present.
- There is a JVM (Java Virtual Machine) in progress. The current focus is completing the core elements necessary to begin writing and testing small programs.
- ImageCraft continues toward the LMM C compiler beta. It appears they have their assembly syntax worked out now. Here is a blurb from the dev team:
1. Assembler reads the assembly file(.s) and generates the ELF object file(.o).
2. Complete Instruction set as per propellar manual except ORG and FIT.
3. ICC Directives - .area, .byte, .word, .long, .align, .blkb, .blkw
4. Sections:
.area text - text section where the code resides
.area data - data section
.area lit - literal tables
.area bss - uninitialized data section
5. Relocatable sections
user defined areas
****
The ELF object file contains debug information, to be used later by a debugger. As you can see, the directives and sections are needed by the C compiler to ... support C. I hope this addresses the question why we can't just use PASM syntax 100%
2. Complete Instruction set as per propellar manual except ORG and FIT.
3. ICC Directives - .area, .byte, .word, .long, .align, .blkb, .blkw
4. Sections:
.area text - text section where the code resides
.area data - data section
.area lit - literal tables
.area bss - uninitialized data section
5. Relocatable sections
user defined areas
****
The ELF object file contains debug information, to be used later by a debugger. As you can see, the directives and sections are needed by the C compiler to ... support C. I hope this addresses the question why we can't just use PASM syntax 100%
That's it for now! From here on out, it's individual posts, each highlighting a development of note.
Subscribe to:
Posts (Atom)