|
EEPROM Write-Protect/Write-Enable - The WP pin of the EEPROM is pulled up to Vcc
through a 10 K resistor asserting Write-Protect. If you initiate a Load-to-EEPROM it will fail verification.
Placing the Blue shunt onto the EEPROM Write-Enable ("WEN") jumper pins will pull the WP pin to ground,
removing the Write-Protect and effectively establishig Write-Enable.
EEPROM - 32K/64K - the PPLA kit comes with a 24LC512 EEPROM with a capacity of 64 KBytes.
Since the Propeller bootload only uses the first 32 KB that leaves 32 KB for use by you the user. Propalyzer.spin
currently uses just under 3000 longs of a possible 8000 so there's room for user added code to use the EEPROM.
Normal Channel Configuration - EEPROM in socket, PPLA firmware (propalyzer.spin) loaded to EEPROM,
Reset-Enable jumper (red shunt near reset button) in place, or not. You have the ability to monitor up to 28
channels, Propeller pins P0 through P27. The 4 lines for P28 through P31 stop at the 2x4 socket header. PPLA
pins P30/P31 are hard dedicated to the high speed serial to the PC Host. PPLA pins P28/P29 are the I2C buss
for the PPLA boot EEPROM.
Optional Channel Configuration - if you have a need to monitor the Unit Under Test's
serial (P30/P31) or I2C (P28/P29) lines there is a way.
- With power removed, carefully pull the PPLA EEPROM. Note - the 8 pin DIP socket supplied with the kit
is a machine pin socket which holds up much better to repeated extraction/insertion.
- Reset-Enable jumper on
- the four pin positions on the socket header correspond L-to-R to P31, P30, P29 and P28
- insert a short bare wire into the lowest row (nearest Prop chip) P29 and the other end into
the highest row (near stackable headers) P29 (I2c) or P31(serial)
- do the same from the lowest row P28 to highest row P28 (I2C) or P30(serial)
- add on any application boards
- Load PPLA firmware (propalyzer.spin) to RAM
- REMOVE Reset-Enable jumper. If not when you switch to Propalyzer software on PC host, the
re-opening of the comport will generate a reset and wipe the PPLA not-so-firmware!
|
