| 02:04.36 | *** join/#edev purl (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 02:04.36 | *** topic/#edev is a channel for the discussion of hacking small consumer electronic devices, mostly ARM based |
| 02:05.44 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 03:31.00 | *** join/#edev diamat (n=cerne@2001:5c0:8fff:fffe:0:0:0:5b4f) |
| 03:31.47 | *** part/#edev diamat (n=cerne@2001:5c0:8fff:fffe:0:0:0:5b4f) |
| 05:34.16 | *** join/#edev DrZimmerman (n=theo@84-74-134-243.dclient.hispeed.ch) |
| 06:17.58 | *** join/#edev T0mW (n=Tom@24.238.86.158.res-cmts.sth.ptd.net) |
| 08:14.35 | *** join/#edev hw (n=hw@87.139.57.5) |
| 10:12.32 | *** join/#edev redblue (i=star@ppp245.108-253-207.mtl.mt.videotron.ca) |
| 11:32.38 | *** join/#edev tkp (n=tom@62-64-195-125.dynamic.dial.as9105.com) |
| 12:06.17 | *** join/#edev sjhill (n=sjhill@real.realitydiluted.com) |
| 13:00.30 | *** join/#edev davidc__ (n=davidc__@c-24-8-151-128.hsd1.co.comcast.net) |
| 13:24.43 | *** join/#edev GPSFan (n=kenm@12.10.255.248) |
| 13:24.43 | *** mode/#edev [+o GPSFan] by ChanServ |
| 14:24.29 | *** join/#edev prpplague (n=dave@mail.americanmicrosystems.com) |
| 14:57.28 | *** join/#edev CosmicPenguin (i=nobody@nat/amd/x-6195b22539335498) |
| 14:57.28 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 15:11.52 | *** join/#edev redblue (i=star@ppp098.110-253-207.mtl.mt.videotron.ca) |
| 15:17.16 | *** join/#edev Crofton (n=balister@hc652163f.dhcp.vt.edu) |
| 15:20.40 | *** join/#edev ccole (n=cole@coledd.com) |
| 15:57.13 | *** join/#edev davidc__work (n=davidc@sta-204-188-103-98.rockynet.com) |
| 15:58.43 | davidc__work | oi all. This is sorta work related, but what would people like to see on an AT91SAM9260 dev board? |
| 16:37.15 | *** join/#edev lyakh (n=lyakh@dynamic-unidsl-85-197-31-110.westend.de) |
| 16:39.04 | hw | davidc__work: hw or sw? |
| 16:39.37 | davidc__work | hw, either. |
| 16:40.14 | davidc__work | I work at a certain unnamed online-electronics seller, doign design stuff. Designing an AT91RM9200 board for people to play with ;) |
| 16:40.33 | davidc__work | Right now its got USB, ethernet, 4xuart, camera connector, 64 MB sdram, JTAG port |
| 16:40.49 | davidc__work | [USB host/device] |
| 16:41.04 | davidc__work | currently running full vers of linux |
| 16:46.06 | hw | In our case we bought the at91sam eval board to have a arm 926EJ core. =) We doing a starterkit for a arm 926EJ based chip. So we dont need more then uart, nic, etc. |
| 16:51.42 | MonMotha | davidc__: bring out all the IOs to headers of something at least semi-standard (i.e. I can buy both parts at Digi-Key/Mouser). That's pretty much a requirement on any dev board I buy |
| 16:52.27 | prpplague | davidc__work: what kind of ethernet? |
| 16:52.52 | prpplague | davidc__work: might add a spi port for doing mmc/sd cards |
| 16:53.57 | MonMotha | ah yes, just chuck the slot on there while you're at it |
| 16:54.00 | MonMotha | mini-SD isn't too big |
| 16:54.49 | MonMotha | including an RS-232 level shifter (as well as an option to bypass and connect directly at the I/O level for that device) is always handy on the dev board, as well |
| 16:55.04 | MonMotha | what kind of onboard flash? |
| 17:07.18 | davidc__work | MonMotha, hmm... I don't havea all the IO's pinned out because there are gobs of em |
| 17:07.23 | davidc__work | gonna have a mini-sd slot |
| 17:07.32 | davidc__work | has rs232 level shifters for the debug uart + uart0 |
| 17:07.44 | davidc__work | the other 3 uarts are available just as headers for TTL IO levels |
| 17:07.48 | MonMotha | they don't need to be brought out "nicely". Just chuck them on headers in a way that makes the layout easy |
| 17:08.05 | davidc__work | yeah.. I might do that. |
| 17:08.17 | davidc__work | I may leave off some bits - aka, ethernet for example |
| 17:08.26 | davidc__work | but the others I'll try and break out |
| 17:08.43 | davidc__work | Currently the onboard flash is just an atmel dataflash that gets bootstrapped into ram |
| 17:09.14 | davidc__work | its got 64MB of ram, so its got plenty of space to store a basic FS + kernel |
| 17:09.18 | MonMotha | well, anything that is already used for a dedicated function (like ethernet) need not be brought out on headers |
| 17:09.29 | davidc__work | MonMotha, problem is, thats most of the chip :/ |
| 17:09.34 | tkp | anyone here got much experience with u-boot? |
| 17:09.46 | MonMotha | well, that makes your life easier then in terms of bringing out all the extra functions :) |
| 17:09.55 | davidc__work | MonMotha, heh, k ;) |
| 17:09.58 | MonMotha | personally, having some NAND on there would be useful for me, as well |
| 17:10.01 | davidc__work | the rest of the FS I was anticipating putting on the microsd |
| 17:10.05 | MonMotha | what's your target price for this board? |
| 17:10.06 | davidc__work | hmm.. I'll look into the NAND |
| 17:10.12 | davidc__work | MonMotha, flexible |
| 17:10.16 | davidc__work | depends on how much we put on it ;) |
| 17:10.23 | MonMotha | the real Atmel board is like $500 or 600 |
| 17:10.30 | davidc__work | yea, definitely below that |
| 17:12.00 | davidc__work | I'm at sparkfun - sorta inline with the rest of our prices is the target. |
| 17:13.36 | davidc__work | prpplague, and it was 10/100 ethernet |
| 17:14.07 | *** join/#edev T0mW (n=Tom@24.238.86.158.res-cmts.sth.ptd.net) |
| 17:15.16 | MonMotha | ah sparkfun |
| 17:15.28 | MonMotha | I was just there looking at the GPRS modules |
| 17:15.46 | MonMotha | Unfortunately, it looks like the power budget is a wee bit too close to power them off USB |
| 17:16.00 | davidc__work | yeah, we do it, but its a bit dodgy. |
| 17:16.32 | davidc__work | hmm.. 2G of flash is pretty cheap these days! |
| 17:16.45 | MonMotha | especially in SD form |
| 17:17.03 | davidc__work | eh, this is in TSOP annd form. just wish it was more than 8 bytes wide |
| 17:17.11 | davidc__work | er, bits |
| 17:17.24 | MonMotha | and yeah, powering those GPRS modules off USB would be possible, as most hosts don't complain TOO much about going over 500mA for short periods of time, but dodgy is the right word |
| 17:17.34 | MonMotha | and I know you can get x16 NAND |
| 17:17.42 | MonMotha | heck, digikey sells it |
| 17:17.45 | davidc__work | yup |
| 17:17.55 | davidc__work | just theres a sweet price point for x8 NAND @ 2Gig :P |
| 17:17.59 | MonMotha | ah |
| 17:18.25 | davidc__work | $12 QTY 1 |
| 17:18.58 | MonMotha | yeah |
| 17:19.01 | MonMotha | that the micron chip? |
| 17:19.13 | davidc__work | ya.. wonder if thats Gb or GB |
| 17:19.20 | MonMotha | Gb, almost certainly |
| 17:19.24 | MonMotha | that's how they always spec them |
| 17:19.41 | davidc__work | yeah, I forgot for a second that digikey caps those specs |
| 17:31.01 | MonMotha | davidc__work: yeah, digikey has decent parametric data, but it's often not in the best form |
| 17:31.14 | davidc__work | ya. |
| 17:31.47 | davidc__work | eh.. I'll look into the nand flash stuff. Looks like I'm gonna have to write spi-mmc support for the kernel for the microSD, which will be a bit of a pain, but oh well |
| 17:32.33 | MonMotha | there's no support for that already? |
| 17:32.43 | davidc__work | eh, apparently there is, but I can't find that it exists |
| 17:33.05 | davidc__work | mmh, found some stuf |
| 17:33.12 | davidc__work | just doesn't look like its hit mainline yet |
| 17:34.12 | MonMotha | that's entirely possible |
| 17:34.18 | MonMotha | though it's probably in some patch series |
| 17:36.48 | davidc__work | hmm.. I'll just move it to the internal MMC controller rather than using the SPI interface. |
| 17:37.04 | davidc__work | that way it'll work with mainline. |
| 18:01.55 | MonMotha | jeeesh, DDR RAM is...um...fun?...to talk to |
| 18:05.21 | davidc__work | yeah :P |
| 18:05.28 | davidc__work | I stick to SDRAM whenever possible |
| 18:05.40 | MonMotha | I need the bandwidth, here |
| 18:05.51 | davidc__work | yeah.. ergo the whenever possible. |
| 18:05.56 | MonMotha | yeah |
| 18:06.04 | davidc__work | Well, if you're using an FPGA, just make a really really wide SDRAM bank :D |
| 18:06.16 | MonMotha | I am using an FPGA, and I could |
| 18:06.16 | davidc__work | [I kid] |
| 18:06.18 | MonMotha | but that takes board real-estate |
| 18:06.24 | davidc__work | yeah, and a routing nightmare |
| 18:06.28 | MonMotha | that too |
| 18:06.51 | MonMotha | SSTL doesn't appear THAT complicated, and there are ready-made DDR controller cores out there for free |
| 18:07.01 | davidc__work | ya, opencores has one |
| 18:07.04 | davidc__work | never used it though |
| 18:07.18 | MonMotha | that's the one I was looking at |
| 18:08.20 | MonMotha | Xilinx has some too that can be had for free via EDK, but they are pretty well married to PPC/uBlaze PLB |
| 18:21.17 | davidc__work | anyhow, if anything thinks of something they want to see on the board, gonna be laying out the R2 board later today, so let me know before then ;) |
| 18:47.40 | MonMotha | davidc__work: not for that board, but I do have a question |
| 18:48.37 | MonMotha | is it possible to get the SAM7X256 board with a 7XC256 mounted? |
| 18:48.50 | MonMotha | or failing that, a board with no chip mounted at all |
| 18:48.59 | MonMotha | but everything else populated |
| 18:50.49 | T0mW | davidc__work: I had SPI MMC support in the H1940 kernel that I used on the samsung s3c2410... |
| 18:51.11 | T0mW | davidc__work: look at what is up on handhelds.org |
| 18:52.08 | davidc__work | T0mW, awesome |
| 18:52.43 | davidc__work | MonMotha, hmm.. talk to olimex. They come to use preassembled :/ |
| 18:52.50 | T0mW | davidc__work: basically, all I did was diff the sources and took their h1940 (s3c2410 again) source and wrote it into my kernel |
| 18:53.33 | T0mW | davidc__work: using apex, I was able to boot from the MMC card |
| 18:53.36 | davidc__work | cool. I'll look into that. |
| 19:00.27 | davidc__work | I might actually use the built in MMC controller rather than running the card through SPI... |
| 19:23.26 | prpplague | davidc__work: for your sam project? |
| 19:24.00 | prpplague | davidc__work: if so, the SPI interface for the sd/mmc is much easier to work with imho |
| 19:24.20 | davidc__work | prpplague, yeah - but there is a controller built in for the MMC int that I'm not using |
| 19:24.31 | davidc__work | also, its got driver support in mainline |
| 19:24.39 | prpplague | davidc__work: ahh |
| 19:24.51 | prpplague | davidc__work: as long as the driver support is in the mainline |
| 19:25.08 | prpplague | davidc__work: btw, hows things going for the job? |
| 19:25.11 | davidc__work | there is some spi-mmc stuff that I could use.. but its not in mainline yet |
| 19:25.14 | davidc__work | prpplague, lovin it ;) |
| 19:25.22 | prpplague | davidc__work: cool |
| 19:27.32 | davidc__work | If you guys ever have things you'd like to see us carry, let me know ;) |
| 19:30.38 | davidc__work | We're always looking for cool chips to breakout ;) |
| 19:39.35 | Crofton | where do you work? |
| 19:40.36 | davidc__work | Crofton, Spark Fun |
| 19:40.54 | Crofton | hmm, I need one of those USB jtag thingies ;) |
| 19:41.01 | Crofton | that is out of stock :( |
| 19:41.08 | davidc__work | heh, the ones we're always outta stock of? |
| 19:41.13 | Crofton | yeah |
| 19:41.16 | davidc__work | Watch the website - just got a big olimex shipment in |
| 19:41.25 | Crofton | the #edev guys have convinced me to get one |
| 19:41.35 | Crofton | cool, I signed up on the auto notify |
| 19:42.14 | davidc__work | nah, didn't come in this shipment :( |
| 19:42.21 | davidc__work | ya, they're insanely handy |
| 19:42.23 | Crofton | bummer |
| 19:42.25 | davidc__work | debugging a kernel with one right now |
| 19:42.30 | Crofton | heh |
| 19:42.41 | Crofton | any thoughts on how long before you see one? |
| 19:43.34 | davidc__work | Crofton, dunno.. I'll ask around when the next olimex shipment is coming in |
| 19:43.40 | Crofton | thanks |
| 19:43.53 | Crofton | basically, days, weeks, months, years :) |
| 19:47.27 | davidc__work | weeks probably |
| 19:57.30 | Crofton | Thanks |
| 19:57.42 | Crofton | I shouldn't focus on that until then anyway :( |
| 19:58.34 | Crofton | Do you have any fast ARM boards with high speed USB ports? |
| 19:59.20 | CosmicPenguin | still on the search for high speed USB ports? :) |
| 19:59.45 | Crofton | yeah |
| 20:05.03 | *** join/#edev tkp (n=tom@62-64-195-125.dynamic.dial.as9105.com) |
| 20:06.01 | davidc__work | Crofton, we have some new stuff coming fairly soon |
| 20:06.11 | Crofton | cool |
| 20:26.15 | prpplague | Crofton: only the arm11 boards will have the usb2.0 host ports |
| 20:26.41 | prpplague | Crofton: i seriously doubt any of the arm vendors are going to retrofit their arm9 boards for 2.0 |
| 20:26.45 | Crofton | yeah, there was one n linuxdevices the other day I think |
| 20:26.47 | Crofton | yeah |
| 20:27.00 | prpplague | Crofton: yea it was arm11 |
| 20:27.34 | prpplague | Crofton: this one - http://www.linuxdevices.com/news/NS5355237317.html |
| 20:27.50 | Crofton | yep |
| 20:30.02 | prpplague | lordy lordy |
| 20:30.11 | chouimat | yes? |
| 20:30.16 | prpplague | CosmicPenguin: my struggles with marvell are slowly grinding to a halt |
| 20:31.52 | CosmicPenguin | for the good or the bad? |
| 20:32.00 | prpplague | CosmicPenguin: for the worst |
| 20:32.40 | prpplague | CosmicPenguin: marvell doesn't think our 30-40k units per year is worthy of the risk in providing us with an nda and docs |
| 20:32.48 | prpplague | CosmicPenguin: soooo |
| 20:33.12 | prpplague | CosmicPenguin: big meeting monday to decide what to do |
| 20:33.28 | Crofton__ | heh |
| 20:33.31 | prpplague | CosmicPenguin: i just don't understand marvell |
| 20:34.20 | davidc__work | prpplague, what kind of a thing are you looking for? |
| 20:34.22 | davidc__work | 24G stuff? |
| 20:34.26 | prpplague | Crofton__: last of the linux people along with 200 other engineers are being laid off from TI starting this week |
| 20:34.33 | davidc__work | er, 802.11g? |
| 20:34.39 | Crofton__ | ug |
| 20:34.44 | prpplague | davidc__work: yea |
| 20:35.11 | CosmicPenguin | Thats too bad |
| 20:35.16 | CosmicPenguin | you were our best hope for OLPC |
| 20:35.20 | Crofton__ | wtf is TI thinking? |
| 20:35.36 | davidc__work | yeah.. specially as linux is going insane on embedded devices. |
| 20:35.47 | davidc__work | OLPC? |
| 20:35.52 | CosmicPenguin | I don't think insane is the right term |
| 20:35.58 | CosmicPenguin | I think linux on embedded is actually declining |
| 20:36.03 | davidc__work | CosmicPenguin, hmm? |
| 20:36.10 | davidc__work | CosmicPenguin, I've seen it on tons of devices recently. |
| 20:36.22 | davidc__work | from a purely davidc__'s view standpoing :P |
| 20:36.33 | CosmicPenguin | The bloom is definately off the rose |
| 20:36.45 | davidc__work | prpplague, I've heard that realtek is pretty good for NDA's /etc |
| 20:36.46 | CosmicPenguin | Linux's inability to sove some seemingly easy problems has hurt it |
| 20:37.08 | davidc__work | prpplague, and they have some MAC/BBP parts |
| 20:37.18 | Crofton__ | which problems? |
| 20:37.20 | davidc__work | [and the RF section] |
| 20:37.53 | prpplague | davidc__work: yea, we will have to go over some stuff monday |
| 20:38.13 | prpplague | davidc__work: our only alternative now is to shell out the $$ for a custom driver |
| 20:38.31 | davidc__work | prpplague, erm? oh, its not running linux or something? |
| 20:38.51 | Crofton__ | this sounds like extortion ... |
| 20:39.22 | prpplague | davidc__work: yea running linux |
| 20:39.41 | davidc__work | prpplague, then why the custom driver thing? Perhaps I'm misunderstanding :P |
| 20:41.08 | prpplague | davidc__work: i can't write the driver with out the documentation, therefor we will have to pay someone who does have access to the documentation |
| 20:41.10 | *** join/#edev Crofton (n=balister@hc652163f.dhcp.vt.edu) |
| 20:41.30 | davidc__work | prpplague, ahhh. I thought you were designing new hardware, not writing to the hardware. |
| 20:42.04 | prpplague | davidc__work: no we are using an embedded module, but we have all the info for making the hardware if we wanted to, its the software side that is the issue |
| 20:43.35 | Crofton__ | prpplague, where are the TI stories coming from? |
| 20:44.00 | prpplague | Crofton__: i am sorry, i did not understand your question |
| 20:45.07 | Crofton__ | Where did you hear about the the TI layoff? |
| 20:48.36 | prpplague | Crofton__: last night on the local news |
| 20:49.24 | Crofton | http://www.pegasusnews.com/news/2007/mar/23/texas-instruments-lay-233-dallas-workers/ |
| 20:49.26 | Crofton | I found this |
| 20:49.27 | prpplague | CosmicPenguin: soooo.... the cf stuff will still move along, but the sdio stuff is dead |
| 20:49.48 | CosmicPenguin | bastards |
| 20:49.59 | prpplague | Crofton: yea that sounds like the one |
| 20:50.23 | prpplague | CosmicPenguin: i guess i could still hack on it, but if management decides to go with something else, i won't be doing full time |
| 20:50.36 | prpplague | CosmicPenguin: really disappointed in marvell |
| 20:51.02 | prpplague | CosmicPenguin: i don't understand how they expect to sell their chips if the software people can't get documentation |
| 20:51.10 | CosmicPenguin | yet they do, in great numbers |
| 20:51.39 | prpplague | CosmicPenguin: ? they sell their chips or software people get documenation? |
| 20:51.55 | CosmicPenguin | sell their chips |
| 20:52.03 | prpplague | CosmicPenguin: agreed |
| 20:52.17 | prpplague | CosmicPenguin: just keeps the smaller companies out of the game |
| 20:52.23 | CosmicPenguin | they don't care |
| 20:52.34 | CosmicPenguin | no big company *really* cares |
| 20:52.55 | prpplague | yea |
| 20:53.04 | prpplague | just disappointing |
| 20:53.45 | chouimat|away | pub time as usual ... bye :) |
| 21:28.27 | *** join/#edev Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net) |
| 21:30.40 | *** join/#edev mattastrophe (n=bigboota@CPE0004e28a9289-CM000a73a14ed4.cpe.net.cable.rogers.com) |
| 21:48.20 | *** join/#edev redblue (i=star@ppp087.108-253-207.mtl.mt.videotron.ca) |
| 23:12.15 | *** join/#edev purl (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 23:12.15 | *** topic/#edev is a channel for the discussion of hacking small consumer electronic devices, mostly ARM based |
| 23:54.32 | *** join/#edev FireEgl (i=Proteus@2001:5c0:84dc:1:211:9ff:feca:b042) |