Prop-to-Prop programming

Bobb Fwed

I have seen the object that allows you to program a propeller with another propeller. What is it called? Are there any requirements for it (in the hardware) like 64K EEPROM or pull-up resistors on any of the three (RES/TX/RX) lines? Any precautions I should know before I use it?

The important thing is: what is it called in the OBEX? Linkme please?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
April, 2008: when I discovered the answers to all my micro-computational-botherations!

Some of my objects:
MCP3X0X ADC Driver - Programmable Schmitt inputs, frequency reading, and more!
Simple Propeller-based Database - Making life easier and more readable for all your EEPROM storage needs.
String Manipulation Library - Don't allow strings to be the bane of the Propeller, bend them to your will!
Fast Inter-Propeller Comm - Fast communication between two propellers (1.37MB/s @100MHz)!

Tubular

Chip's Prop Loader
obex.parallax.com/objects/61/

I don't know why searching for "loader" doesn't find it. Perhaps because of the capital L

kuroneko

Bobb Fwed said...
I have seen the object that allows you to program a propeller with another propeller. What is it called? Are there any requirements for it (in the hardware) like 64K EEPROM or pull-up resistors on any of the three (RES/TX/RX) lines? Any precautions I should know before I use it?

FWIW, it's also part of the Propeller Tool library (called PropellerLoader.spin). No special requirements, although the doc suggests to pull the slave RES to ground until showtime. But that's not really necessary if you're careful.

Be aware, the upload bit rate is about clkfreq/4400 so if you have lots of stuff to transfer (16KB in ~7sec @80MHz) then you might want to think of something clever [noparse]:)[/noparse]

jagrifen

I have been playing around with this Prop Loader and have been successful in getting the two chips to talk to eachother. Is there a way to load the program to the EEPROM of the client propeller from the first propeller?


Never mind. I figured it out. I changed the Command variable in the PropellerLoader example to "loader#ProgramRun" and it works like I wanted it to now.

Post Edited (jagrifen) : 6/26/2010 12:06:47 AM GMT