#avr | Logs for 2016-03-10

Back
[02:10:29] <PoppaVic> well, that was a waste of two hours
[02:23:27] <PoppaVic> Lambda_Aurigae: fought with doze, installers - hell, even my Rand McNally Dock program.. No joy anywhere. So much for getting the stupid assembler .inc files
[02:23:57] <PoppaVic> oh, I forgot: I still hate windows.
[04:01:35] <julius> assembler is like shooting yourself in the food before running
[04:01:44] <julius> foot
[04:17:56] <Thrashbarg> shooting yourself in the foot with cycle accuracy
[04:37:45] <Jartza> wut
[04:37:49] <Jartza> assembly is nice
[04:37:59] <Jartza> and avra is quite decent assembler
[04:38:11] <Jartza> http://avra.sourceforge.net/
[04:38:18] <Jartza> even if it's not been updated for some while
[04:42:22] <julius> besides special cases where speed is more important than insanity i wouldnt use assembler
[04:42:57] <Jartza> I quite like it
[04:43:25] <Jartza> with assembly you don't have to guess what the compiler might do :)
[04:44:17] <Jartza> I do like C too, but sometimes I still write some code with assembly just to be sure things work like I want them
[04:54:50] <dunz0r> As long as you don't use crazy levels of optimization, the compiler usually makes the correct choice :)
[04:55:30] <dunz0r> I don't think I've ever had to do something in assembly because the compiler did weird things
[04:55:38] <dunz0r> I have however done things in assembly just because
[11:27:06] <keithbrown> has anyone worked with the BLE112a before?
[11:27:27] <Lambda_Aurigae> never met her.
[11:27:46] <keithbrown> shes beautiful
[11:32:56] <keithbrown> has anyone worked with the BLE112a before?
[11:35:17] <Lambda_Aurigae> I'm guessing nobody who is currently here/awake/not busy.
[12:01:19] <WormFood> keithbrown, why not just ask whatever question you have. You never know who might be able to help. Also, someone may be able to give you an answer, when you're not at the computer.
[12:02:38] <keithbrown> WormFood: thanks. im working with the bluetooth chip, and wanted to know if anyone had success with firmware/custom app programming
[12:03:15] <WormFood> You mean, reprogramming the firmware, of the bluetooth module?
[12:04:11] <keithbrown> correct and getting it to be readable by an existing phone app or one of their creation
[12:04:43] <keithbrown> WormFood: missing that one last step
[12:05:10] <WormFood> If your answer is not specific to the AVR, you might want to also try asking in #electronics
[12:05:44] <keithbrown> WormFood: ok thanks. wasnt sure where to ask
[12:06:15] <WormFood> that channel is a little more active, and might be able to give you a faster response.
[13:15:27] <PoppaVic> anyone got the atmel studio installed? I could use the stupid .inc files (booting back to doze was horrific, and the install failed and just sorta' locked - I give up)
[13:16:15] <Lambda_Aurigae> PoppaVic, it won't install on my computer.
[13:16:24] <PoppaVic> yeah. i was irked
[13:16:25] <Lambda_Aurigae> something about needing a window installed first.
[13:17:20] <PoppaVic> I dual boot, but last night was so horrific I am getting a new ISO and preparing for a complete reinstall and stealing the entire drive. I loath doze - it even screwed my gps updating and munged the device
[13:17:36] <Lambda_Aurigae> I won't install it here.
[13:17:42] <Lambda_Aurigae> I am forced to use it for work.
[13:18:02] <inkjetunito> window? isn't that the system used for powering internet connected billboards?
[13:18:03] <Lambda_Aurigae> for home, my wife has it on her laptop for the moment.
[13:18:04] <PoppaVic> well, if anyone can tarball those damned files, I can use them with avra.
[13:18:20] <Lambda_Aurigae> inkjetunito, yeah, the ones where you want to display that nice pretty blue screen.
[13:18:36] <Lambda_Aurigae> PoppaVic, what files is that?
[13:19:07] <PoppaVic> Lambda_Aurigae: I dunno if that even matters, now - doze is so "tablet" it's disgusting. Oh, the m*.inc files - the device includes
[13:20:18] <PoppaVic> damnit
[13:20:36] <PoppaVic> like m328p.inc and m1284p.inc - those things
[13:24:22] <PoppaVic> oh, sorry.. m328pdef.inc - like this: http://permalink.gmane.org/gmane.comp.hardware.avr.avra/95
[13:24:34] <Lambda_Aurigae> for some reason I used to think those were included in avr-libc or avr-gcc but can't find them.
[13:25:15] <PoppaVic> well, avr-gcc has io*.h, but avra uses avr's asm formats, so: above
[13:25:16] <Lambda_Aurigae> http://avr.8b.cz/inc/
[13:25:26] <Lambda_Aurigae> you might find what you need there.
[13:25:30] <PoppaVic> loading
[13:26:06] <Lambda_Aurigae> 328p is there.
[13:26:59] <PoppaVic> yep. cool.. All I need is the 1284p
[13:27:07] <Lambda_Aurigae> that one I don't see there.
[13:27:39] <PoppaVic> made me wonder: isn't the 1284p the same as a 644, but twice the flash?
[13:27:49] <Lambda_Aurigae> could be close.
[13:28:00] <Lambda_Aurigae> I suspect there might be some register position differences.
[13:29:40] <PoppaVic> https://github.com/DarkSector/AVR/blob/master/asm/include/m1284Pdef.inc
[13:30:02] <Lambda_Aurigae> good to know.
[13:30:07] <Lambda_Aurigae> just bookmarked the parent directory.
[13:31:04] <Lambda_Aurigae> and grabbed the entire git
[13:31:12] <PoppaVic> yeah, me too - and grabbed the file. I'll get the two and be able to test next week (there is a bench in that room, really)
[13:31:22] <Lambda_Aurigae> ok..back hanging steel sheets.
[13:33:00] <PoppaVic> heh
[13:40:17] <liwakura> Does anyone know that Vide where two thiefes break into a mansion that "magically" opens its doors itself and so on, while Steve Jobs on a Conference is holding his Phone and saying "Its perfectly secure"
[13:41:01] <liwakura> sorry, wrong channel
[13:42:19] <PoppaVic> um.. Sure.
[13:51:54] <Jartza> PoppaVic did you manage to get avra working?
[13:52:08] <Jartza> PoppaVic: octapentaveega is made with avra
[13:52:22] <PoppaVic> Jartza: found the files. The rest is for another day. I head to work here in a few
[13:52:41] <PoppaVic> avra looks like it should work fine
[13:54:13] <PoppaVic> Jartza: just finding those stupid m*def.inc files was driving me apeshit
[14:01:16] <Jartza> oh
[14:01:26] <Jartza> I just stole them from atmel studio
[14:01:42] <julius> if a mosfet draws a lot of current while switchig on, will it strain/destroy the pwm pin of a avr over time?
[14:02:16] <cehteh> depends, but also quite likely
[14:02:53] <cehteh> thats why you add this 30-100ohm resistor to the gate
[14:03:05] <cehteh> (logic level fet)
[14:03:19] <julius> yeah, i got that reverse psychology
[14:03:42] <julius> protect the driver by limiting the current by fixing voltage and resistance
[14:04:44] <julius> i also got some hints from #electronics and found some nice mosfets for logic level
[14:05:09] <cehteh> i used smaller fets w/o resistor . usually works, but that was only switching, not pwm
[14:05:32] <julius> whats the difference between "turn on delay time" and "turn on rise time" for this mosfet http://www.diodes.com/_files/datasheets/ZXMN4A06G.pdf ?
[14:05:43] <PoppaVic> Jartza: yes, hence last nights hell under win8 on the other partition - and my plans to backup the system, install new ubuntu to a flash, reinstall and nuke the entire drive: win8 has been an unmitigated nightmare.
[14:06:04] <julius> good choice PoppaVic
[14:06:10] <PoppaVic> oh, and the AS install bombed/locked at 3/4
[14:06:20] <julius> although ubuntu does a lot of updates, i like debian more
[14:07:24] <PoppaVic> debian updated in the long ago by erasing the drive and making it unbootable. I pass
[14:07:34] <cehteh> julius: why do you want pwm anyway? .. using a valve behind the pump and driving the pump with somewhat lower voltage (have you tried how it works at 5V?) should do the job much better
[14:08:06] <julius> basically i want to calculate its current draw I=Q/t im unsure what to use for t. usually i would use "switching speed" from the data sheet
[14:08:10] * PoppaVic pats his istick100w ;-)
[14:08:24] <julius> true, but i learned so much already
[14:11:40] <cehteh> eh anyone of you know how much drop the lm317 has w/o looking at the datasheet?
[14:12:14] <PoppaVic> s/of you //
[14:15:16] <cehteh> https://www.insidegadgets.com/wp-content/uploads/2012/06/sc_5.png
[14:15:20] <cehteh> google knows
[14:36:39] <Jartza> PoppaVic: well, Linux is fine for AVR development... still you could've gotten those files from atmel studio :)
[14:36:59] <Lambda_Aurigae> Jartza, one problem with that.
[14:37:14] <Lambda_Aurigae> atmel studio requires one actually boot up windows and install it.
[14:39:19] <theBear> meh, these days it's hard to find an install package obfuscated enough something like 7zip won't just open it as if it were a regular old fashioned zip or tar file to pull odd files and bits out
[14:40:09] <Lambda_Aurigae> yup. I never actually tried.
[14:40:46] <Lambda_Aurigae> mainly because I use avr-gcc and avr-as and don't need the files in question.
[14:41:11] <Jartza> Lambda_Aurigae: no it doesn't. the installer runs fine under wine :)
[14:41:22] <Lambda_Aurigae> Jartza, never got it to run here.
[14:41:30] <Lambda_Aurigae> granted, I haven't tested it in a while.
[14:41:35] <Jartza> then just grab the files and remove the studio :)
[14:41:38] <Lambda_Aurigae> I tried it when atmel studio first shipped.
[14:41:58] <Jartza> ahh. I tried with quite recent linux mint and atmel studio 7
[14:42:00] <Jartza> worked fine
[14:42:02] <Lambda_Aurigae> the installer kept horking hairballs.
[14:42:40] <Lambda_Aurigae> after second try I gave up. I guess wine has gotten better at handling it.
[14:43:23] <Jartza> yea, wine has gotten much better over the years
[14:44:11] <theBear> cheaper too ! oh <he said acting as if this were news to him> i see, you mean THAT kinda wine
[14:54:09] <Jartza> shiit
[14:54:10] <Jartza> https://www.youtube.com/watch?v=936m7FMS__c
[14:54:14] <Jartza> I'm still quite proud of that
[15:00:52] <julius> looks interresting
[15:02:27] <julius> PoppaVic, you dont really need atmel studio. you can use any editor to write your code, a Makefile and gcc to compile it with: "make"
[15:05:01] <theBear> heh, anyone ever said you look a bit like a younger sid vicious, or other old real rocknroll type dude ?
[15:08:55] <Jartza> who?
[15:12:24] <Jartza> theBear: ^
[15:22:36] <h4x0riz3d> --makefiles; ++codeblocks;
[16:00:21] <lorenzo> I spent half an hour investigating an i2c issue ..
[16:00:26] <lorenzo> turns out I forgot to << 1 the address :D
[16:00:35] <lorenzo> logic analyzer didn't point that out for some reason
[16:10:43] <julius> what a evil logic analyzer ;)
[16:28:35] <liwakura> i finally got my serial console on my atmega328p working
[16:28:53] <liwakura> sadly, the RX interrupt doesnt
[16:29:33] <liwakura> i set RXCIE0, but the interrupt (tried USART_RX_vect and USART_RXC0_vect) never seems to fire
[16:31:11] <liwakura> ah, what about including the interrupt.h -.-
[16:32:12] <liwakura> got it
[16:33:11] <liwakura> works perfectly.
[16:33:17] <liwakura> i also forgot sei()
[16:47:56] <Jartza> liwakura: naah, tiny problems ;)
[16:48:15] <liwakura> currently doing my own ringbuffer
[16:48:20] <liwakura> and no, i want to do an own
[16:51:45] <cehteh> everyone doing his own :D
[16:58:25] <cehteh> so position lights fpr copter .. guess they are bright enouh :D https://twitter.com/CehtehCt
[16:59:47] <cehteh> sanding the leds lenses down to get a wider angle
[17:10:16] <Jartza> well. ringbuffer is one of the easiest things to do :)
[17:11:54] <cehteh> depends
[17:13:49] <cehteh> on linux i did one using memory mapping to handle warp around instead checking length constantly
[17:14:35] <Jartza> make the size power of 2 and no prob :)
[17:15:04] <liwakura> Jartza: volatile ringbuffer with random read access :D
[17:16:08] <Jartza> what could possibly go wrong
[17:16:16] <liwakura> buffer overread?
[17:16:21] <liwakura> currently it works
[17:16:41] <liwakura> except the random read
[17:17:00] <liwakura> but i can enter F2 in serial terminal and get the hexdump of some weird sequence back
[17:18:19] <cehteh> Jartza: i did some implementation in my uart lib which coincidentally doesnt need the size a power of 2 and is even simpler
[18:49:23] <applepi> Hi all.. I'm having a weird issue where I'm passing a char array over to a function which accepts char*, but when I read the first character in the function which accepts it, it is not what I'm passing over.
[18:49:50] <cehteh> then you do something wrong
[18:50:00] <cehteh> string in progmem?
[18:52:05] <applepi> I'm using string_literals_in_flash, if that's what you mean
[18:52:58] <Lambda_Aurigae> might not pass correctly.
[18:52:59] <cehteh> yes
[18:53:12] <cehteh> not passing but reading then
[18:53:25] <applepi> I have a 'char i2cReadBuffer[4];', which as a simple test I'm just writing '\x01' and '\x04' to [0] and [3], then pass it over to my i2cRead function which takes (char * buffer)
[18:54:20] <applepi> and then in char * buffer i'm just checking [0] and [3] for \x01 and \x03 to make sure I got the right buffer, because it hasn't be working correctly
[18:54:27] <applepi> Er, sorry, in i2cRead
[18:55:03] <applepi> Er, also checking [3]=='\x04'
[18:55:19] <cehteh> where are there string_literals_in_flash?
[18:55:44] <applepi> it's a compiler arg
[18:56:36] <cehteh> what compiler is that?
[18:56:44] <applepi> IAR embedded
[18:56:54] <cehteh> anyway, thats not the case here, you do something else wrong
[18:57:14] <cehteh> i only use/know gcc for avr
[18:57:25] <applepi> I am tied to IAR embeeded unfortunately
[18:58:23] <cehteh> still thats not the problem here, you possibly do something else wrong
[18:58:32] <cehteh> try to isolate the error
[19:00:03] <applepi> I'm trying, but I can't seem to get more minimal than passing a pointer to a function.. I feel like it's going to be something to do with how IAR treats pointers and the high bit for flash/ram..
[19:00:26] <cehteh> 128k ram chip?
[19:00:34] <cehteh> (err are there any?)
[19:00:52] <cehteh> flash .. i meant
[19:01:15] <applepi> I've got to be missing something.. I have to use the string_literals_in_flash arg, and then for any function that takes a string literal it has to take (char __generic * foo)
[19:01:31] <applepi> atmega128rfa1
[19:01:36] <cehteh> strings in flash need some speciall massaging
[19:01:56] <cehteh> but you pass a ram buffer around here right?`
[19:03:10] <applepi> that is the goal as I need to be able to write to it
[19:03:19] <applepi> from my i2c results
[19:04:11] <cehteh> check your code, i bet there is some error somewhere
[19:04:49] <cehteh> alternatively try to port/compile the thing with gcc ... if the bug remains, its yours
[19:13:37] <applepi> i'm sure it's mine, it's just a matter of if it's my code or my compiler settings :)
[19:15:38] <applepi> i've dumbed the code down as much as i can, and this project is a little part of a very big project (this C code is actually being jumped to from little code VM)
[19:22:58] <cehteh> there are not many compiler options who generate broken code
[19:23:03] <cehteh> dunno about your compiler
[19:23:17] <cehteh> tiny-stack in gcc could do so
[19:23:30] <cehteh> -mint8 also
[19:37:38] <Jartza> night all
[21:11:50] <PoppaVic> Wine.. pfft.
[21:13:52] <Casper> Wine Is Not an Emulator, right? or you mean the disgusting liquid?
[21:14:19] <PoppaVic> someones solution to doze hours ago
[21:15:09] <PoppaVic> Oddly, virtual box decided neither image I had is runnable. And, I think this week I'll prepare to thermonuke win-friggin'-8 completely off the hdd.
[21:16:31] <heyfbiwhatsup> Hello!
[21:17:13] <Casper> most likelly a troll anyway
[21:21:28] <PoppaVic> well, aside from proving the doze partition is a complete waste of spacetime, all it did was mung my GPS and scare me when linux didn't want to boot. (so it's time to backup /home, get a list of packaged I require, and reinstall over the whole drive.
[21:22:16] <PoppaVic> heh.. and Rand McNally seems to think I must talk on the phone to fix the GPS - no I don't. Gimme' price and RMA, you can replace the battery and use yer own damned doze-machine to fix it.
[21:25:23] <Casper> is your linux ok?
[21:25:35] <Casper> and do you have space to backup your root?
[21:26:01] <Casper> mount -o bind is usefull, specially if you combine with tar :D
[21:26:20] <PoppaVic> well, it kept complaining that /media/system was damaged. But eventually booted past it. I think it's a partition-artifact that removing win8 and reinstalling will solve.