Back
[04:54:26] <RikusW> mind reading ->
http://www.sciencedaily.com/releases/2013/08/130819141641.htm
[04:59:17] <taken90> Hey everyone, I was wonderind what happens when I write with ST to the (memory mapped) Register which is used by ST and is incremented afterwards. Is the content the byte to be loaded or the incremented address?
[05:02:02] <RikusW> Don't do that ....
[05:02:35] <RikusW> iirc the datasheet says undefined
[05:03:38] <taken90> @RikusW Thanks for the response, could your reference the datasheet, I couldn't find that statement.
[05:06:22] <taken90> @RikusW sorry I didn't know what iirc ment
[05:06:39] <RikusW> heh
[05:09:03] <RikusW> The result of these combinations is undefined:
[05:09:03] <RikusW> ST Y+, r28
[05:09:03] <RikusW> ST Y+, r29
[05:09:03] <RikusW> ST -Y, r28
[05:09:03] <RikusW> ST -Y, r29
[05:09:45] <RikusW> www.atmel.com/Images/doc0856.pdf
[05:10:57] <Roklobsta|2> don't do them. the universe will end.
[05:13:44] <taken90> @RikusW Well, now I see it too, I must have been blind ... thank you very much guys!
[05:21:13] <RikusW> http://www.sciencedaily.com/releases/2013/03/130315074613.htm It's clear that raeders can dael wtih wodrs in wihch not all teh leettrs aer in thier corerct psotiions.
[05:36:07] <twnqx> RikusW: oooold fact, it's most important that the first and last letters are correct
[11:18:08] <masterq> how do i move the stack to the end of the external memory?
[11:20:29] <masterq> ok, forgot to say, by telling the linker its position
[11:33:26] <RikusW> its easy in asm
[11:33:36] <RikusW> in C you can always change SPH and SPL
[11:33:52] <RikusW> inside main() and just never return
[11:34:05] <RikusW> masterq:
[11:34:36] <masterq> is there a way to tell the linker where the stack pointer has to be placed?
[11:38:08] <masterq> i write in c, and so long as i know the stack pointer will be automatically initiated. I see that it would be possible to change it's position in runtime.
[11:38:55] <masterq> but if possible wan't it to be initiated the right place...
[11:40:11] <masterq> even though thanks RikusW
[11:40:48] <abcminiuser> You should be able to override it with a linker flag
[11:41:44] <abcminiuser> Hrm no, seems the default linker scripts use the init2 section to do it
[11:41:48] <abcminiuser> So it's baked into the CRT
[11:44:15] <twnqx> i think there is...
[11:44:29] <twnqx> or was that heap only
[11:48:04] <masterq> maybe it will just be set to whatever RAMEND is set to, but RAMEND is part of the atmel io includes. And i'm not sure it's a good idear the change this...
[11:48:34] <masterq> heap is no problem: -defsym=__heap_end=0x87FFFF -Wl,--defsym=__heap_start=0x800000
[11:49:03] <masterq> sry: copy not complete: -Wl,--defsym=__heap_end=0x87FFFF -Wl,--defsym=__heap_start=0x800000
[11:49:04] <masterq> ...
[11:55:41] * RikusW is in blissful ignorance of those commandline parameters :-P
[12:05:13] <mitsakos> hello has anybody ever used an 7.0" TFT LCD Module, Resolution 800x480, SSD1963 ?
[12:08:35] <masterq> there is something called XRAMEND, maybe this is usefull
[12:08:47] <twnqx> not really
[12:08:49] <Joggl> mitsakos, i am sure anybody did!
[12:09:06] <mitsakos> anybody?
[12:09:22] <mitsakos> are you kidding me?
[12:09:32] <Joggl> no, never.
[12:12:49] <mitsakos> as yo can imagine i'm trying to make that display work using an AVR atmega168
[12:13:58] <tekzilla> hey, do all the mcus of the same dip package size share the same programming pin layout ?
[12:16:22] <The_Coolest> Joggl lol
[12:16:46] <The_Coolest> tekzilla see datasheet
[12:17:04] <tekzilla> yeah sorry :/ i'm a lazy bastard
[12:17:15] <The_Coolest> the atmega8/168/328 do
[12:17:54] <tekzilla> ok cool thanks, i'll have to dig
[12:20:33] <mitsakos> so anybode who has succesfully interfaced an TFT LCD Module, Resolution 800x480 on an avr?
[12:24:17] <soul-d> what type of interface speed how many bit colors etc etc
[12:24:20] <soul-d> http://tinyvga.com/vga-timing
[12:34:39] <mitsakos> here
[12:34:40] <mitsakos> http://www.ebay.com/itm/7-inch-TFT-LCD-module-800x480-SSD1963-w-touchpad-PWM-arduino-AVR-STM32-ARM-/121017488870
[12:35:43] <hackman> hey guys, what software can I use to draw schematics ?
[12:35:50] <Joggl> eagle.
[12:36:01] <inkjetunito> another vote for eagle
[12:36:03] <hackman> on Linux :)
[12:36:09] <inkjetunito> hackman: still eagle
[12:36:18] <Joggl> yes, eagle.
[12:36:37] <theBear> we told you this days ago, don't you believe us ?
[12:38:20] <mitsakos> https://github.com/candrian/SSD1963_Driver/blob/master/SSD1963/ssd1963.c here is the library i have "write"
[12:38:31] <soul-d> well it's crealy marked for the arm 32 bit
[12:38:43] <soul-d> if you realy have to use avr it seems you need extra pre chips
[12:38:56] <soul-d> otherwise looks so far to mee it's just wriiting to some flash mem
[12:39:05] <soul-d> static image
[12:42:42] * twnqx votes for eagle, too
[12:44:07] <soul-d> anyhow mitsakos what avr is it 32 bit ? unless your running min 26.4 to 46.8 your not gonna do much with the screen
[12:44:15] <soul-d> CLK Frequency fclk 26.4 33.3 46.8 MHz
[12:44:27] <soul-d> it has to be exactly one of those frequency's
[12:44:39] <soul-d> DCLK*
[12:46:13] <mitsakos> DCLK ?
[12:46:17] <mitsakos> what do you mean? which clock is this?
[12:46:19] <mitsakos> data clock?
[12:47:17] <soul-d> data clock for the color lines
[12:47:40] <mitsakos> yes but this on LCD's board
[12:47:54] <mitsakos> it doesn't has to do with the mcu
[12:48:06] <mitsakos> you are writing and seding commands to the LCD asynchronous
[12:49:07] <soul-d> can't find anything about serial interface but still where are you gonna provide that data from with an avr ?
[12:49:38] <mitsakos> soul-d i want to make a simple display. i'll use it to make a dashboard displaying different signals
[12:49:51] <mitsakos> i'm not going to process graphics
[12:50:06] <mitsakos> just light some pixels
[12:50:24] <mitsakos> and draw 2-d graphics which will be specific like an image
[12:50:37] <soul-d> well is DCLK* on and running ? usaly it's mandatory to speak to serial part of lcd's
[12:50:55] <mitsakos> there is no DCLK
[12:51:01] <mitsakos> the lcd is parallel
[12:51:11] <soul-d> well even with some pixels an avr willl have a hard time
[12:51:22] <soul-d> if lcd has some static mem to display
[12:51:40] <mitsakos> hm..
[12:51:42] <soul-d> like pointing to mem adress it's possible to show somthing maybe even do somthing
[12:51:44] <soul-d> but not much
[12:51:52] <soul-d> your talking about 45 MB
[12:51:56] <soul-d> for 1 frame
[12:51:59] <soul-d> in 1 color
[12:53:03] <soul-d> thats why if you read ebay site
[12:53:12] <soul-d> that if you want to display somthing like text
[12:53:16] <soul-d> to get a difrent version
[12:54:07] <mitsakos> hmm yes
[12:54:14] <soul-d> and again what avr and avr 32 might do somthing
[12:54:20] <soul-d> avr8 just don't bother
[12:54:24] <mitsakos> so it would be better to use a 32-bit arm right?
[12:55:26] <hackman> Joggl, inkjetunito thank you very much for the suggestion of eagle. I see I have to learn quite a bit there :)
[12:55:27] <inkjetunito> mitsakos: how many pixels do you need?
[12:55:39] <mitsakos> i haven't count them
[12:57:20] <soul-d> well even arm will mostly be busy doing the screen
[12:57:42] <mitsakos> xm..
[12:58:46] <soul-d> soo if that board has 3x 8 bit inputs for color
[12:59:13] <soul-d> almost sure you will need a nice clpd or fpga to handle your frames for you with a bit of mem
[13:00:03] <mitsakos> hm..
[13:01:13] <mitsakos> so i'll try stm32f4 discovery i already have but i have never used it before
[13:01:21] <mitsakos> and i'm really new in ARM
[13:01:35] <soul-d> im lazy got a 4,3" with typical chinese datasheet non standard stuff and a fpga havent gotten around to it supposedly easy just set it in rgb mode send some data :)
[13:01:58] <soul-d> but ofcourse only some crapy verilog code wich makes no sense whatsoever still on the todo list
[13:04:06] <mitsakos> as i can see here
http://www.youtube.com/watch?v=srvM57YTp_U
[13:04:19] <mitsakos> stm32f4
[13:04:23] <mitsakos> can handle it easy
[13:06:58] <soul-d> sure probrably can do it on 1 port ive no arm expierence but that would but quick google shows it runs 100mhz+ so yeah thats much better choice then avr8
[14:36:32] <masterq> will variables in the external memory be initiated in the same way every other variable is beeing initiated
[14:37:35] <masterq> because it feels like there are just shit in my memory directly after booting...?
[14:40:32] <OndraSter> external memory?
[14:42:50] <masterq> yes external sram
[14:49:26] <OndraSter> on which device?
[14:49:45] <masterq> xmega128a1u
[14:50:17] <masterq> running in 4port ebi
[15:02:58] <megal0maniac> I hate flipping electronics
[15:03:23] <megal0maniac> I don't want to know about a common-emitter amplifier with an ac (capacitively) coupled load
[15:03:31] <megal0maniac> Go away!
[15:03:41] <megal0maniac> </end rant>
[15:05:00] <spec_> But flip-flopping electronics are fun!
[15:05:21] <megal0maniac> They will be
[15:05:24] <megal0maniac> But not now
[15:09:08] <OndraSter> masterq, AFAIK gcc is not aware of external RAM
[15:09:09] <OndraSter> check out atmel's samples
[15:09:13] <OndraSter> it is there
[15:09:19] <OndraSter> and ASF has got a project with their xmega EBI library
[15:09:25] <OndraSter> well, code for it
[15:14:53] <masterq> ok, im not really fan off the asf. but it should be possible to tell gcc that there is external memory... and the ram is initiated succesfully.
[15:36:33] <masterq> i have read the asf, there is nothing new, just that the asf is obsolete, there is no support for 4-Port ebi.
[15:49:15] <OndraSter> yeah, abcminiuser was not sure if 4port EBI works on 100pin devices
[15:49:20] <OndraSter> let alone me :P
[15:49:31] <abcminiuser> IIRC no
[15:49:48] <OndraSter> but it is in the datasheet
[15:49:52] <OndraSter> for the A series
[15:49:55] <OndraSter> with pin mapping
[15:51:39] <abcminiuser> I believe it's technically in the design
[15:51:47] <abcminiuser> But not implemented in any shipped products
[15:51:52] <OndraSter> D:
[15:51:55] <abcminiuser> A1 manual only has 3 port
[15:51:57] <OndraSter> I wanted to run 128Mbit SDRAM :(
[15:52:02] <abcminiuser> So you'd need an A0 :P
[15:52:09] <OndraSter> are there any? :P
[15:52:15] <abcminiuser> No
[15:52:18] <OndraSter> :(
[15:53:21] <abcminiuser> 128 is possible with 3 port according to the datasheet
[15:53:23] <abcminiuser> For SDRAM
[15:53:32] <abcminiuser> Supports SDRAM up to
[15:53:32] <abcminiuser> – 128M bit using 3-port EBI
[15:53:34] <OndraSter> so I remember that
[15:53:36] <OndraSter> yeah
[15:53:42] <OndraSter> good
[15:53:43] <OndraSter> gooooood
[15:55:31] <abcminiuser> *** SysOp: Warning, the system will sleep in 5 minutes. Please complete all ongoing transactions. ***
[16:14:10] <The_Coolest> damn it. I want to ask whether his system slept successfully or not
[16:43:30] <RikusW> A program is a sequence of processing errors.
[16:43:30] <RikusW> (c) An unknown author
[16:51:49] <asteve> RikusW: are you South African?
[16:51:59] <RikusW> yes
[16:52:03] <asteve> nice
[16:52:25] <RikusW> where are you from ?
[16:52:52] <asteve> USA
[16:53:27] <asteve> I just saw your name and thought it sounded very South African like
[16:53:39] <RikusW> indeed
[16:54:05] <RikusW> there are a few of use around on freenode
[16:54:10] <RikusW> *us
[16:54:25] <RikusW> like megal0maniac
[16:54:32] <RikusW> cart_man
[16:54:57] <RikusW> I've not seen scuzzy in a very long time
[16:58:12] <inkjetunito> steve sounds north american
[16:59:07] <abetusk_w> I'm thinking of using an atmega328 at either 1MHz or 8MHz using the internal RC oscillator (no external crystal). Do you think I need a decoupling cap for it?
[16:59:32] <RikusW> on Vcc ?
[16:59:38] <RikusW> Uuse at lea
[16:59:43] <RikusW> Use at least 100nF
[16:59:50] <asteve> shouldn't you always have a decoupling cap and a bypass cap?
[17:00:53] <inkjetunito> argh. no breadboard-friendly xmegas
[17:42:09] <masterq> ok, i think i got it
[17:43:08] <masterq> the solution is, to init the sram in .init0 section
[17:48:43] <RikusW> seems about right
[17:56:05] <masterq> RikusW: why about?
[18:32:54] <RikusW> init0
[19:14:24] <MarkX> hey
[19:15:56] <MarkX> quick question about USB development, when using the audio class for (example) a usb speaker, is it necessary to add an input terminal in the configuration descriptor?