A few ramdom notes that may interest some.
Target Clock Speed vrs IDE Performance
I had been working with the 18F1330 at 32MHz. Today I wrote code for the Junebug 18F1320 8 MHz onboard target.
The IDE seemed sluggish.
The debugger preformance we see is the result of the interaction of MPLAB with Junebug; and Junebug with the debug monitor resident on the target chip.
When you slow the target from 32 to 8 MHz you also slow the target's debug monitor which handles the interface between itself and Junebug. Overall IDE preformance/speed suffers.
By the same token when you switch from a 8 MHz target to a 32 MHz target the IDE seems to fly.
Programming I2C EEPROMS with Junebug
When working on the BTC audio playback project I needed to program the speach bits into a 24LC512 I2C serial EEPROM. It was easy to do using Pickit2 V2.40 software and the Junebug. I made a simple adaptor board that plugged into the socket next to the Junebug processor chip. Ask if you want details on how to make one.
Target Clock Speed vrs IDE Performance
I had been working with the 18F1330 at 32MHz. Today I wrote code for the Junebug 18F1320 8 MHz onboard target.
The IDE seemed sluggish.
The debugger preformance we see is the result of the interaction of MPLAB with Junebug; and Junebug with the debug monitor resident on the target chip.
When you slow the target from 32 to 8 MHz you also slow the target's debug monitor which handles the interface between itself and Junebug. Overall IDE preformance/speed suffers.
By the same token when you switch from a 8 MHz target to a 32 MHz target the IDE seems to fly.
Programming I2C EEPROMS with Junebug
When working on the BTC audio playback project I needed to program the speach bits into a 24LC512 I2C serial EEPROM. It was easy to do using Pickit2 V2.40 software and the Junebug. I made a simple adaptor board that plugged into the socket next to the Junebug processor chip. Ask if you want details on how to make one.