Back
[05:26:56] <julius> cehteh, on the backside are two traces that start at the in side and go to 75% of the board, but not all the way to the end
[07:42:51] <aczid> anyone here have experience writing bootloaders for AVRs that lack a BOOTRST fuse?
[07:44:13] <aczid> my plan is to use the normal interrupt vector table to get the regular reset vector to jump to the bootloader, then switch interrupt vector banks with the IVSEL bit, then fill the bootloader's IV table with jumps back to a 'virtual' IV table in the application space. is that sane?
[07:46:09] <aczid> my concern is that I don't want to make the application code responsible for jumping to the bootloader after a flash: i.e. I don't want to flash the reset vector every time
[07:46:51] <cehteh> looked how other bootloaders do it?
[07:47:08] <cehteh> https://github.com/micronucleus/micronucleus fyi
[07:47:08] <aczid> could only find ones that rely on BOOTRST so far, if you can recommend another one that'd be great.
[07:47:17] <aczid> cool, will take a look, thanks
[07:48:00] <cehteh> bbl
[07:50:19] <aczid> it seems this bootloader doesn't use any interrupt vectors except for reset in the crt1.S
[07:50:25] <aczid> thanks though
[07:52:21] <lorenzo> hm
[07:52:27] <lorenzo> is there a way to send the degree symbol via uart?
[07:52:44] <lorenzo> I've tried \xB0, \xA7 without luck
[07:52:45] <LeoNerd> ?
[07:52:53] <LeoNerd> UART sends number
[07:53:03] <LeoNerd> The meanins of those numbers is entirely up to you
[07:53:28] <LeoNerd> Maybe you'll pick a character set + encoding that includes the degree symbol
[07:54:12] <lorenzo> eh, I'm using ASCII but my terminal doesn't seem to like it
[08:05:34] <cehteh> lorenzo: utf8 ftw :D
[08:05:48] <cehteh> bbl again
[08:06:29] <LeoNerd> Well, yes; the degree symbol doesn't appear in ASCII
[08:06:34] <LeoNerd> So you'll have to pick a different set/encoding
[08:40:56] <cehteh> i added utf8 support to my UART lib (lineeditor)
[08:41:27] <LeoNerd> I imagine about the only thing you'd need to do there is backspacing
[08:41:37] <LeoNerd> or maybe you support arrow keys and actual editing in the middle too?
[08:54:46] <cehteh> yes
[08:55:00] <cehteh> and manage space
[08:55:14] <cehteh> there are surprisingly many corner cases
[08:55:50] <cehteh> actually i discovered there is some lingering bug with 3 byte (chinsese) characters on monday, had no time to fix it yet, will do so soon
[08:58:25] <cehteh> i made the line editor rather feature complete (overwrite mode, backspace, delete, cursor keys, history) .. later one can configure things out for space reasons
[09:28:00] <twnqx> i, on the other hand, would just & 0x7f everything there .P
[10:44:37] <LeoNerd> Ohyes.. doublewidth characters will annoy you there
[11:49:40] <vaskozl> Hey anyone using you complete me from vim?
[12:30:11] <Lambda_Aurigae> I didn't even know it existed.
[12:30:16] <Lambda_Aurigae> but I'm an old vi person myself.
[12:31:14] <Lambda_Aurigae> glub...that makes it look like microsoft visual studio or something.
[12:32:12] <Lambda_Aurigae> looks annoying as hell.
[12:33:58] <julius> hi guys
[12:35:03] <Lambda_Aurigae> hi julius
[12:35:37] <julius> my moist sensor keeps doing things differently than expected, now when i disconnect gnd from the sensor and only connect it for a short ammount of time i get one value. but after that value the rest is 0 again
[12:36:32] <Lambda_Aurigae> I'm guessing you need to learn how a relaxation oscillator works and get an oscilloscope to see what it is doing.
[12:37:03] <julius> that would be a good way to test the circuit
[12:37:07] <Lambda_Aurigae> I would put a frequency counter on the output and see what it is putting out.
[12:37:28] <Lambda_Aurigae> but, for that, an oscilloscope is necessary I would think.
[12:37:34] <julius> i wrote a frequency counter with timer0
[12:37:41] <LeoNerd> I use my oscilloscope :)
[12:37:48] <julius> let me check my code again
[12:38:15] <Lambda_Aurigae> then make sure the frequency counter is working right.
[12:38:29] <Lambda_Aurigae> maybe, with another avr or a 555 timer to generate a pulse stream for you to test against.
[12:38:51] <Lambda_Aurigae> do you know what the frequency range is that thing is supposed to put out?
[12:40:21] <Lambda_Aurigae> I would guess in the 10khz to 500khz range but not sure...that's just a WAG.
[12:46:57] <julius> a few hundreth khz up to megaherz
[12:47:27] <julius> i could swear that this other frequency counter code was working before, now it doesnt :(
[12:49:57] <julius> any idea why line: 47 wont toggle the led every second?
http://codepad.org/VVlWV7HW
[12:51:38] <julius> oh wait
[12:51:39] <julius> never mind
[12:51:44] <julius> sei() was commented out
[12:52:03] <Jartza> yay new shinies
https://drive.google.com/file/d/0B2dTzW9TMeBxMlYtQWZKS1Exems/view?usp=sharing
[12:59:45] <julius> Lambda_Aurigae, ok the frequency counter works. i can count a 27khz signal generated for the water pump by timer1
[13:00:07] <julius> maybe i killed the sensor by static charge
[13:26:05] <learath> BBB rocket cape?
[13:26:11] <learath> what is a "rocket cape"
[14:03:27] <wpo> gives your bbb flying abilities
[14:12:43] <applepi> Hi all... I'm working on a small i2c test for an atmega128rfa1, talking to a zx motion sensor (just as a dummy test), but I'm having some weird behavior... in between sending the START condition, and writing the address, I'm seeing a two-clock-long period of SCL going high
[14:14:24] <applepi> Is this normal? I took a capture of it here, it seems to be confusing the digiview capture and making it think the data is bit shifted one to the left, I'm not sure if it's affecting the device yet, but it looks strange:
http://i.imgur.com/JMMAK9C.png
[16:48:26] <julius> on some days amtel just works against me
[16:48:43] <LeoNerd> Oh?
[16:49:32] <julius> yesterday i killed a sensor
[16:49:43] <julius> today my pwm code, that did work before wont
[17:47:28] <cehteh> julius: you use git?
