IRC log for #edev on 20091225

00:13.46*** join/#edev linac (n=lin@122.90.101.131)
00:46.40*** part/#edev Omegamoon (n=egoe@demolitionman.xs4all.nl)
02:04.18*** join/#edev JoeLlama (n=snork@pool-71-110-196-168.lsanca.dsl-w.verizon.net)
02:25.16*** join/#edev roxfan (i=dunno@64.149-240-81.adsl-dyn.isp.belgacom.be)
05:39.37*** join/#edev mbuf (n=mbuf@122.169.213.24)
07:26.41*** join/#edev davidc___ (n=davidc__@S01060002b360aacd.vc.shawcable.net)
08:58.57*** join/#edev SandGorgon (n=OmNomNom@122.162.51.84)
09:03.52*** join/#edev SandGorgon_ (n=OmNomNom@122.162.51.84)
10:05.46*** join/#edev SpeedEvil (i=1000@tor/regular/SpeedEvil)
10:38.00*** join/#edev JoeLlama (n=snork@pool-71-110-196-168.lsanca.dsl-w.verizon.net)
11:36.36*** join/#edev pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB)
11:37.31*** join/#edev pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB)
11:48.39*** join/#edev pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB)
13:23.18*** join/#edev SandGorgon (n=OmNomNom@122.162.51.84)
15:15.43*** join/#edev GPSFan (n=kenm@64.92.145.112)
15:15.43*** mode/#edev [+o GPSFan] by ChanServ
15:23.24*** join/#edev tnrdvc (n=taner@88.249.6.230)
15:39.28*** join/#edev kergoth (n=kergoth@ip24-251-170-95.ph.ph.cox.net)
16:02.25MirellHappy Santy Claws!
16:31.48*** join/#edev MuscleNerd (i=eric@adsl-75-27-189-151.dsl.irvnca.sbcglobal.net)
18:16.50*** join/#edev ZeZu (n=null@c-71-201-12-60.hsd1.in.comcast.net)
18:57.49*** join/#edev cbx (n=cbx@unaffiliated/cbx)
19:18.27*** join/#edev SandGorgon (n=OmNomNom@122.162.51.84)
19:40.43*** join/#edev pku (n=pku@DSL01.83.171.186.177.ip-pool.NEFkom.net)
19:53.01*** join/#edev SandGorgon (n=OmNomNom@122.162.51.84)
20:10.10*** join/#edev _ABC (n=me@pool-72-83-175-203.washdc.east.verizon.net)
20:12.58_ABCHi all n Merry Christmas! I am just starting out on arms and I am seeing "startup codes" in example files. What's the use of "startup codes"? Is it just like a "boot file"?
20:37.41madsy_ABC: Never heard of such a definition.
20:38.19madsyMy guess would be a bootloader.
20:38.33madsyBut impossible to say for sure without looking at the code.
20:39.03_ABCmadsy: ah okay
20:39.30_ABCmadsy: have you worked with atmel's arm?
20:40.06madsyYou mean an Atmel ARM CPU implementation? Nope.
20:40.43_ABCok
20:41.22_ABCI am wondering if I can assume that coding style be the same as long as the same compiler is used
20:42.45madsyWhat is 'coding style' in this context?
20:43.21madsyIf you mean code formatting, then obviously not. Different programmers use different identation and styles.
20:44.16_ABCoh I see
20:44.20SpeedEvilTabs vary, as does function arrangment, and insanity.
20:44.56madsySpeedEvil: You said it ;-)
20:49.13_ABCwell how could I see if my device is supported by gcc (WinARM)?
20:58.22*** join/#edev davidc__ (n=davidc__@S01060002b360aacd.vc.shawcable.net)
21:35.13madsygcc doesn't support devices. It's a C compiler.
21:35.23madsyIts BFD library supports instruction sets.
21:35.55madsyFigure out the instruction set version of your CPU family, and compare it to the features your gcc toolchain is compiled with.
21:36.37madsybrb
22:04.26*** join/#edev florian (n=fuchs@Maemo/community/contributor/florian)
22:07.20_ABCok I checked arm's website and it says the device uses the ARMv5TEJ instruction set. but gcc only offers ARMv5/t/e/te, no J
22:15.43_ABCI find it quite odd, as gcc supports ARM926EJ-S, but not its instruction set ARMv5TEJ?!
22:20.25*** join/#edev madsy (n=madsy@78-26-25-57.network.trollfjord.no)
22:27.06_ABChi Madsy
22:27.15_ABCI checked arm's website and it says the device uses the ARMv5TEJ instruction set. but gcc only offers ARMv5/t/e/te, no J
22:27.22_ABCI find it quite odd, as gcc supports ARM926EJ-S, but not its instruction set ARMv5TEJ?!
22:29.49MadsyJ stands for jazelle, which is a instruction set for execution of java code.
22:30.16Madsygcc does not support it, because the specification has to be licenced from ARM under an NDA
22:30.25Madsyan instruction set*
22:30.27_ABCI see
22:30.32_ABCwhats NDA?
22:30.44MadsyNon-disclosure agreement.
22:30.56_ABCok
22:31.12_ABCso good, the device is supported :)
22:31.46MadsyYou probably don't need to know the Jazelle instruction set anyway. You'll have your hands full when learning ARM and Thumb.
22:32.02_ABCyeah  indeed
22:32.10MadsyAnd it's not useful unless you implement a Java VM for your OS.
22:32.19_ABCokay
22:33.01_ABChow about the device's peripherals? in example files I see that a header file mapping the peripherals is included
22:33.32MadsyWhat about the peripherals?
22:33.55MadsyI'm willing to help, but your questions have to make sense..
22:35.01_ABCHow do I know if I need to write the peripheral header file from scratch or it already has it?
22:35.56MadsyARM only makes CPU specifications. Independent hardware vendors licence the right to implement ARM processors, often embedded on more advanced chipsets.
22:36.46_ABCOh right..I am using Atmel's ARM implementation
22:37.34MadsyThen figure out the model of your chipset and see if Atmel has any SDKs or documentation for it.
22:37.46_ABCOkay
22:37.49MadsyARM only has specifications for their CPUs and instruction sets.
22:38.11MadsyAtmel should provide documentation for peripheral hardware registers and such.
22:39.19_ABCok
22:43.18_ABChm I dont see any on the website. Im flipping through the datasheet now
22:47.43*** join/#edev Crofton (n=balister@c-68-59-21-191.hsd1.sc.comcast.net)
22:48.50_ABCthe header file says it's from Atmel's software support
22:54.19*** join/#edev kergoth (n=kergoth@ip24-251-170-95.ph.ph.cox.net)
22:56.02_ABCnice I think I found it! :D
22:56.31_ABCthanks Madsy!
23:05.03_ABCHow kind is Atmel to provide files for gcc! I wonder if other manufacturers does the same

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.