Back
[01:11:49] <rue_shop3> theBear, what you doing for entertainment?
[02:08:40] <cehteh> is there some simple generic way to find out if code runs within an interrupt handler?
[02:19:38] <Xark> cehteh: I don't think so. Generally code will always "run", it just may not do what you want. :)
[02:20:43] <Xark> Race conditions are one of the most annoying bugs, as they can lay dormant indefinitely (and tend to be "Heisenbugs").
[02:21:02] <cehteh> i am thinking about some sensible way to handle errors from interrupts, having a global errno like var which get set when any error happens
[02:21:52] <cehteh> so far .. now i'd like to spilt that into 2 errnos one for sycnhronous code in the main loop and one for async code in interrupts
[02:22:29] <cehteh> but seems to me its really hard to figure out if running in 'some' interrupt
[02:22:39] <Xark> cehteh: Well, you can certainly have an "interrupt_errno" or similar.
[02:23:08] <Xark> cehteh: Well, you can have an "in interrupt" flag that is only set on entry and cleared on exit.
[02:23:08] <cehteh> yeah but if the interrupt calls library routines these routines need to displatch to the right errno
[02:23:30] <Xark> My advise would be don't do anything in an interrupt that could fail.
[02:23:48] <cehteh> thats really hard to do
[02:23:49] <Xark> Just have interrupt set a flag and have mainline service the job.
[02:24:32] <cehteh> i do the barely necessary .. for example serial RX would only push the byte received on a buffer
[02:24:48] <cehteh> but i need to notify when this buffer is full
[02:25:05] <cehteh> of course i could associate a 'overflow' flag to the buffer
[02:25:17] <cehteh> no generic errno then
[02:25:20] <Xark> cehteh: Just use a specific flag for "RX overrun", don't try to use an errno generic variable.
[02:25:38] <cehteh> yeah, guess thats the way
[02:25:40] <Xark> Also, what would you do on RX overrun?
[02:25:50] <cehteh> up to the user
[02:25:59] <cehteh> default is just die :)
[02:26:06] <Xark> Seems reasonable. :)
[02:26:20] <cehteh> but i'd like to have it logged then one may reconsider the rxbuffer size
[02:27:15] <cehteh> anyway .. that was just an example to show that its not always possible to avoid errors from interrupts
[02:29:26] <cehteh> guess i am just reserving a bit for every error that may happen
[02:29:32] <cehteh> instead global errno
[02:30:20] <Xark> cehteh: Is this like an AVR OS/framework or similar?
[02:30:29] <cehteh> yeah
[14:23:38] <NicoHood> okay i got something very weird happening:
[14:23:39] <NicoHood> Ive pluggin in an external HDD adapter into power (not usb). This is the only connection it has. If i touch the hdd (on the adapter) with my hand and then touch my music aplifier (not connected in any ways) i feel a voltage. I just measured 50V with my multimeter!!! if i measure the voltage the sound outputs noise. what the hell is happening here?
[14:28:01] <Casper> sadly normal
[14:28:35] <Casper> there is some anti-EMI capacitors between the main and the DC ground that let a tiny bit of current pass throught
[14:31:24] <julius> hi
[14:31:29] <Casper> o/
[14:40:48] <Lambda_Aurigae> bit of ground loop going on, eh?
[15:07:18] <Jartza> heh
[15:07:33] <Jartza> seems attiny5 handles 20Mhz too :)
[15:07:43] <Jartza> spec says 12Mhz
[15:08:25] <RikusW> don't complain if you get hw buggyness ;)
[15:08:40] <Jartza> nah, I'm not complaining at all, just fooling around
[15:08:40] <Jartza> :)
[15:09:25] <Jartza> attiny85 can do 40MHz :P
[15:09:30] <Lambda_Aurigae> biggest issue I've had with overclocking is the ADC.
[15:10:15] <Jartza> yeah
[15:10:22] <RikusW> Jartza: used HVSP yet ?
[15:10:28] <Jartza> not yet!
[15:10:48] <Jartza> been "tied up" with this thing called christmas :D
[15:11:10] <Jartza> you know, having some time with family and stuff :D
[15:11:20] <RikusW> At least you got your U2S before christmas :)
[15:11:36] <Jartza> yea, planning to have some tests with it soon
[15:11:41] <Jartza> maybe even tomorrow
[15:12:20] <RikusW> Just look at the dragon docs, or even the pinouts on my site to get it connected
[15:14:23] <Jartza> yeah
[15:14:28] <Jartza> at least Mac sees it ok
[15:18:42] <RikusW> did the red led flash once or twice when you plugged it in ?
[15:18:55] <Jartza> twice
[15:19:10] <RikusW> so it is in stk500 mode by default
[15:19:40] <RikusW> once is bootloader mode
[15:19:49] <Jartza> yeah, so I figured from the site
[15:19:50] <Jartza> https://i.imgur.com/NohABkl.png
[15:19:57] <Jartza> that's what mac system info says
[15:20:33] <Jartza> crw-rw-rw- 1 root wheel 17, 17 Dec 26 22:54 /dev/cu.usbmodemU21
[15:20:40] <Jartza> and that's the device created :
[15:20:41] <Jartza> :)
[15:21:14] <RikusW> nice :)
[15:21:50] <RikusW> I reused the U2S string because there was no more bytes left in the bootloader....
[15:22:06] <Jartza> yeah
[15:22:25] <Lambda_Aurigae> U2S?
[15:22:36] <Jartza> well, seems the device also answers
[15:22:44] <RikusW> https://sites.google.com/site/megau2s/
[15:23:05] <Jartza> says invalid signature when I have no chip connected
[15:23:23] <Jartza> I guess that's about normal
[15:23:26] <RikusW> Another reason to keep the "serial" number the same is to keep different U2S's on the same COM port in windows
[15:23:38] <RikusW> yep
[15:23:58] <RikusW> in bootloader it will give the mega32u2 sig and can even read the fuses
[15:24:35] <Lambda_Aurigae> but can't write the fuses I suspect?
[15:24:43] <RikusW> it can't
[15:25:02] <RikusW> it can write lockbits, but I intentionally didn't allow that
[15:25:37] <Jartza> RikusW: so that pinout adapter didn't fit the hvpp board?
[15:25:55] <RikusW> its for the xlat board
[15:26:28] <Jartza> mkay
[15:26:36] <RikusW> it can fit on the hvpp board for hv TPI, but will need a modified version of LUFA avrisp
[15:27:36] <Jartza> ahh yeah
[15:27:49] <Jartza> you mentioned that already, I just forgot it :9
[15:28:17] <RikusW> iirc in app mode there is a loopback code
[15:28:32] <RikusW> -a
[15:28:39] <Jartza> I'm just wondering, if I want to do HVSP now with attiny85, where to connect the chip
[15:28:44] <RikusW> will just echo everything
[15:28:56] <RikusW> soic or dip ?
[15:29:04] <Jartza> dip
[15:29:11] <RikusW> use a breadboard
[15:29:28] <Jartza> yea, but I mean, what pins from that HVPP board
[15:29:38] <Lambda_Aurigae> it's right in the datasheet dude!
[15:29:50] <RikusW> Look in the dragon docs, or on my site
[15:30:08] <RikusW> the HVPP pinout is identical to the dragon
[15:31:23] <Lambda_Aurigae> page 155, section 20.6, figure 20.3
[15:31:40] <Lambda_Aurigae> of the attiny85 datasheet
[15:31:43] <RikusW> Look on the stk500 page
[15:31:46] <Jartza> http://www.atmel.com/webdoc/avrdragon/avrdragon.hvsp_description.html
[15:31:47] <Jartza> this?
[15:32:58] <RikusW> avrdragon yes
[15:33:12] <Jartza> mmkay
[15:33:20] <RikusW> on the stk500 page is the full schematic of the hvpp board as well
[15:33:30] <RikusW> rather simple actually
[15:35:13] <RikusW> https://sites.google.com/site/megau2s/home/STK500
[15:35:19] <nikomo> Jartza: why do you want to do high voltage programming on the tiny anyways? I don't recall there being any benefit
[15:35:39] <Lambda_Aurigae> nikomo, big advantage...you can set the reset line to play i/o pin
[15:35:48] <nikomo> ooooooooooh right
[15:35:57] <nikomo> get another pin
[15:35:57] <Lambda_Aurigae> once you do that you have to have high voltage programming to get around it.
[15:35:59] <nikomo> out of it
[15:36:56] <Lambda_Aurigae> also, if you futz up the clock source fuses that's usually the best way to recover.
[15:37:24] <Lambda_Aurigae> is pretty much why I keep my dragon around still.
[15:38:11] <Lambda_Aurigae> although, I haven't used it in 4 years.
[15:38:38] <Jartza> nikomo: one more pin, yes.
[15:39:07] <nikomo> I've only got an usbtinyisp for programming AVR chips so not much of a possiblity for me heh, but I don't poke around with stuff that "small" generally, where I end up having to use the reset pin for IO
[15:39:16] <RikusW> Jartza: what kind of wire are you using to connect to the pinheaders ?
[15:39:22] <Jartza> shenanigans:~ jartza$ avrdude -c stk500hvsp -p attiny85 -P /dev/cu.usbmodemU21
[15:39:22] <Jartza> avrdude: AVR device initialized and ready to accept instructions
[15:39:22] <Jartza> Reading | ################################################## | 100% 0.00s
[15:39:22] <Jartza> avrdude: Device signature = 0x1e930b (probably t85)
[15:39:22] <Jartza> avrdude: safemode: Fuses OK (E:FF, H:DF, L:E2)
[15:39:24] <Jartza> yay
[15:39:39] <RikusW> in hvsp mode ?
[15:39:52] <Jartza> yes
[15:40:03] <Jartza> see command above :)
[15:40:16] <Jartza> that was _working_ attiny85 now
[15:40:28] <Jartza> next I'll try burning fuses for one that I've messed up
[15:40:42] <RikusW> in -t terminal mode you can poke around easily
[15:41:39] <RikusW> Great to know it works nicely on mac :)
[15:42:04] <Jartza> occasional timeouts, but still seems to work :o
[15:42:10] <Jartza> might be my crappy usb-hub, too
[15:42:27] <Jartza> http://pastie.org/10654375
[15:42:28] <Jartza> but yea!
[15:42:33] <RikusW> or it might be avrdude
[15:42:38] <Jartza> burned fuses nicely on one of the chips I had messed up
[15:42:50] <RikusW> nice :)
[15:42:51] <Jartza> can't remember if I disabled ISP or reset, but anyhow :)
[15:43:00] <Jartza> burned the factory default fuses back nicely
[15:44:24] <Jartza> I can now revive those 10-15 attinys I've messed up :D
[15:44:34] <RikusW> thats a lot :-D
[15:44:50] <RikusW> and build some more vga adapters ? :-D
[15:45:05] <Jartza> well yes... one reason was that I made stuff that needed reset pin...
[15:45:28] <Jartza> and then the firmware had a bug - just plug in next chip
[15:45:42] <Jartza> I used to have around 200 attinys
[15:46:12] <Jartza> vga adapter uses soic8 and I'm actually all out of soic8 versions
[15:46:27] <Jartza> used the last one for tagsu v7 proto
[15:47:17] <RikusW> I like soic8, its quite easy to solder, and not that hard to unsolder either
[15:48:11] <Jartza> RikusW: avrdude: stk500v2_ReceiveMessage(): timeout
[15:48:25] <Jartza> I get that 1-3 times after avrdude command, but after that everything works just fine
[15:48:26] <nikomo> RikusW: easy to work with, but it's also not massive like SOP
[15:49:48] <Jartza> anyway.. 11 attinys revived
[15:50:09] <RikusW> I developed the U2S on AS4 and tested it with AS5 and 6, and avrdude
[15:50:15] <Jartza> I know I still have few more Somewhere
[15:50:27] <nikomo> Jartza: They live, they die, they live again.
[15:50:43] <RikusW> You'll find them sometime while looking for something else ;)
[15:51:08] <Jartza> ahh, I actually remember, they are on single breadboard
[15:51:17] <Jartza> all the "messed up"
[15:51:18] <nikomo> I found my NRF24s whilst looking for voltage regs, and I found my voltage regs whilst looking for the NRF24s
[15:51:42] <Jartza> so if I already revived 11, there might be like 11 more
[15:53:16] <Jartza> anyhow, U2S seems to work and now I have more attinys to play with :)
[15:53:37] <RikusW> great to hear :)
[15:53:49] <RikusW> Jartza: the U2S fw is open source asm, its on the site
[15:53:58] <Jartza> cool
[15:54:37] <RikusW> So if you manage to kill the mega32u2, replace and flash
[15:54:54] <Jartza> hehe. I hope I won't need that
[15:55:00] <RikusW> me neither
[15:55:03] <Jartza> next I need to figure out the PDI
[15:55:32] <RikusW> for xmega ?
[15:55:36] <Jartza> yea
[15:55:50] <RikusW> you'll need the xlat board + pinout adapter
[15:56:07] <Jartza> yep
[15:56:11] <Jartza> figured out that much :)
[15:56:14] <RikusW> and build the LUFA AVRISP mkii, there is a U2S board type
[15:56:24] <RikusW> megal0maniac added that for me
[15:56:38] <Jartza> ahh, nice
[15:57:14] <RikusW> and do make sure the 5V jumper is removed
[15:57:31] <RikusW> (two pins right bottom on xlat board)
[15:58:09] <Jartza> mmkay
[15:58:11] <RikusW> the jumper underneath is for dW disable to work, its just a pullup on B0
[15:59:00] <RikusW> iirc I put the jumper out of the way on the 2x5 header
[15:59:01] <Jartza> I think I'll do that tomorrow as I need to put some more wires on breadboard :)
[15:59:19] <Jartza> yeah, there's one underneath
[16:00:15] <RikusW> try enabling dW on a tiny, just remember a 10k pullup on reset, and watch ISP magically work
[16:00:52] <RikusW> I don't think even Atmel's own programmers can do that :-P
[16:01:17] <Jartza> oh
[16:01:28] <Jartza> neat
[16:01:31] <Jartza> haven't used dW ever
[16:02:05] <RikusW> I send the temporary dW disable command, that is until powerdown
[16:02:16] <Jartza> neat
[16:02:26] <RikusW> just send 0x06 at the right baud to the chip
[16:02:57] <RikusW> releasing reset causes the avr to send 0x55 which is used to calibrate the baud
[19:37:24] <Jartza> oh. success.
[19:37:24] <Jartza> https://www.youtube.com/watch?v=wjjK1NnwrMs
[19:38:09] <cehteh> no vga yet?
[19:41:20] <Lambda_Aurigae> it's an attiny5....he should at least be getting 1200x600 hdmi out of it by now!
[19:41:29] <nikomo> how do you deploy those in a production environment? just order them preprogrammed from Atmel? because if you're using reset as IO, that means HVSP, which is problematic because 12V
[19:42:36] <Lambda_Aurigae> in system programmer or a clip programmer
[19:42:49] <Lambda_Aurigae> there are sockets of sorts you can drop them into.
[19:46:08] <cehteh> interesting thing .. HV programming was pull the reset to 12V .. but tiny5 has no reset :D guess i have to read the datasheet
[19:46:14] <cehteh> .. or better, never ever use these
[19:46:21] <Lambda_Aurigae> automated systems can pre-program them in circuit or before they get put on the board.
[19:47:14] <cehteh> yes
[19:47:29] <cehteh> does atmel offer to order them preprogrammed?
[19:48:05] <cehteh> ah pb3 is reset
[19:48:17] <nikomo> probably - almost everyone offers almost everything preprogrammed
[19:48:32] <nikomo> I bet you could call them and say you want 2500pcs preprogrammed and they'd bend over and do it
[19:48:40] <Jartza> cehteh: hehe :)
[19:48:53] <Jartza> no vga yet. just got the programming to work.
[19:49:24] <cehteh> maybe 25000 pcs .. but 2500 .. doubt so, or at least only for horrendous prices
[19:49:27] <Jartza> and yes, there is reset.
[19:49:43] <cehteh> i just read the datasheet
[19:49:54] <Lambda_Aurigae> for the right price you could get 1 preprogrammed.
[19:49:57] <Jartza> nikomo: well. at customer we use attiny5 in one product and that gets programmed like any other mcu
[19:50:19] <Jartza> chinese do program them at the assembly house
[19:50:27] <nikomo> makes sense
[19:50:43] <Jartza> even though they have reset disabled
[19:51:12] <cehteh> usually this small tinys are only used for very small/modest tasks .. in production stuff no one can afford to put as much development into it as Jartza does for the octapentaveega i guess
[19:52:04] <cehteh> fan controller on a pc mainboard or whatever .. just simple stuff
[19:52:38] <nikomo> they have some sort of internal RC oscillator available right? I bet someone with enough experience could write the code for blinking an LED with specific times, faster than someone could implement it with analog stuff
[19:52:53] <cehteh> yes
[19:53:04] <cehteh> all atmels have internal RC oscs
[19:53:15] <Lambda_Aurigae> all modern avr chips do.
[19:53:20] <Lambda_Aurigae> not all atmel chips.
[19:53:27] <Lambda_Aurigae> early at90s series didn't
[19:53:27] <cehteh> all avr i know
[19:53:42] <Lambda_Aurigae> atmega and attiny do.
[19:53:54] <cehteh> xmega too or?
[19:54:15] <Lambda_Aurigae> dunno bout those...I don't use xmega yet.
[19:57:25] <Lambda_Aurigae> or possibly ever.
[19:57:33] <Lambda_Aurigae> I kinda skipped over them to the pic32 series.
[19:57:46] <nikomo> sounds more like a downgrade
[19:57:57] <Lambda_Aurigae> not really.
[19:58:01] <Lambda_Aurigae> pic32 is a mips processor.
[19:58:06] <Lambda_Aurigae> with pic peripherals attached.
[19:58:17] <nikomo> anything PIC is a downgrade to me, have to work with their stupid compiler :P
[19:58:20] <Jartza> yes, xmega has internal oscillator too
[19:58:42] <Lambda_Aurigae> xc32 is just a modded gcc.
[19:58:47] <Lambda_Aurigae> just like avr-gcc
[19:58:57] <nikomo> 32MHz internal oscillator says ATxmega128A4U datasheet
[19:59:26] <nikomo> Lambda_Aurigae: I did a microcontroller course at school, the __delay macro had a max lenght to it under xc8, that's about where I stopped giving a shit about PIC
[19:59:40] <Lambda_Aurigae> yeah..pic 8bit sucks.
[19:59:46] <nikomo> the limit of course went away if you gave them money
[19:59:51] <Lambda_Aurigae> 16bit isn't much better.
[20:00:05] <nikomo> 32bit better then?
[20:00:12] <Lambda_Aurigae> xc32 is similar unless you pay for it or compile it yourself.
[20:00:42] <Lambda_Aurigae> xc32 is fully functional, even the free version..just missing the optimizations in the free version.
[20:00:51] <nikomo> it's one of those points though where I think, if I want 32bit, everyone else went ARM, and I don't really know better than they do, so I'd be risking "it", going for something else
[20:01:08] <nikomo> I follow the pack if I don't know better
[20:01:21] <Lambda_Aurigae> I like having a 28pin dip package for a 32bit processor with hardware usb.
[20:01:45] <Lambda_Aurigae> and the ability to execute code from flash or sram.
[20:01:54] <nikomo> that part's nice
[20:02:02] <nikomo> not a massive fan of DIP packages nowadays personally though
[20:02:13] <Lambda_Aurigae> I am,,,
[20:02:18] <nikomo> yay I can breadboard it... get an adapter...
[20:02:19] <Lambda_Aurigae> but they work best for what I do.
[20:02:54] <Lambda_Aurigae> I did recently get some pic32mz chips in tqfp 100 packages and today put them on adapter boards.
[20:03:07] <Lambda_Aurigae> the boards are square though and not breadboard friendly really.
[20:03:14] <nikomo> yeah, I can imagine
[20:03:18] <Xark> Did you hear that Microchip made a bid for Atmel (trying to bid more than Dialog offer)?
[20:03:28] <nikomo> yup, that was mentioned on the amp hour
[20:03:29] <Lambda_Aurigae> didn't hear that.
[20:03:43] <Xark> http://www.reuters.com/article/us-atmel-m-a-microchip-exclusive-idUSKBN0TY2P420151215
[20:03:53] <Lambda_Aurigae> I suspect that 8bit avr might have some issues soon.
[20:04:20] <nikomo> ARM is taking the race to the bottom in regards to prices, to the extreme, 8bit in general might be in problems
[20:04:31] <nikomo> but it'll still exist, I reckon
[20:04:47] <nikomo> I don't see those 6pin micros being 32bit ARM any time soon
[20:05:04] <Lambda_Aurigae> I don't see why not.
[20:05:18] <nikomo> They could, but not in a couple of years
[20:05:23] <nikomo> Decade from now maybe?
[20:05:26] <Lambda_Aurigae> naa.
[20:05:36] <Jartza> there are plenty of 8-pin arms already
[20:05:38] <Lambda_Aurigae> teeny tiny arm chips are easy.
[20:06:19] <nikomo> yeah, but is there going to be a market for them? you have to pay the ARM tax so it'll up the prices compared to AVR, PIC etc.
[20:07:06] <Lambda_Aurigae> 8pin 32bit arm for 39 cents
[20:07:22] <nikomo> got a part number? sounds interesting
[20:07:31] <Jartza> http://www.mouser.fi/Search/m_ProductDetail.aspx?Cypress-Semiconductor%2fCY8C4013SXI-400%2f&qs=sGAEpiMZZMuoKKEcg8mMKIhFBj6ODnhHr4B2LmGnsEZzxmuc%2fT2Ipg%3d%3d
[20:07:38] <Jartza> there's one
[20:07:52] <nikomo> oh right I think I actually saw a Cypress ARM chip mentioned on nicechips
[20:08:43] <Lambda_Aurigae> lpc812 for under 2 dollars from mouser
[20:08:44] <nikomo> exactly the one Jartza linked lol
[20:08:55] <nikomo> I need ARM experience
[20:09:08] <nikomo> I bought the MSP432 launchpad but never really bothered to do anything with it
[20:09:33] <nikomo> someone recommended some stm32 discovery thingie for me, might have to look into that
[20:09:40] <Jartza> http://www.mouser.fi/Search/m_ProductDetail.aspx?NXP-Semiconductors%2fLPC810M021FN8FP%2f&qs=sGAEpiMZZMsrb0xF%2fYczN%252bwThWVw5fK9iko0%2fnyAmxI%3d
[20:09:43] <Jartza> dip-8
[20:09:46] <Lambda_Aurigae> I have some of the stm32 boards.
[20:10:23] <Jartza> nikomo: forget discovery, nucleo is more modern
[20:10:30] <Jartza> still stm32
[20:10:53] <nikomo> programmed via a usb bootloader?
[20:10:59] <Jartza> dev boards about 10€ and they include st-link v2 programmer
[20:11:18] <nikomo> you have my interest
[20:11:19] <Jartza> for the easiest use, they show up as usb drive
[20:11:37] <Jartza> just drop the binary there and it'll get flashed
[20:11:53] <Jartza> I also made nucleo-to-breadboard -adapters
[20:12:08] <nikomo> I assume the 10€ dev boards are one of the Nucleo-32 boards?
[20:12:12] <Xark> http://www.cypress.com/documentation/development-kitsboards/cy8ckit-059-psoc-5lp-prototyping-kit-onboard-programmer-and looks interesting too (PSOC 5 + debugger for $10)
[20:13:17] <nikomo> welp, I know where all my money's going start of next month, again
[20:13:45] <Jartza> I like stm32
[20:14:22] <Jartza> though I have to say, avr is still my fav for simple tasks
[20:14:41] <Jartza> arm requires much more to get started
[20:15:08] <Jartza> simple stuff. like vga :D
[20:15:08] <nikomo> actually getting code onto the device, has been a bit difficult, for me
[20:15:21] <Jartza> with avr?
[20:15:25] <nikomo> the msp432 launchpad I got, if you use the horrible IDE that makes you want to kill yourself, you press run and it almost works
[20:15:39] <nikomo> but without the IDE, wtf are you supposed to do
[20:15:51] <nikomo> you need a build system, you need to figure out how the interact with the programmer...
[20:16:11] <Jartza> I don't know, I dob't use ide :p
[20:16:12] <nikomo> Jartza: I still haven't actually built anything for AVR with makefiles etc., from scratch, that I've made myself.
[20:16:16] <Jartza> being an old fart
[20:16:32] <Xark> nikomo: You mean the crappy Arduino fork IDE or crappy Eclipse fork? :)
[20:16:33] <Lambda_Aurigae> Jartza, you aren't an old fart.
[20:16:34] <nikomo> if someone gives me a ready project where I can just make and it gives a .bin, I'm ok with that, but I've never set that up from scratch
[20:16:50] <nikomo> Xark: crappy Eclipse fork, I tried the crappy Arduino fork but it didn't work
[20:17:05] <Jartza> Lambda_Aurigae: well, level 43 today ;)
[20:17:08] <Lambda_Aurigae> 48 here...probably one of the older in the channel.
[20:17:18] <Xark> nikomo: I never had trouble with Code Composer and 432 board. Programming debugging was easy IIRC..
[20:17:20] <Lambda_Aurigae> congrats on your level up.
[20:17:38] <Lambda_Aurigae> Xark, I never got that to work on linux
[20:17:40] <nikomo> Xark: try it on a low-end laptop from 2012.
[20:17:49] <nikomo> and you will know suffering
[20:18:10] <nikomo> that's the good thing about make+sublime text, it doesn't murder my laptop :P
[20:18:18] <Xark> Hehe. I only used it under Win7-64 on a decent machine.
[20:18:18] <Lambda_Aurigae> nikomo, most of my avr and pic programming is done on p-4 laptops with linux on them.
[20:18:43] <nikomo> Lambda_Aurigae: connected to mains, hopefully, p4 on a battery sounds fun
[20:18:51] <nikomo> I use Arch on my laptop
[20:18:57] <Lambda_Aurigae> although, it's all done command line with vim for an editor.
[20:19:10] <Lambda_Aurigae> nikomo, yeah...they are just workstations that can be easily moved.
[20:19:20] <Lambda_Aurigae> most of the batteries are good for 2 to 5 minutes max.
[20:19:21] <nikomo> I think Stallman has a faster machine than you, nowadays, actually
[20:19:29] <Jartza> Lambda_Aurigae: yea, thx.
[20:19:47] <Lambda_Aurigae> 1138
[20:20:11] <nikomo> Libreboot X200 has a Core2Duo P8400, and I think Stallman migrated to one of those because someone gave him one
[20:20:18] <nikomo> but I could be wrong
[20:20:32] <Jartza> nikomo: anyway, if you want avr quick'n'east, check atmel xplained -boards
[20:20:39] <Jartza> if arm, check nucleo
[20:20:55] <nikomo> Nucleo looks pretty good
[20:20:57] <Jartza> both boards include the programmer/debugger
[20:22:02] <Jartza> Lambda_Aurigae: btw. have you played with the latest octapentaveega?
[20:22:12] <Lambda_Aurigae> no chance yet.
[20:22:17] <Lambda_Aurigae> I have it downloaded though.
[20:22:40] <Lambda_Aurigae> worked on my sawdust pile mostly today.
[20:22:56] <Jartza> ahh
[20:23:06] <nikomo> st-link is supported under openocd so that sounds good to me. I've never used openocd but it seems to be what people use for programming their ARM chips often
[20:23:39] <Jartza> it's pretty good
[20:23:47] <Jartza> and also for debugging
[20:24:16] <Jartza> but you don't even need openocd
[20:24:21] <learath> I ended up using urjtag over openocd, but I don't remember why
[20:24:25] <cehteh> st-link is some rebranded jtag or?
[20:24:39] <nikomo> st-link is the programmer's name
[20:24:39] <Jartza> https://github.com/texane/stlink
[20:24:42] <nikomo> I think it uses SWD
[20:25:18] <cehteh> i have some st-link clone here, used it, it worked, didnt care what it uses underneath :D
[20:27:19] <Jartza> I have nucleo F030R8, F401RE and F411RE
[20:30:22] <Jartza> ohhh
[20:30:43] <Jartza> they also produce "nucleo 32" -miniboards
[20:30:45] <Jartza> niiice
[20:31:43] <Jartza> http://www.mouser.fi/Search/m_ProductDetail.aspx?STMicroelectronics%2fNUCLEO-F303K8%2f&qs=%2fha2pyFaduipjVzuvWOZebxnp0aJbi72%2f1fk9%2fP8moZq6L3ocL8%252baw%3d%3d
