#avr Logs

Jan 15 2018

12:30 AM _ami_: what is the rise/fall time of an avr pin? i think its related to F_CPU/clk?
12:34 AM _ami_: e.g.
12:34 AM _ami_: PORTB |= (1 << PB0);
12:34 AM _ami_: PORTB &= ~(1 << PB0);
12:34 AM _ami_: how much time does it take to reach from HIGH to LOW practically?
12:34 AM _ami_: interested in knowing the fall time from 70% to 30%
12:34 AM _ami_: does anybody have done some experiment on it?
12:36 AM Casper: most likelly specified in the datasheet
12:37 AM _ami_: ok, should search for slew rate in DS.
12:37 AM _ami_: and its not controlled by cpu speed. ok, thats good to know.
12:39 AM Casper: I would be surprised that a digital electrical parameter would be cpu speed related...
12:56 AM _ami_: Casper, is there any special mechanism i2c slaves have which tell them to me in particular i2c speed mode.
12:56 AM _ami_: ?
12:56 AM _ami_: e.g.
12:56 AM _ami_: i am reading ina219 DS
12:56 AM _ami_: http://www.ti.com/lit/ds/symlink/ina219.pdf
12:56 AM _ami_: page no. 6
12:56 AM _ami_: there are two speed modes.
12:57 AM _ami_: does ina219 switch to HIGH speed mode if it detects high speed master?
12:58 AM Casper: most likelly it detect by timing
12:58 AM _ami_: Casper, by t(HDSTA)?
12:58 AM _ami_: hold time before START
01:01 AM Casper: not sure, but most likelly. To be frank, I never worked with i2c yet, but considering that the first 'bit' length change with the speed, it would be easy to detect it
01:02 AM Casper: "if bit shorter than x then ignore, if shorter than y then fast speed, if shorter than z then slow speed, else error out"
01:03 AM _ami_: yes, this should be the case.
01:04 AM _ami_: need to try and check.
01:05 AM _ami_: Casper, http://amitesh-singh.github.io/stm32/2018/01/07/making-i2c-slave-using-stm32f103.html <-- i recently implemented an i2c slave on stm32f1. In that case, i set the speed to standard. (100 Khz)
01:05 AM _ami_: but it would be good idea to have several speed modes.
01:06 AM Jartza: _ami_: most i2c devices are slaves and they follow the master clock, most timing parameters in data sheet are just i2c standard mins & maxes
01:06 AM _ami_: there are so many mins corresponding to timing parameters.
01:07 AM Jartza: I have played around with i2c in current customer project a lot and tested i2c on 12 different chips and on dozens of sensors/whatnot via i2c
01:07 AM _ami_: nice.
01:07 AM _ami_: you did master or slave?
01:07 AM Jartza: even if some chip says it supports "normal" and "fast" mode, they usually support anything in between
01:08 AM Jartza: both of them. I fixed various bugs in vendor SDKs and made workarounds for several silicon bugs :)
01:08 AM Jartza: nobody believes how many ways i2c peripherals can be broken
01:09 AM _ami_: Jartza, i faced those silicon bugs in stm32f1 :P
01:09 AM _ami_: that was a big pain :/
01:10 AM _ami_: i did not know abt those silicon bugs until i read stm32f1 Erratas
01:10 AM Jartza: kinetis was the most stubborn, and errata only covered some of the silicon bugs
01:11 AM Jartza: but kinetis i2c peripheral is derived from coldfire, the whole design is from motorola-era :P
01:11 AM Jartza: including bugs
01:11 AM Jartza: so some help was found by reading coldfire documentation
01:12 AM Jartza: but if chip says it supports fast mode and high-speed mode, then probably any clock between 400k and 3.4M is fine :)
01:12 AM Jartza: not necessarily, but most probably
01:12 AM _ami_: Jartza, i was wondering how i2c slave know the speed of i2c master?
01:12 AM Jartza: this i2c LCD I have says to support fast mode, I've been running it with i2c clocks from 100Hz to 400kHz :)
01:13 AM Jartza: _ami_: master drives the SCL
01:14 AM Jartza: what those speeds actually mean is the i2c start detection usually
01:14 AM Jartza: as long as the start signal is within the limits supported by chip, the clock can be anything in real transfer
01:14 AM _ami_: yes, the t(HDSTA) time -
01:14 AM _ami_: so i2c slave has to have a mechanism to know t(HDSTA) time ?
01:15 AM _ami_: then only it can configure its i2c peripherals according to i2c master speed.
01:15 AM Jartza: well, the i2c standard defines the times from SDA low to SCL low in start
01:17 AM Jartza: but most sensors talking to i2c don't really "adjust" anything, they just follow the SCL speed in i2c
01:18 AM Jartza: and START signal detection has some minimum and maximum times of course
01:18 AM _ami_: hmm.. i get the idea.
01:20 AM Jartza: some sensors also use the i2c ability to stretch clock if they can't follow the master clock speed
01:20 AM Jartza: which actually is nifty feature, but causes a lot of headache because broken i2c peripherals :P
02:37 AM Jartza: "These bits set to a 1 whenever a Current register reading is below (Imn) or above (Imx) the IAlrtTh thresholds. These bits may or may not need to be cleared by system software to detect the next event."
02:37 AM Jartza: mmkay
02:37 AM Jartza: I may or may not clear them then
05:03 AM polymorph: [03:28] <nuxil> but that will only trigger on positive edges - adc does nat have edge detect, and auto trigger is continuous, btw adc is slow.
05:04 AM polymorph: you will write a code to derivate/average samples and set thresholds
05:06 AM polymorph: [07:30] <_ami_> how much time does it take to reach from HIGH to LOW practically - it is pretty fast actually, you can do 2MHz+ datacom with them,
05:07 AM polymorph: lol wtf? http://www.microchip.com/wwwproducts/en/ATmega168PA just found that microchip now makes atmel arms?
05:07 AM _ami_: thanks
05:07 AM _ami_: what!! u did not know?
05:07 AM _ami_: living under rock? ;)
05:10 AM polprog: microcheap bought atmel like a long time ago :P
05:12 AM polymorph: https://www.microchip.com/announcements/microchip-technology-inc-acquires-atmel - lol?
05:13 AM polymorph: polprog: does that mean now that they will make shit atmegas?
05:13 AM polprog: no idea
05:13 AM polymorph: ;<
05:13 AM * polprog is planning to learn stms *just in case*
05:13 AM polymorph: anyway i can got arms, it is 2018 already
05:14 AM polprog: all ive needed all ive wanted is here in my arms
05:14 AM polymorph: polprog: looking at LPC1763
05:14 AM polprog: nxp
05:14 AM polprog: hmm
05:14 AM polymorph: 100MHz arm ;> cool stuff
05:14 AM polprog: well if i had openocd working this would probably mean i can buy any arm, since the programmers are the most problematic
05:15 AM polymorph: it does and i saw llvm compiler that supports it
05:15 AM polprog: but on the other hand "words are very unncecesary" :P so i could try pics !
05:15 AM polymorph: hehe
05:15 AM polprog: if there was a pic bitbang flasher anywhere
05:15 AM polprog: ;)
05:15 AM polprog: yeah but ill just get a blue pill...
05:16 AM polymorph: polprog: i want parallel port too ;>
05:16 AM polprog: i just got a pc with one!
05:16 AM polymorph: https://embdev.net/topic/188600
05:16 AM polymorph: i only have pcs with parallel port
05:17 AM polprog: wow
05:17 AM polymorph: maybe only my T400 laptop does not have it anymore
05:17 AM polprog: old much
05:17 AM polprog: anyway
05:17 AM polprog: gotta go for a walk
05:17 AM polymorph: haha
05:17 AM polymorph: polprog: i have a g2030 with 8GB ddr3-1333 and parallel port, is that old for you?
05:18 AM polprog: not really
05:18 AM polprog: i mean i have a gigabyte board with no parpoprt but my compaq has one
05:18 AM polprog: anyway, see ya
05:18 AM polymorph: btw there used to be headers you can plug in
05:40 AM Jartza: polymorph: I don't know about atmegas, but at least the new attinys are amazing
05:40 AM Jartza: more like atxtiny
05:41 AM Jartza: they have great peripherals, hardware multiplier, memory mapped flash, sleepwalking, ccl, event system
05:41 AM Jartza: like xmega but tiny
05:41 AM nuxil: polymorph, Huu?? according to my datasheet page 321, you can set it up to trigger on a positive edge using Ain0 "External inerrupt", The trigger source is selected by setting the ADC Trigger
05:41 AM nuxil: Select bits, ADTS in ADCSRB.
05:42 AM polymorph: nuxil: in digital mode
05:42 AM polymorph: there is edge trigger
05:42 AM polymorph: you decide which edge you want, ignore the other.
05:42 AM nuxil: yea.
05:42 AM polymorph: at least for the now atmego, there is pinchange int
05:43 AM polymorph: new
05:45 AM polymorph: btw you can't trigger on adc analog voltage if it is not ding conversion ;)
05:46 AM polymorph: the continuous autotrigger is the only way it works fast
05:47 AM polymorph: there is however an analog comparator that works all the time and might be able to trigger... but you can use an external one
05:48 AM Jartza: built-in comparator can switch on both edges
05:48 AM Jartza: switch? trigger...
05:49 AM polymorph: Jartza: he was asking about interrupt
05:49 AM nuxil: yea i only want to sample the input then there is a change on the pin.
05:49 AM nuxil: *when there
05:50 AM polymorph: you dont know if there is change until you sample
05:50 AM polymorph: but on 10 bit there probably is
05:51 AM polymorph: so microchip boucght atmel ? i didnt know they had that kind of money
05:53 AM nuxil: i was thinking if i setup the analog comp in toggle mode or something and when that triggers. enable adc and read the pin? is that a way to do it ???
05:53 AM polymorph: and atmel was doing militarly stuff too
05:54 AM nuxil: polymorph, space stuff aswell :)
05:55 AM polymorph: nuxil: last time etested i have put adc in continuous mode, and i averaged it, and placed it in a variable, so i can read the value anytime
05:58 AM polymorph: https://sites.google.com/site/tahull83/projects/tips-tricks/OpenOCD-Mod/openocd-with-parallel-port-jtag-wiggler
06:18 AM polymorph: https://hackaday.com/2016/10/18/whats-the-deal-with-atmel-and-microchip/
06:18 AM polymorph: Microchip does not help open source projects at all. In fact, they sell old versions of GCC for $800 because they keep the build arguments secret. It’s time to abandon Atmel and AVR because they are going to same way. - oh i remember ;)
06:20 AM polymorph: Rest in Pieces Atmel
06:31 AM nuxil: relax, dont be so negative
06:37 AM nuxil: polymorph, if they start to fuck up for the hobbyists. people will leave for other chips(stm32 etc). so Q. why would they try and kill something that gen income ?
06:37 AM nuxil: there is a hole commuinty that uses avr's, arduino etc.
06:40 AM nuxil: if they keep the same attatute against hobbyists/opensource project in the future as thet have in the past. then microship will soo also be dead.
06:41 AM nuxil: to many other chip makers offer "open source" solution that they can keey can keep ignoring it.
06:42 AM nuxil: *that they can ...
06:42 AM nuxil: just my thought on it tho.
06:44 AM Snert: it's all in how much income.
06:44 AM nuxil: well. isnt some income better than 0 income ?
06:48 AM Snert: below a certain amount (even if it's profit) a corporation doesn't even care.
06:49 AM Snert: what good is $1,000.00 profit.
06:49 AM Snert: hey wanted 100million.
06:49 AM nuxil: greed always wants more :p
06:51 AM nuxil: well. im not jumping the ship yet. i have not seen any changes.
06:51 AM nuxil: all i know is that the CEO said that some of the chips will be discontinued.
06:51 AM nuxil: which one remains to be seen.
06:52 AM nuxil: but that is to be expected. like there is tonz of atinys.
06:52 AM nuxil: old atmegas
06:53 AM nuxil: would be cool is the pic line was discontinued tho :p lol
06:53 AM theBear: :)
06:56 AM nuxil: if they do anything with the atiny85, i'll hunt down the CEO and give him some ass kicking.
06:58 AM nuxil: i'll probably need to stop by Jartza and pick him up aswell :p
07:39 AM polprog: if you give me a cat5'o'9tails can go with you as well
07:43 AM revdns: Hello everyone! I bought a USB 2 TTL conv. with auto-reset. As i see the AVRdude try to upload new firmware too long after ATMega reset, how can I remove delay or increse attemps?
07:44 AM polprog: im not sure bout that but you can manually reset the avr, just put a jumper from RST pin to ground
07:45 AM revdns: I know that but i'm too lazy :) is there no chance to do that in the other way
07:45 AM revdns: I'm reading avrdude.conf now, but there is multiple delays settings :)
07:50 AM polymorph: nuxil: another problem is i always said that pic is a toy and not meant for industrial use, if they make pic out of atmels then im out
07:52 AM polprog: ive seen people using pics in proffesional applications
07:53 AM polprog: but it was mostly like "receive this 4 bytes over uart and set PWM accordingly to control the leds"
07:53 AM polprog: maybe except the control box which has had some beefy pic inside etc
07:54 AM polymorph: polprog: it is unreliable.
07:54 AM polymorph: bad hardware design
07:54 AM polprog: i dont know, never used pics
07:54 AM polprog: iirc they have paged ram
07:55 AM polprog: that must be pain in the ass
07:55 AM polymorph: and horrible instruction set
07:55 AM polprog: if its turing complete....
07:55 AM polymorph: oh and you need many instructions to outport lol
07:56 AM polprog: i need to take a look lol
07:56 AM polprog: 14 bit word
07:56 AM polymorph: it is like 1/10 MIPS/MHz at best
07:56 AM polprog: okay
07:57 AM polymorph: i also read a story where pics died because bad design, adc damaged because of thermal expansion issues tearing apart the chip
07:57 AM polymorph: it was major problem
07:58 AM polprog: i can see the set, looks a bit small... whand whats with this W register
07:58 AM polprog: horrible indeed
07:59 AM polymorph: W is god lel
07:59 AM polprog: BTFSS im polish and i cant even pronounce it
08:00 AM polymorph: polish is cool
08:01 AM nuxil: iirc pic need around 4 cycles per instructions while avr only need 2, so you need to run pic at twise the the speed to do the same job
08:02 AM polymorph: at least some has 1/10 MIPS / MHz...
08:02 AM polymorph: i don't even want to know about the new ones lol
08:03 AM polymorph: atmega168 was approaching 1 MIPS per MHz
08:04 AM polprog: i have the instruction set open and it says most need 1 cycle
08:05 AM polymorph: anyway i did not make this up
08:05 AM nuxil: polymorph, the ATmega324P
08:05 AM nuxil: achieves throughputs close to 1MIPS per MHz. :)
08:05 AM polprog: i know, i have heard that pics arent that fast
08:05 AM polprog: s/fast/efficient/
08:06 AM nuxil: well i can do: Up to 20 MIPS Throughput at 20MHz, with this chip :)
08:07 AM nuxil: so i guess the same goes for all newer avr's
08:07 AM polymorph: nuxil: i used mega168 at 8MHz and was surprised about the 8 bit computing power, even did 32 bit math with it
08:07 AM polprog: its pretty C and asm friendly
08:08 AM polymorph: instructian set somewhat similar tox86
08:08 AM polprog: my biggest problem with learning avr assembly was basically putting the toolchain together
08:08 AM polprog: it's greatly simplified compared to x86
08:08 AM polymorph: yea
08:08 AM polprog: (im starting to learn x86/x86_64 now)
08:08 AM polymorph: and you write an os all the time :)
08:08 AM nuxil: polprog, whats hard with sudo apt-get intall avrdude :p
08:09 AM polprog: and boy all those weird stuff, i expceted huge difference between avr and x86 but not that weird stuff
08:10 AM polprog: nuxil: its not that, it took me a good day to find out there is Gnu Assembler (gas) and Netwide Assembler (nasm) and they are totally incompatible
08:10 AM polymorph: polprog: you can set gas to be intel syntax
08:10 AM polprog: (i compiled .s files with gcc on avrs and for x86 id have to look at makefile)
08:10 AM polymorph: instead of crap&t
08:11 AM polprog: polymorph: thanks for the info... turns out avr-gcc uses intel syntax
08:11 AM polprog: this will greatly reduce my fatigue with this crap
08:11 AM polprog: no %r1 or other bull
08:11 AM polymorph: polprog: you can also use C and do inline asm with gcc
08:11 AM polprog: i know
08:12 AM polymorph: who else planning to ditch avrs and use arms instead?
08:13 AM polprog: "else"
08:13 AM polymorph: the price is not high
08:13 AM polprog: i wouldnt say im ditching avrs
08:13 AM nuxil: i got a nucleo sitting ready :p
08:13 AM polprog: i believe that you should use the right tool for the job
08:13 AM nuxil: havent open the package yet
08:13 AM nuxil: cos i feel like a arduino user when i look at it
08:13 AM polymorph: polprog: arm can flash a led more quickly lel
08:14 AM nuxil: :D
08:14 AM polprog: lol
08:14 AM polprog: when i was 7 i wanted to build a calculator with an amd athlon in it
08:14 AM polprog: kk
08:14 AM polprog: kek
08:14 AM nuxil: why not :p
08:14 AM polymorph: i did flash leds with an AMD64 clocked at 2.2GHz :>
08:15 AM polprog: polymorph: care to elaborate?
08:15 AM polymorph: through parallel port
08:15 AM polprog: ah
08:15 AM polprog: i thought that! i even read a tutorial on linux using parport as gpio
08:15 AM polymorph: and i have driven a stepper motor with it
08:15 AM polymorph: wrote some C code on linux
08:17 AM polymorph: Hm my tft started displaying volume up down and brightness up down crap, i hit it several timus with a screwdriver and it is ak now
08:17 AM polprog: lol
08:17 AM polymorph: the philips tft shit's buttons rot away in a year
08:17 AM polprog: what the thing that uses the tft
08:17 AM polymorph: a g2030 with dvi
08:18 AM polprog: aha
08:18 AM polymorph: 19" philips tftshit
08:18 AM polymorph: ;/
08:18 AM polymorph: i like capacitive and hall buttons only
08:19 AM polprog: topre
08:19 AM polprog: yes
08:19 AM polymorph: i need to make my capsense testboard :(
08:20 AM polymorph: i already made a copsense button like >8 years ago using cmos ics without mcu that is not adaptive
08:20 AM polymorph: capsense
08:20 AM polprog: i made a capsense button with a bc547 :P
08:21 AM polprog: "button"
08:21 AM polymorph: oh i measured capacity, not noise :)
08:21 AM polymorph: i have inected a test signal between 2 plates, that are isolated and measured the feedback
08:22 AM polymorph: *injected
08:22 AM polprog: in the sense it lit a led up
08:23 AM polymorph: My only problem with this is it consumes a few microwatts because it is polling :(
08:23 AM polymorph: Also hall needs current to measure magnetic field
08:24 AM polymorph: a tiny magnet and coil could trigger an interrupt...
08:26 AM theBear: https://medias.audiofanzine.com/images/thumbs3/pulsar-lights-masterpiece-108-1742353.jpg this sucker is imho the king of capacitive/no-moving-parts touch-switchery...
08:28 AM theBear: not quite sure how they even put together the front panel (tho i been inside and out of many of them in previous lives) but it sure works nicely, excepting if it got excessive something all over either side of it... you know, like a thick coating of maybe cigarette smoke + smoke machine leftovers
08:28 AM polymorph: theBear: a metal foil can be attached to some silicone and covered with silicone/plastic so you have a button-like thing you can push with gloves, maybe underwater
08:29 AM nuxil: can the dielectric dry out in these capsense buttons :P
08:29 AM polymorph: But for consumer stuff a cap touch/proximity sensor is cool
08:30 AM polymorph: nuxil: it requires none
08:30 AM polymorph: air and silicone works
08:30 AM polymorph: also fiberglass...
08:31 AM polymorph: my first capsense button is 2 rectangles next to each other an a pcb... less than 10 nF
08:32 AM nuxil: no isolation on top?
08:32 AM theBear: polymorph, mmm, interesting.... we talking kinda adaptive self/continuously calibrating for the underwater/gloves stuff ?
08:33 AM polymorph: theBear: if it is sealed like that i don't think it requires that special stuff :)
08:33 AM polymorph: the conductive surface only gets a little closer under pressure, depends on depth
08:33 AM polymorph: casically it is a pressure sensor then
08:33 AM polymorph: b
08:34 AM nuxil: polymorph, bare metal isnt nice, assume you get some fault in you board while a person with a peacmaker touches the button :p
08:35 AM polymorph: i think i would make a lever that pulls the button instead so i can press it at any depth?
08:35 AM polymorph: nuxil: lol
08:35 AM polymorph: nuxil: a capacitive sensing button is isolated electrically
08:36 AM theBear: polymorph, oh, i thought the silicone was just for isnulation from the panel... mmm, i approve :)
08:37 AM polymorph: fiberglass is an insulator too
08:37 AM nuxil: polymorph, was a jokke but, a fault might mean that you get some unwanted discharge. sparks jumping over traces etc.
08:37 AM * theBear is isolated, and not just electrically <grin>
08:37 AM polymorph: you might be able to turn the board upside domn and sense through the fiberglass board
08:38 AM polymorph: that will be rated about 20kV maybe
08:38 AM polymorph: ac/dc
08:38 AM theBear: metallica
08:38 AM nuxil: fibreglass gets a exlelent conductor when its burnet :p
08:38 AM polymorph: nuxil: ya
08:38 AM theBear: yeah, but it needs a good burning
08:38 AM polymorph: nuxil: ok then get a glass or ceramic plate
08:38 AM nuxil: ^^
08:39 AM polymorph: it will widthstand some blowtarch
08:39 AM polymorph: i would lke to use a sapphire crystal glass layer
08:39 AM polymorph: that is kind of tough
08:39 AM polymorph: a bit expensive now ;<
08:43 AM polprog: i should rearrange my workshop
08:44 AM polprog: it being in my bedroom in a block of flats is not making it easy
08:44 AM polprog: but i dont have any other plce to put it
08:44 AM nuxil: sleeping with sexy chips ?
08:44 AM polprog: i guess i just need to get more component boxes
08:44 AM polprog: nuxil: my private stripper is in the toolbox
08:44 AM nuxil: ^^
08:46 AM polprog: ;)
08:50 AM revdns: I found my USB2TTL on Aliexpress, https://www.aliexpress.com/item/New-Arrival-6Pin-USB-2-0-to-TTL-UART-Module-Serial-Converter-CP2102-STC-Replace-Ft232/32610617027.html
08:50 AM revdns: Cloud someone help me with AVR Dude to wait for ATMega328 restart
08:51 AM theBear: erm, whaddya mean wait fro ? watcha doin exactly
08:51 AM revdns: Now it's look like, ATMega reseting too slow, so AVR Dude can not connect to bootloader
08:52 AM revdns: I'm using Arduino bootloader and PlatformIO IDE
08:52 AM theBear: oh look, it's like a little watchacallit, teensy programmer ?
08:53 AM theBear: erm, afaik arduino bootloader ain't ever gonna work over serial, it is for native usb chips... but feel free to correct me
08:53 AM theBear: that very translated page does suggest it has both clock and reset lines on the board.. you identified or using those at all ?
08:54 AM theBear: oh i see, lots of stuff on the bottom side that isn't on the header
08:54 AM revdns: It's working over serial, i can upload new firmware but with manual reset of AtMega, but i need to shot in avrdude getting something from avr
08:55 AM theBear: the umm, so when you not doing it that way (manual reset) how are you resetting your avr ? while we at it, is it in some big fancy dev-board, or just something minimal you rigged up ?
08:55 AM revdns: I has connected VCC, GND, TX, RX and Reset line
08:56 AM revdns: I make own PCB for that project (simplex ham repeater)
08:57 AM revdns: It's reseting AVR but too late
08:57 AM revdns: So i think to add delay before AVRDude send request to get some data from AVR
08:57 AM theBear: hmm, what else is on your reset pin ? what resistor and any caps ?
08:58 AM revdns: No it's now connected only to USB2TTL
08:58 AM revdns: directly
09:27 AM skz81: I doubt the statement that "[to] add delay before AVRDude send request to get some data from AVR [would be necessary]"
09:28 AM skz81: I mean, AVR *are* resetting in time with other USB 2 TTL chips (FTDI, ch390, ...) and avrdude is able to cope with it
09:30 AM skz81: I would suspect something weird with this particular adaptor... At the first glance, nevertheless
12:02 PM polprog: installed an ericson GPRS modem in this laptop as well, now in device manager i can see it registered as a GPS on COM5... and surprise surprise, putty shows empty NMEA sequences at 9600 baud :o
12:20 PM Casper: maybe you need to send an initialisation string
12:20 PM polprog: maybe
12:22 PM Casper: did you tried "at/gps" ?
12:24 PM polprog: id have to look at the docs. maybe some old map navigation soft would work with it. or qlandkarte..
02:30 PM Ameisen: Is there an easy-to-use serial-over-usb library out there like the Arduino's USB Serial code?
02:31 PM Ameisen: that's easier to integrate into baremetal implementations?
02:31 PM Ameisen: I've been trying to rip the Arduino's version, their code is just all over the place
02:31 PM Ameisen: which makes it difficult
03:14 PM antto: Ameisen LUFA i think has serial over usb for avr
04:40 PM polymorph: can the JTAG wiggler be used with avrdude to program an avr? :)
04:40 PM polymorph: https://wiki.openwrt.org/doc/hardware/port.jtag.cable.buffered
11:41 PM day__ is now known as day