#qi-hardware IRC log for Sunday, 2014-08-31

shevekwpwrak (or anyone else), I've been looking at some documents about the KL26, but can't figure out how I am supposed to put a program into the flash.  Should I be using the debug interface for that?00:33
wpwrakshevek: yes, SWD is the way to do00:39
shevekOk, thanks.00:39
wpwrakhere is a very crude library that implements the protocol: https://gitorious.org/anelok/anelok/source/libswd00:40
shevekAnd you have software for doing that, I suppose?  I think I'll take a look at that when I have a board ready, or should I know things about it while desiging the pcb?00:40
wpwrakcrude = it often gets confused and aborts00:40
shevekI can live with that. :-)00:41
wpwrakso what i do is that i install a DFU loader as soon as possible, then enjoy the comfort of USB ;-)00:41
shevekI suppose the SWD pins can be used for other purposes during normal operation?00:42
wpwrakyou can also flash the critter with one of freescale's freedom boards. but careful: it seems that the chip on the board and the target have to be exactly matched00:42
wpwrake.g., i have a kl25 board that doesn't want to flash the kl2600:42
shevekAh, ok.00:42
wpwrak(of course, that was just more motivation for getting libswd done ;-)00:42
wpwrakand yes, you can do other things with the two SWD pins00:43
shevekIs the library only for ben with ubb, or is that just one option?00:44
wpwrakyou can replace ben.c with your own IO functions00:44
shevekObviously. :-)  But you haven't written anything else?00:45
shevekI don't mind using my Ben, but requiring people to have a Ben if they want to make a copy of the device seems too restrictive. ;-)00:46
wpwrake.g., the not-very-accurately-named libswd also has a protocol engine for the cc2543. that one, i drive either from ben or i embed it into the kl26 and tyrannize the cc2543 from here00:46
wpwrakno, i haven't written anything else. but it's nor exactly difficult :)00:46
wpwrakjust don't try to copy all the messy little twists of ben.c :)00:47
shevekAh, ok.  That makes sense.  I suppose the Y-box has those connections on the board, so it just works?00:47
wpwrak(not difficult) but depends on your environment, of course. as i said, there's nothing even remotely linux-specifc in there00:47
shevekHaha, I'll try. :-P00:47
wpwrakyes. and anelok now does, too (since i switched from at86rf23x to cc2543)00:48
shevekI'd probably want to offer people to do it from an arduino.00:48
wpwrak(nothing remotely linux) actually, checking, there is a bit .. calls to exit()00:49
wpwrakand a few printf diagnostics00:50
shevekI don't think Arduino supports exit(), but that's ok; there's nothing to exit to anyway, so I can just write void exit() { while(1) {} }. :-)00:50
wpwrakexit usually means that something went wrong and that you want to retry00:51
shevekIf I set up a watchdog, that's also what that exit function will do. ;-)00:51
wpwrakah yes, in ccdbg i have a report() callback. but been too lazy to do that on libswd00:52
wpwrakwell, if nobody else beats me to it, it'll have to make libswd just as clean as ccdbg when i make the test fixtures :)00:52
shevekWhat is the reason you went with freescale?  I read your post on the selection, but don't remember the arguments.  I know TI has some similar chips which seem to work well, too.  They call them Tiva.  Are there any objections against those, in particular with regards to freedom of toolchains, libraries, datasheets, etc?00:56
shevek(I'm looking for an replacement of Atmel avr chips that have a bit more power, and was thinking of the KL26 because you used it, so it must be good. ;-)  But maybe you chose it for arguments that don't apply to my case.)00:57
shevekOn the other hand, if you know of a SoC that can run Linux, that would be even better.  But I don't think those exist, because the amount of RAM you want isn't normally on the same chip.00:59
shevekHmm, that isn't exactly true, I suppose; without the RAM it's still called a SoC.  But I can't solder BGAs, which seems to be a problem for this.  And I'm not looking forward to hooking up RAM to a chip, although that may be easier now than it was 20 years ago (when I last looked at it). :-P01:01
wpwrakdidn't look too much into the tivas. they're more powerful. also considerably more expensive.01:01
shevekAh, ok.  That is an important consideration for me as well.01:02
wpwrakso i looked for sufficient feature set, proper documentation, packages i like, and then lowest cost01:02
wpwraki looked at kinetis, stm32, and tiva. tiva were the ones i found the least exciting. i've worked with stm32 before. alas, they tend to be bulkier than kinetis.01:03
shevekAh yes, that's an issue for Anelok, but it's not a problem for the board I'm making.01:03
wpwrak(soc with linux) the freescale i.mx family may have some things you may like. not rock-bottom cost but pretty open. alas, there's still no single-chip linux in sight. but give it a few years ...01:04
wpwrake.g., i.mx233 looks quite decent. and you don't have to go bga.01:11
shevekI'm looking at it, thanks. :-)01:13
DocScrutinizer05aren't these used on those oval board for ~12 bucks?01:13
wpwrakwhich on what ? :)01:14
shevekIt seems it is al BGA; where do you see one that isn't?01:18
wpwraklqfp-128, kid's play :)01:20
shevekYes, that shouldn't be a problem. :-)01:21
--- Mon Sep 1 201400:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!