Crack SimpleAvr's clock easter egg

[simpleavr 399]

What chips are those? AVRs? I've never seen chips piggybacked like that.

 

from my vusbtiny project

if you are using vusbtiny to flash 8 pin AVR devices, you can just press your target device on top of the programmer device. the programmer had been designed so that the programming pins matches w/ targets. there is one trick though, you will need to isolate pin 2 and 3 on the programmer mcu, as they are the USB D+ and D- pins connecting to the PC. i use a cut of scotch tape to achieve this, you can see it on the photos. show below is a tiny13v "riding" on the tiny45, ready to receive firmware.

 

there is even a "video", u'll have to find it yourself, can't give detail here, after all this is 430 land.

[bluehash 1,581]

there is even a "video", u'll have to find it yourself, can't give detail here, after all this is 430 land.

Oh no! Nothing like that. You are free to post videos. As long as its technical and in response to a question.

[cde 334]

Now if we could only get v-usb or similar ported over to the 430 valueline. 2k flash (1.4k used, so 600 left for code) and 128b ram, 12mhz clock are the only requirements from what I see...

[simpleavr 399]

it's do-able but will take some time, v-usb has timing critical sections in assembly, one would need to know the instructions (both avr and msp430) well to port them over.

 

may be a good time killing exercise during xmas holidays.

[jbremnant 17]

Dang, I just looked at your source code for this project.

GeekDoc's right. It's code-porn.

Don't mind if you see bits of your code in my future hack jobs.

[simpleavr 399]

thanks, and most of my code are "collected" snippets turn to my use though

 

but the led multiplexing is an original (as far as i know), not the multiplexing itself, but the way macros are used to resolve the port values at compile time, at run-time i don't need to map / translate the port bits (led segments) from a digit for output, i just output to the port right away. it uses more program / data memory (using table to "remember" port values and stay values for each digit) but it's so fast that u can run the multiplexing on a 32khz clock source w/o clicker.

 

actually i was trying to run this at very low clock and created this mechanism, eventually the lack of dimmer control (at low clock speed) made me abandon it and now i think the rtc clock runs at 1Mhz divided by 2 (500khz), sort of a compromise.

 

if any part of the code can do good in your projects, do use them, no need to credit me, as i said, i just "collected" them from here and there.

[KentJonathan 0]

Hi, good day everyone,

 

Can I ask a question? that is not quite related to the topics.. haha..

 

Where to locate the .elf file. I know that when we right click the workspace and select properties, we can select the output format to be legacy COFF or eabi(ELF). But I can't find the .elf file around. And I saw the author posting .elf file in his website, maybe I can ask around. =)

 

Warm Regards,

Kent

[simpleavr 399]

 

Where to locate the .elf file. I know that when we right click the workspace and select properties, we can select the output format to be legacy COFF or eabi(ELF). But I can't find the .elf file around. And I saw the author posting .elf file in his website, maybe I can ask around. =)

 

 

 

Hi Kent,

 

For this clock project I used mspgcc to build and the default product is .elf files. Are you using CCS / IAR or energia? I sometimes uses CCS but never take a close look at the output format as long as I can get my firmware downloaded to my LP.

[KentJonathan 0]

I am using CCS v5.5 =). We select the output file, but I just cant find it. :3

I tried searching the solution online but doesn't have a clear answer. Actually, I was planning to use the output file to do some simulation in Proteus ISIS. 

Hope you can help. =) 

[simpleavr 399]

Well, I tried CCS V5.4 w/ a blinky.c specifying elf format.

 

I can see that it's under by ~/blinky/debug/ as blink.out

 

1st line is like so.... appears to be elf format.

 

^?ELF^A^A^A^@^@^@^@^@^@^@^@^@^B^@i^@^A^@^@^@^