Sudden Change in Yocto Behavior During Firmware Debugging
Posted: Sep 30th, '17, 21:19
Hello kind people!
I've been working on code to correct the "pushing multiple step buttons during edit mode does weird things" bug, and I think I've fixed it. However, I've run into a bit of a snag. This morning when I turned the Yocto on via the standard 15VAC power inlet to triple-check my work, I noticed three problems emerge:
I have a few spare ATMEGA1284 and ATMEGA1284P chips on order already to see if swapping them helps.
Lastly, is anyone using an ATMEGA1284 as their Yocto MCU, or does everyone have the ATMEGA1284P? The Yocto install guide and kit BOM shows the P version of the chip, but my unit is the non-P version. Maybe this has something to due with this problem? The datasheets of these two parts are very similar, but the P version looks like it can be run in a lower-power state by shutting down some parts of itself.
I've been working on code to correct the "pushing multiple step buttons during edit mode does weird things" bug, and I think I've fixed it. However, I've run into a bit of a snag. This morning when I turned the Yocto on via the standard 15VAC power inlet to triple-check my work, I noticed three problems emerge:
- All of my programmed patterns were overwritten with a hit on every step for every instrument
- Changed to patterns were not being saved
- The Yocto was not responding to the tempo encoder or to external tempo sync (STOP/START via MIDI does still work)
I have a few spare ATMEGA1284 and ATMEGA1284P chips on order already to see if swapping them helps.
Lastly, is anyone using an ATMEGA1284 as their Yocto MCU, or does everyone have the ATMEGA1284P? The Yocto install guide and kit BOM shows the P version of the chip, but my unit is the non-P version. Maybe this has something to due with this problem? The datasheets of these two parts are very similar, but the P version looks like it can be run in a lower-power state by shutting down some parts of itself.