#avr Logs

Jul 15 2022

01:30 AM Phantom: qu1j0t3: I also vote for the wrong fuses, they also set the clock source and clock divider
04:24 AM twnqx: exp: want a hongkong reseller? they do full reels only though :P
04:26 AM exp: twnqx: of which?
04:26 AM twnqx: you can ask for anything :P if they have it, they'll tell you
04:27 AM twnqx: i don't know what cpart digikey pushed back again
04:27 AM exp: oh, LM5050MK2
04:27 AM exp: but i have dozens of backorders, i don't think they're essential yet
04:27 AM exp: but we're going to run out in the coming year
04:28 AM twnqx: heh, same
04:28 AM twnqx: i am currently trying to go to stock of 10k pieces of each i need...
04:28 AM twnqx: which would be ~2 years
04:29 AM twnqx: in some parts i think i have been overdoing it, i'll soon (january) have 20k step-up regulators :S
04:30 AM exp: very nice, i only have a small selection of buck/boosts, mostly LM5176
04:30 AM exp: probably < 1000 of them
04:33 AM twnqx: MIC2876-AYMT-TR here... 10000 in stock, 10000 pieces on order
04:34 AM exp: that looks like quite a nice part
04:35 AM exp: 4.8A is good until you wanna go deep into boost, i need to do a 5:1 almost
04:35 AM exp: you should see the frigging size of the inductor i need to produce 150W or so out of this damn thing
05:39 AM specing_ is now known as specing
07:47 AM qu1j0t3: nuxil: Phantom will look into it, thankyou.
09:41 AM qu1j0t3: I feel stupid for asking this, but is there anything more to using port C on a 168 than setting Direction and setting Data? because i got nothing on that port. Chip damaged? (it was basically new)
09:42 AM qu1j0t3: (and yeah i have a working program on other ports)
09:46 AM exp: JTAG fuse?
09:46 AM exp: don't know 168 offhand
09:47 AM qu1j0t3: i hate mysteries ;-)
09:50 AM Cracki: set bit in DDRC, set bit in PORTC, ... that oughta be it
09:50 AM Cracki: show _how_ you do that
09:51 AM qu1j0t3: oh, i have it owrking on other ports. i know how to do that. :)
09:51 AM qu1j0t3: i'm asking about reasons _other_ than those :)
09:51 AM Cracki: it's either pebkac or some power saving feature but I kinda doubt it
09:51 AM Cracki: or it's fried
09:51 AM qu1j0t3: i'd go with 'fried' except it's a new chip
09:52 AM Cracki: if you only tell us what you've already checked, we can't tell you more than you already know
09:52 AM Cracki: 20 questions is a poor game to play with other people's time
09:52 AM qu1j0t3: ...
09:52 AM qu1j0t3: okay no worries, i'll refrain!
09:53 AM Cracki: you get what I'm saying? I'm asking you to present a lot of data, rather than waiting to be prompted
09:53 AM Cracki: standard stackoverflow/helpdesk interaction
09:53 AM qu1j0t3: it's fine, i shoudl be $working anyway. sorry for the .. whatever
09:53 AM qu1j0t3: just hate taking a chip from the 'new' bag and putting it in the 'can't use' bag.
09:53 AM Cracki: what, they're cheap
09:54 AM Cracki: take one, see if it does the same thing
09:54 AM Cracki: if it does, it's not the chip
09:54 AM qu1j0t3: 1) cheap, 2) can't get a 328 till october.
09:54 AM qu1j0t3: unfortunately i'm down to my last 168 and last 328.
09:54 AM Cracki: basic debugging. you aren't gonna make any progress if you think your time is worth less than the cost of a chip
09:54 AM qu1j0t3: oh, i'm not new to basic debugging.
09:54 AM Cracki: ¯\_(ツ)_/¯
09:55 AM exp: check the actual code being run
09:55 AM qu1j0t3: exp: Yeah.
09:55 AM exp: you might for some reason have the wrong port pointers
09:55 AM qu1j0t3: exp: there are a few more theories to explore. i am using the avr headers but i haven't spotted a build config error yet, it's still worth going over and over and over it. i'll check the assembler as you say
09:56 AM qu1j0t3: exp: Yeah, that did occur to me. last night i was only able to check that at a Makefile level,
09:56 AM qu1j0t3: exp: maybe tonight i'll take it further.
09:56 AM qu1j0t3: but other ports are working so it's a long shot.
10:04 AM qu1j0t3: exp: Now that i think about it after a night's sleep, i am more convinced it's a build issue. will check later
10:05 AM exp: good luck ;)
10:05 AM qu1j0t3: o/
11:53 PM qu1j0t3: lol, of course fuses fixed the clock issue. but now the board doesn
11:53 PM qu1j0t3: t probe as a usb/serial device, so... can't use the bootloader after all.
11:53 PM qu1j0t3: one step forward, one step back.
11:53 PM qu1j0t3: gotta laugh
11:58 PM Phantom: atleast yours you have a community to help
11:58 PM Phantom: we had issues at work... and fuck it, it was painfull! (and not fully fixed yet)