Do I have it right that if I send anything out on USART1 it should come out of the USB/CDC port? (Com21 on mine)
Is there anything that needs to be bridged? It seem not.
Do I have it right that if I send anything out on USART1 it should come out of the USB/CDC port? (Com21 on mine)
Is there anything that needs to be bridged? It seem not.
That's usually the way.
(haven't tried mine yet)
hmm nothing is coming out but I have just modified my ASM driver for USART1, the version for USART0 was working with the Tiny817 and they seem to be the same type of USARTs.
I'll try USART0 on PA0 and PA1 with one of my TTL/RS232 boards.
USART0 is now working, need to set up TXD as output like the Xmegas. Also the clock defaults to 3.333 MHz.
Nothing on USART1/CDC/USB com port.
EDIT of course needed to update Studio to 1645 but don't rely on breakpoints working!!
Does it need any of the flow control signals asserted ... ?
And finally for the night I can't get the memory mapped data to print, going to the "data MAPPED_PROGMEM" I can't see the string to print, it is there in normal PROGMEM LPM style.
With the Tiny817 it was retrievable by using
ldi zl, low ((Button_pressed * 2) - 0x8000) ldi zh, high ((Button_pressed * 2) - 0x8000)
but this only prints garbage.
Maybe tomorrow.
but since it has more than 32K flash it must start lower. 0x4000 would be my guess (RTFM)
Does it need any of the flow control signals asserted ... ?
Just tried with both RTS and DTR asserted, no cigar.
0x4000 would be my guess (RTFM)
Also no cigar. Nothing at where Z is pointing to. I'm ASS-U-MEing that this window would show the 2 strings I have in the code. I can see the 2 strings in normal progmem and both string work using LPM.
Never mind about the USB/CDC output, I had a copy and paste bug and it was till initializing USART0 instead of USART1 all is well with that.
Maybe I'll start another thread about the memory mapped printing if I can't find it myself.