Back
[03:49:27] <Anaphaxeton> what do you think of the following combination?
[03:50:13] <Anaphaxeton> ATECC108-SSHDA-B-ND and ATMEGA88A-AU-ND
[04:15:38] <Anaphaxeton> this sucks
[04:15:46] <Anaphaxeton> i have to find a european vendor
[04:16:05] <Anaphaxeton> mouser italy doesnt sell the crypto cheap in small amounts
[06:10:39] <megal0maniac_afk> Anaphaxeton: What about xmega?
[06:17:04] <megal0maniac_afk> Something like the ATXMEGA16A4U-AURCT-ND
[06:20:06] <megal0maniac_afk> Faster CPU, double the flash, 7 SPI channels, 5 UARTS, 2 TWI channels, higher resolution ADC plus a DAC, and cheaper and smaller than your combination
[06:20:43] <megal0maniac_afk> Oh and obviously built in crypto. Which was kind of the point of the suggestion :)
[06:21:24] <megal0maniac_afk> And it comes in a USB version if you desire. I think I'm done
[06:22:51] <Anaphaxeton> βθιλτ ιν ψρυπτο?
[06:22:59] <Anaphaxeton> built in crypto?
[06:23:05] <Anaphaxeton> that's nice
[06:23:40] <Anaphaxeton> i chose a non xmega because the programmer i currently have doesnt support them and i wouldnt like to invest in a better programmer
[06:23:45] <Anaphaxeton> but let me check the chip
[06:24:02] <megal0maniac_afk> Oh whoops. The one I linked to IS the USB version
[06:25:39] <Fornaxian> http://tom-itx.dyndns.org:81/~webpage/commerce/commerce_index.php nice little programmer that does xmega as well as atmega and attiny...and sold by someone in here.
[06:26:26] <megal0maniac_afk> If you get the USB version then you can use the bootloader. No programmer needed. Otherwise what Fornaxian said. Worthwhile investment
[06:26:46] <Fornaxian> yeah. usb bootloader is nice too.
[06:27:25] <Fornaxian> I spend more going out to eat once a week with the wife than I did on that programmer.
[06:27:35] <Anaphaxeton> it seams those chips offer block cyphers only
[06:27:57] <Anaphaxeton> the crypto chip i was thinking about does asymmetric, hash+hmac
[06:28:08] <Anaphaxeton> i need to make an authentication device
[06:32:17] <Anaphaxeton> i checked 32bit avrs too
[06:32:29] <Anaphaxeton> max they can do is AES256
[06:32:45] <Anaphaxeton> not bad, but also not useful in this case
[06:33:24] <Roklobsta> haha aes256 can be hacked in 3ns by You Know Who
[06:34:04] <Roklobsta> must have hardware Blowfish4096 to be safe now
[06:34:30] <megal0maniac_afk> You Know Who?
[06:34:40] <Fornaxian> our lusterlus government.
[06:34:43] <Fornaxian> lusterless
[06:35:08] <megal0maniac_afk> Boring :)
[06:35:16] <Fornaxian> Neophite Social Anemics.
[06:35:29] <megal0maniac_afk> I wonder if our government knows about crypto...
[06:35:35] <Anaphaxeton> if there where blowfish4096...
[06:35:40] <Anaphaxeton> how about serpent?
[06:35:49] <megal0maniac_afk> ROT13?
[06:36:05] <Fornaxian> bah...send everything in plaintext so they start digging for the hidden meaning.
[06:36:18] <Roklobsta> The goose flies at night.
[06:36:22] <megal0maniac_afk> That's my intention :)
[06:36:30] <Anaphaxeton> youtube video steganography!
[06:37:36] <Fornaxian> I saw a proposal on irc a couple of years back about dual-storage encryption system. Encrypted harddrive with two sets of data intertwined. What you see when you decrypt depends on what password you give.
[06:37:58] <Roklobsta> given what's been relvealed doing stuff like firewalls and antivirus is mostly security theatre.
[06:38:02] <Fornaxian> so, if they want your password for your computer, give them the one that decrypts the videos of my little pony.
[06:39:51] <megal0maniac_afk> Do xmegas come with the bootloader preloaded?
[06:41:27] <Anaphaxeton> we want to install an alarm system in our home
[06:41:34] <Anaphaxeton> hear this feature
[06:41:40] <Anaphaxeton> say my pin is 1234
[06:41:59] <Anaphaxeton> i choose 5 as a security prefix
[06:42:26] <megal0maniac_afk> Don't tell us!
[06:42:44] <Anaphaxeton> the burglar puts a pistol on my head and tells me to open the door and disactivate the alarm
[06:42:55] <Anaphaxeton> i pres 51234
[06:43:07] <Anaphaxeton> the alsrm disarms
[06:43:14] <Anaphaxeton> the burlgar is happy
[06:43:18] <Fornaxian> the way they did it in the military was to add 10 to your code....regular code gave you access...add 10 and it gave access but activated silent alarm.
[06:43:28] <Anaphaxeton> exactly
[06:43:29] <megal0maniac_afk> The burglar is never happy
[06:43:30] <Fornaxian> both ways, 4 digit code.
[06:43:31] <Anaphaxeton> silent alarm
[06:43:54] <Fornaxian> but, the keypads were scramble pads.
[06:44:07] <Anaphaxeton> brb food
[06:44:07] <Fornaxian> all the keys were little displays. and it would rearrange the numbers on the pad each time it was used.
[06:44:20] <Fornaxian> so someone couldn't remember your pattern.
[06:44:31] <Anaphaxeton> cool feature
[06:44:53] <Anaphaxeton> if somebody could tell me anothe mcu to pare to the atmel crypto chip?
[06:44:58] <Fornaxian> many people had problem remembering their codes though. people tend to memorize patterns rather than codes.
[06:45:03] <Anaphaxeton> pair*
[06:45:27] <Fornaxian> no clue. I don't do crypto on anything less than an arm or x86.
[06:45:40] <Fornaxian> and, in that, I just use it.
[06:46:11] <Fornaxian> no clue why you need crypto for a home alarm though.
[06:46:27] <megal0maniac_afk> Lockbits should suffice, no?
[06:49:58] <Fornaxian> your keypad should never send an unlock or disable command anyhow...it should send just the keypresses to a physically remote and secure device that interprets them.
[06:50:49] <Roklobsta> which has unsecure wires coming back to the door snib
[06:51:04] <Fornaxian> yeah...so that should be armored.
[06:54:43] <Fornaxian> well, off to work. laters.
[07:13:05] <Anaphaxeton> the crypto chip has nothing to do with the home alarm
[07:13:34] <Anaphaxeton> i just mentioned the alarm for the silent alarm feature, which made me quite an impression
[07:13:49] <Anaphaxeton> i want to make a module for authentication
[07:14:10] <Anaphaxeton> that crypto chip does exactly what i need
[07:14:22] <Anaphaxeton> but the mcu still remains a question
[07:14:33] <Anaphaxeton> bbl, nap
[10:28:41] <bss36504> My understanding of ASF is that it provides a nice API for you to get CPU peripherals working without having to write all the code from scratch. I have a custom board with a mega164 on it, and I'd like to utilize ASF. If I create a standard C/C++ project then try and add stuff via the ASF Wizard, it yells at me for not using an example project. I know I can use a "user-board" template, but I only see one megaAVR user board project
[10:28:41] <bss36504> template, and that is for the mega256RFR2. I've gone ahead and created the project using that template, and now when I go to the ASF Wizard, there are tons of options. My question is: What do I need to put in board definition file to make the added ASF modules work so that when I change the target part to a mega164 everything works well? Does Atmel actually have a doc on making custom ASF projects (all I have is:
[10:28:41] <bss36504> http://www.atmel.com/Images/doc32198.pdf)?
[11:33:38] <Casper> bss36504: just be carefull, those stuff may add unneeded code size or ram usage
[11:33:46] <Casper> which is very low on avr
[11:34:02] <Casper> but not an issue on pc, so just check that up
[11:55:42] <bss36504> Casper: Well I got it to compile for the 164PA finally. Now I just dont have options for useful peripherals (like USART and SPI) in ASF Wizard. Is there a way to add or enable them?
[13:04:51] <DLPeterson> are there any gentoo users out there that are familiar with setting up the avr toolchain using crossdev?
[13:38:15] <Casper> DLPeterson: I did it in the past, I forgot how I did it :D
[13:38:27] <DLPeterson> :)
[13:38:39] <DLPeterson> are you currently using gentoo?
[13:55:42] <Casper> OS: Gentoo | Up: 77 days, 3:51 Record: 195 days, 18:55:02 | CPU: Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz (load: 0.34, 0.28, 0.24) | Gfx: NVIDIA Corporation GT200b [GeForce GTX 275] (rev a1) Res: 1920x1080 | Ram: 3762/5952MB | Hdd: /mnt/data 10177GB/15001GB (68%), /home 24GB/85GB (30%), /mnt/floppy 10GB/33GB (31%)
[13:55:44] <Casper> :D
[13:55:57] <Casper> DLPeterson: no, I am not :D hehe
[13:56:56] <DLPeterson> Casper, just curious, what command did you use to generate that?
[14:04:24] <Casper> commands
[14:04:30] <Casper> it's a small bash script that I did
[14:04:47] <Casper> that extract the info here and there, and glue them together
[14:05:48] <Casper> basically, sed, grep, uprecords, /proc/cpuinfo, lspci, xres, free, df
[14:06:32] <Casper> I think also head and tail
[14:17:46] * abcminiuser yawn
[14:19:24] * Casper throws a lemon in abcminiuser's yawning mouth
[14:19:29] <abcminiuser> Aww
[14:19:35] <abcminiuser> I've had a long day
[14:19:49] <Casper> and me some weird issues
[14:20:03] <Casper> this gateway computer.... the recovery is broken
[14:20:29] <Casper> this pc bsod with an hardware fault message when the hardware is fine
[14:20:58] <Casper> that other pc is supposed to be infected with the ukash virus and locked... the virus is gone, but I see some rootkit
[14:22:42] <Casper> and that store still hasn'T sent me the quote... grrrr
[14:23:58] <abcminiuser> Try dealing with a support case where you have one day to fix a bootloader that's going into 600K parts
[15:23:15] <Casper> abcminiuser: easy... just don't make error first, so you won't have to fix the error :D
[15:23:31] <abcminiuser> Hey, wasn't my fault
[15:23:40] <abcminiuser> I was on failure analysis
[15:24:07] <Casper> what do you think of rigol oscope?
[15:24:36] <abcminiuser> Mines worked well
[15:24:40] <abcminiuser> Old DS1052E
[15:25:37] <MannImMond> 'upgraded' to 100MHz?
[15:26:00] <Casper> I'm thinking to get the ds1104z-s
[15:26:09] <abcminiuser> Nah not yet
[15:26:12] <abcminiuser> Will when I need it
[15:26:19] <Casper> but I'm worried about the combo...
[15:26:56] <Casper> the -s have a siggen built in
[15:29:52] <abcminiuser> I prefer discrete tools where possible
[15:30:02] <abcminiuser> Combo tools usually suck at on, the other, or both
[15:31:40] <w|zzy> I agree with abcminiuser
[15:31:41] <MannImMond> Ordering a new oszi for the office (if it gets approved) in the next couple of days. That will definitely help
[15:31:57] <w|zzy> Also.. filling your desk up with cool looking test gear is awesome :p
[15:32:25] <abcminiuser> "This is the machine that goes 'ping'"
[15:32:34] <w|zzy> yes!
[15:33:01] <w|zzy> I am very tempted to make a desk stand for my scope
[15:35:40] <Casper> that is what I'm worried about the combo
[15:35:54] <Casper> but cheaper than buying 2 units, and save space
[15:36:05] <Casper> both being interresting
[16:41:06] <Anaphaxeton> what do you think about ATmega328P for a begginer?
[16:41:24] <Anaphaxeton> seems to have less constraints, and ok features
[16:43:25] <codyps> Anaphaxeton: compared to?
[16:44:32] <Anaphaxeton> atmega88 that i had mentioned earlier
[16:45:50] <Anaphaxeton> much ealrier actually
[16:46:21] <Anaphaxeton> i wanted to pair it to a ATECC108
[16:46:33] <Anaphaxeton> but it seems nobody in europe has it
[16:49:44] <Anaphaxeton> "Optional Boot Code Section with Independent Lock Bits," what does this mean
[16:49:52] <Anaphaxeton> ?
[17:05:32] <Casper> Anaphaxeton: I sugest the biggest avr for starters
[17:06:43] <Casper> the only issue is that the documentation can discourage them
[17:06:43] <Anaphaxeton> isnt 328 big enough?
[17:06:44] <Casper> yes it's big enought
[17:06:45] <Anaphaxeton> good
[17:06:47] <Casper> but the 600+ pages datasheet can be frightening :D
[17:06:48] <Anaphaxeton> i always thought that i will start with x64 asm...
[17:07:00] <Anaphaxeton> but i guess this will be even more fun
[17:07:17] <Anaphaxeton> shouldnt coding in C make things a lot easier?
[17:07:38] <Anaphaxeton> and make those 600 pages not so necessary?
[17:08:40] <OndraSter_> I have never read the datasheets from beginning to the end
[17:08:47] <OndraSter_> always only the chapters about peripherals that I used
[17:09:40] <Anaphaxeton> i havent seen those datasheets so i cannot tell
[17:10:04] <Anaphaxeton> i hope thy dont have many diagrams because my ebook reader sucks with them
[17:10:29] <OndraSter_> XMEGA datasheets have diagrams
[17:10:32] <OndraSter_> no idea how mega
[18:34:26] <Fornaxian> mega datasheets have diagrams too Anaphaxeton
[18:34:39] <Fornaxian> and lots of info.
[18:43:10] <Anaphaxeton> goodnight folks
[20:12:28] <darsie> Do I need a certain rise/fall time to wake from standby via a PCINT pin change?
[20:13:22] <Tom_itx> any realterm users here?
[20:13:35] <Tom_itx> wanna figure out if i can save a setup for it
[20:22:30] <Casper> darsie: afaik, only a change...
[20:22:39] <darsie> thx
[20:43:29] <darsie> damit, I mixed up Vdd and Vss on an attiny45
[20:44:13] <darsie> I should sleep
[20:47:51] <DLPeterson> does anybody understand the -MD and -MP compiler/preprocessor flags?
[20:48:02] <darsie> it's still working \o/
[20:48:07] <darsie> I wonder how they do that.
[20:48:59] <DLPeterson> I'm working on a project that uses them and the project compiles both with and without the flags but the output code size is about 3k different
[21:45:15] <Casper> rue_house: ya there?
[21:55:08] <rue_shop2> no
[21:55:15] <rue_shop2> I'm over there
[22:40:30] <Casper> hey rue_shop2 ! do you know what are the fees from importing oscope from usa to canada? standard 5-15$ fees + tax + ecofees?
[23:18:52] <rue_house> depends
[23:19:00] <rue_house> if its shipped it can be as low as 0
[23:19:07] <rue_house> if you drive it, its the tax
[23:25:33] <Casper> will be shipped... trying to find somewhere that answer the quotation request!
[23:25:51] <Casper> mind you, it seems like ALL the place have a big delay or do not reply
[23:25:52] <DLPeterson> j
[23:32:46] <learath> uh, really dumb question: is the eeprom_read_byte function really limited to addresses under 256?
[23:37:15] <Casper> I somewhat doubt so
[23:37:59] <learath> so do i. but the function definition in the manual is pretty clear
[23:38:03] <learath> uint8_t eeprom_read_byte (const uint8_t *__p) __ATTR_PURE__
[23:38:29] <learath> and when I pass a uint16_t as the address I get Warning 1 passing argument 1 of '__eerd_byte_m328p' makes pointer from integer without a cast [enabled by default] C:\Users\nick\Documents\Atmel Studio\6.1\spi_shortcut\spi_shortcut\main.c 567 3 spi_shortcut
[23:38:35] <learath> ... that's really ugly.
[23:38:40] <learath> sorry
[23:39:04] <learath> I guess I have to use eeprom_read_block, which will work
[23:39:18] <Casper> o.O weird you're right, 8 bits... weird
[23:45:38] <learath> Are you familiar with eeprom_read_block? I'm passing a uint16_t as the second argument, any clue if it'll work?