#avr Logs

Jul 20 2020

06:04 AM Red_Tide: hey so I am trying to program an atmega644p with avrdude, but it is giving me a device signature of all 0
06:10 AM Red_Tide: I checked the usb connection would I be having this problem if I had accidently enabled a crystal and was not using one?
06:18 AM Red_Tide: hmm no luck will not let me adjust fuses just gives me same error msg
06:25 AM strata: need jtag or a HV programmer
06:31 AM Red_Tide: those are both special pieces of hardware yes I have a usbtiny programmer only
07:06 AM skz81: Red_Tide, you may try to generate a square wave from another AVR, if you have some handy...
07:06 AM skz81: I guess it would default to 1MHz or something (unsure about the m644p)
07:09 AM skz81: Hum I guess it doesn't matter actually. Should be enough to revive it enough to reprogram the fuses. Your applicative delays may be wrong tho... ^^
02:08 PM xMOPX is now known as XMoPX
03:57 PM TOB_CyxoB: Hello, starting out with attiny406 on Linux. Does anything work with Pickit4? Everything seems a bit dated... Is there replacement for PICkit4 with 12V (high-voltage) UPDI support? Thanks
03:58 PM LeoNerd: No idea about pickit but if you want a 12V-capable UPDI programmer, I make/sell them
03:59 PM LeoNerd: https://www.tindie.com/products/leonerd/avr-updi-programmer-with-12v/
03:59 PM TOB_CyxoB: LeoNerd, wow cool does it support avr-gdb?
03:59 PM LeoNerd: No idea. Does avr-gdb support UPDI over a plain UART ?
04:01 PM TOB_CyxoB: I guess the answer is no :) avr-gdb talks to server that supports gdb requests and translates them to UPDI...
04:01 PM TOB_CyxoB: LeoNerd, how do you debug?
04:01 PM LeoNerd: How do I? Usually by making an LED blink at the right time. Or just writing stuff out of the serial console
04:01 PM LeoNerd: That's what the second port here is for :)
04:02 PM LeoNerd: But anyway, if you have a gdb server thingy that talks UPDI over UART, that would work with this
04:02 PM TOB_CyxoB: :) I hear you
04:02 PM TOB_CyxoB: averice may have done that but I think it doesn't work with UPDI
04:03 PM LeoNerd: ?
04:04 PM TOB_CyxoB: sorry avarice
04:05 PM LeoNerd: It's more your statement doesn't make sense
04:05 PM LeoNerd: If "it doesn't work with UPDI" then they haven't "done that"
04:06 PM TOB_CyxoB: avarice provides server for gdb but it development for avarice stopped in 2012
04:06 PM LeoNerd: Ah, a shame
04:06 PM skz81: <LeoNerd> How do I? Usually by making an LED blink at the right time. >> somtimes, a logic analyzer plugged on a GPIO is better. Got a LED bliking, but when reaching the bug, was full-on, full-off, or even dimmed.
04:06 PM skz81: So useful :)
04:06 PM LeoNerd: Yah.. LA on a spare pin can be handy indeed
04:07 PM LeoNerd: Send little pulse-trains to identify parts of the program. I've done that before too
04:07 PM LeoNerd: Usually far more handy than a gdb console
04:07 PM TOB_CyxoB: Yes it is the only way to get real timing info with a scope or something
04:08 PM TOB_CyxoB: But if you are trying to figure out if you've configured peripheral just like you wanted to gdb makes nice dump of data structures etc... I'm just testing waters to see what is available
04:09 PM LeoNerd: Well, if anyone were to write a updi-uart server for it, then this would do it
04:09 PM LeoNerd: I have no idea how to write such a server
04:10 PM TOB_CyxoB: LeoNerd, what software do you use with your programmer?
04:11 PM LeoNerd: My own avr-udpi program
04:11 PM TOB_CyxoB: One stop shop :)
04:11 PM TOB_CyxoB: cool
04:11 PM LeoNerd: but you could also use pyupdi. or probably avrdude if anyone ever gets around to writing (you guessed it) a updi-uart implementation
04:11 PM LeoNerd: I still have no idea why they still haven't
04:12 PM LeoNerd: I may get really annoyed at them and just write it for them one day
04:13 PM TOB_CyxoB: I bet your sales will go way up...
04:13 PM TOB_CyxoB: especially if you make it work with the debugger
04:14 PM LeoNerd: That would require me to know how to do that bit
04:14 PM LeoNerd: Me working out how to talk to avrdude or gdb - much work involved
04:14 PM LeoNerd: Anyone else workign out how to send UPDI over a serial port - trivial. You just write the bytes.
04:15 PM TOB_CyxoB: well here is a starting point: https://www.embecosm.com/appnotes/ean4/embecosm-howto-rsp-server-ean4-issue-2.html
04:16 PM LeoNerd: OK yeah that's a rather nontrivial amount of translation needed in the middle then
04:17 PM LeoNerd: reading/writing memory isn't hard, but a lot of the step and control stuff requires talking ot the OCD parts of the chip. Which Microchip haven't documented
04:17 PM LeoNerd: Intentionally :(
04:17 PM TOB_CyxoB: Well, that's how you'll know that your hardware is unique...
04:17 PM TOB_CyxoB: Only you will sell it ;)
04:18 PM LeoNerd: It's unrelated to the hardware
04:18 PM LeoNerd: It's about the bytes to talk /directly/ to the chip with
04:20 PM TOB_CyxoB: I see, flipping through UPDI documentation for attiny406...
04:20 PM LeoNerd: You'll notice an absence of docs about the OCD
04:20 PM LeoNerd: I may get around to rev-eng'ing it one day, out of one of the Xplored devices
04:20 PM LeoNerd: Just.. Eh. ETIME
04:21 PM TOB_CyxoB: I hear you
04:23 PM TOB_CyxoB: LeoNerd, thank you
04:39 PM TOB_CyxoB: Another question: did anybody use microchip-direct with "Atmel" chips? Web-site says they support it for 15c a chip but just wanted to make sure.
04:40 PM TOB_CyxoB: Just don't want any surprises (I get a lot of them with Microchip).
09:39 PM rue_mohr: yea microchip is trouble and I prefer to steer clear
09:40 PM rue_mohr: I started with PICs and moved to AVRs for good reasons
09:40 PM rue_mohr: so now I'm moving to stm32
11:31 PM day_ is now known as day