👋👋🌈🎆🥳🎉 Welcome to Bloom Discussions!👋👋🌈🎆🥳🎉

[navnavnav]

👋 Welcome!

Hi all,

I've setup GitHub Discussions for Bloom users to ask questions and share anything Bloom related.
Feel free to start a new discussion.

Thanks,
Nav

[cbwolfe94]

I've downloaded all of the necessary software. Verified my connection to my atmega328p by flashing a program to it using the Atmel ICE using the SPI interface. Not sure what I am doing wrong.

[cbwolfe94]

Working. Thanks!

[cbwolfe94]

Power cycle was indeed necessary.

[navnavnav]

Just one more thing to note with debugging via debugWire: If you're using AVRDUDE to program the target, you may run into issues when the DWEN fuse is set, where AVRDUDE will report errors such as "Unexpected response" or "Short read, read only 0 out of X bytes". And it will leave the Atmel-ICE in a bad state, where it will need to be re-enumerated before you can use it again. This is due to a timeout bug in AVRDUDE, explained here: avrdudes/avrdude#900 The PR for this fix is still pending approval.

If you do run into that issue, you can use the disableDebugWirePreDisconnect target config param in Bloom, to have Bloom disable the DWEN fuse just before disconnecting with the target. But the down-side to this is that you'll have to cycle the target power every time you start/stop Bloom, or for every debug session, if releasePostDebugSession is enabled. So it may be a good idea to disable releasePostDebugSession (debug tool config param - see https://bloom.oscillate.io/docs/configuration#debug-tool-config-param-releasePostDebugSession), so that Bloom doesn't disconnect from the target at the end of each debug session.

For more on this, see https://bloom.oscillate.io/docs/debugging-avr-debugwire

[cbwolfe94]

Noted. Also I like your profile pic. I am a Chimchar man myself, but I do like Turtwig.

[navnavnav]

Thanks! 😊