| 00:38.58 | *** join/#edev MonMotha (n=monmotha@cpe-24-160-204-34.ma.res.rr.com) |
| 01:31.51 | *** join/#edev FireEgl (i=Proteus@2001:5c0:84dc:0:211:9ff:feca:b042) |
| 04:07.02 | *** join/#edev linac (n=lin@5.92.76.222.broad.fz.fj.dynamic.163data.com.cn) |
| 04:43.21 | *** join/#edev LyosNorezel (n=LyosNore@cpe-75-179-153-30.woh.res.rr.com) |
| 05:46.25 | *** join/#edev DrZimmerman (n=theo@84-74-134-243.dclient.hispeed.ch) |
| 06:25.15 | *** join/#edev silverpower (n=shrike@adsl-234-210-221.cha.bellsouth.net) |
| 06:46.33 | d-d-c | could someone tell me about the jtag cable for the walnut ? |
| 07:35.35 | *** join/#edev hw (n=hw@87.139.57.5) |
| 08:41.04 | d-d-c | is there a way to realize a lowcost jtag programmer for the walnut ? |
| 10:41.12 | *** join/#edev d-d-c (n=none@host48-143-dynamic.54-82-r.retail.telecomitalia.it) |
| 12:30.59 | *** join/#edev GPSFan (n=kenm@12.10.255.248) |
| 12:30.59 | *** mode/#edev [+o GPSFan] by ChanServ |
| 13:07.11 | *** join/#edev prpplague (n=dave@mail.americanmicrosystems.com) |
| 13:28.15 | *** join/#edev sjhill (n=sjhill@real.realitydiluted.com) |
| 14:11.32 | *** part/#edev wmat (n=btraynor@gromit.mixdown.ca) |
| 14:16.35 | d-d-c | does somebody know a way to build a cheap jtag cable to reprogram the dht-walnut ? |
| 14:21.31 | agaffney | 08:49 <@jbevren> http://elinux.org/wiki/ |
| 14:21.31 | agaffney | 08:49 <@jbevren> lotsa info there, including the jtag port |
| 14:21.40 | agaffney | he already answered you yesterday |
| 14:25.52 | *** join/#edev chouimat|Zzzz (n=dieu@r2351064.cidc.net) |
| 14:27.12 | chouimat | morning |
| 14:40.30 | d-d-c | agaffney i've read the page |
| 14:41.05 | d-d-c | but if i'm here asking, is because there is information missing: the jtag cable ! |
| 14:42.06 | d-d-c | and this is what i'm asking about: information about how to make this cable |
| 14:42.28 | agaffney | you buy one |
| 14:42.34 | agaffney | or you use google |
| 14:42.35 | *** join/#edev Chocobo (n=swinchen@strongbad.eece.maine.edu) |
| 14:42.37 | agaffney | it's your friend |
| 14:43.00 | d-d-c | :'( |
| 14:43.17 | d-d-c | damn the hell |
| 14:43.34 | d-d-c | i'm also asking about the jtag-walnut pinout |
| 14:43.49 | d-d-c | it has got 4 pin not covered in the jtag standard |
| 14:45.22 | d-d-c | see the standard |
| 14:45.23 | d-d-c | http://linkstationwiki.net/index.php?title=Install_a_JTAG_Port |
| 14:45.27 | d-d-c | - |
| 14:46.06 | d-d-c | the dht-walnut has these extra pins |
| 14:46.08 | d-d-c | SRESET =Soft-Reset |
| 14:46.08 | d-d-c | HRESET =Hard-Reset |
| 14:46.08 | d-d-c | KSTP_OUT = ? |
| 14:46.08 | d-d-c | CKSTP_IN = ? |
| 14:46.12 | d-d-c | - |
| 14:46.17 | d-d-c | so what about the cable ? |
| 14:46.31 | d-d-c | could/should i ignore the 4 extra pins ? |
| 14:57.45 | prpplague | http://www.elinux.org/wiki/JTAG |
| 14:58.29 | prpplague | d-d-c: unless you are truely interested in understanding the mechanics of jtag, its just as easy to purchase a cheap dongle |
| 14:58.48 | d-d-c | no |
| 14:58.49 | d-d-c | no |
| 14:58.57 | d-d-c | again no |
| 14:59.11 | d-d-c | have you read what i need to know ? |
| 14:59.14 | prpplague | d-d-c: ok, well you aren't asking the right question |
| 14:59.22 | d-d-c | no ! |
| 14:59.28 | d-d-c | i'm asking the right ! |
| 14:59.40 | d-d-c | i'm asking about the not standard jtag |
| 14:59.53 | d-d-c | if you see the url i provided |
| 15:00.03 | d-d-c | you will see a standard jtag |
| 15:00.13 | d-d-c | if you look inside the walnut jtag |
| 15:00.13 | prpplague | i've very familiar with standard jtag |
| 15:00.23 | d-d-c | you will find 4 extra pins |
| 15:00.24 | d-d-c | so ? |
| 15:00.43 | prpplague | if they aren't part of standard jtag description, then they aren't used for standard jtag |
| 15:00.44 | d-d-c | i'm asking if to ignore them |
| 15:01.04 | d-d-c | they are included in the walnut pinout documentation |
| 15:01.21 | d-d-c | i don't know if the ODC-commander hw uses them |
| 15:01.46 | prpplague | like i said, if they aren't part of standard jtag, then they aren't used for jtag |
| 15:01.51 | d-d-c | i'm asking if the widdle clone (a one that should be used with this software) uses/ignore them |
| 15:02.06 | prpplague | d-d-c: the wiggler does not use them |
| 15:02.16 | d-d-c | exactly ! |
| 15:02.31 | d-d-c | but the odc commander has not been designed for the wiggler ! |
| 15:02.41 | d-d-c | i know |
| 15:02.53 | d-d-c | 1) to reprogram the walnut i need the ODC commander |
| 15:03.04 | d-d-c | 2) the ODC commader uses a commercial jtag |
| 15:03.13 | d-d-c | 3) the walnut has 4 extra pins |
| 15:03.16 | d-d-c | conclusion |
| 15:03.27 | *** mode/#edev [+o prpplague] by ChanServ |
| 15:03.28 | d-d-c | could i use the widdle with ODC programmer ? |
| 15:04.09 | d-d-c | :) |
| 15:04.18 | prpplague | d-d-c: widdle == wiggler ?? |
| 15:06.02 | d-d-c | sure |
| 15:06.32 | prpplague | then yes, iirc the wiggler is supported in ODC |
| 15:06.38 | d-d-c | good |
| 15:06.40 | d-d-c | :) |
| 15:06.52 | d-d-c | good news |
| 15:06.53 | d-d-c | :) |
| 15:13.54 | d-d-c | - |
| 15:14.12 | d-d-c | guys, i'm working about the palmpilot mc68328 |
| 15:14.52 | d-d-c | if it could be interesting: i'm working around special uart bootstrap |
| 15:15.38 | prpplague | d-d-c: not polite to /msg without asking |
| 15:15.50 | prpplague | d-d-c: i never worked directly with the walnut board |
| 15:16.34 | d-d-c | prpplague i private message 'cause it is a private message |
| 15:17.42 | prpplague | d-d-c: ask next time |
| 15:18.09 | d-d-c | ok |
| 15:18.11 | d-d-c | :) |
| 15:18.24 | d-d-c | what about the 68328 ? anybody interested ? |
| 15:23.38 | prpplague | since the 683xx is EOL, no one is really doing any development these days |
| 15:25.41 | chouimat | 68328?? the one in the old palm? |
| 15:25.46 | d-d-c | yes |
| 15:25.52 | d-d-c | palm m105 |
| 15:26.22 | d-d-c | i'm able to bootstrap from an eeprom i2c |
| 15:26.38 | d-d-c | or from the uart |
| 15:26.45 | d-d-c | the idea is to replace the rom |
| 15:27.21 | d-d-c | palm m105 is also good as external display uart connected to linux |
| 15:27.34 | d-d-c | so ... cheap/intersting |
| 15:27.59 | chouimat | d-d-c: yup ther m125 too :) |
| 15:28.09 | d-d-c | eheheh yes |
| 15:29.01 | d-d-c | the only problem with 68328 is that you have to replace the uart bootstrap with something that understdans SREC |
| 15:29.37 | d-d-c | i did a little adapter that is loaded at the bootstrap time |
| 15:29.46 | d-d-c | then it handles the second load |
| 15:30.23 | *** join/#edev cbaird (n=cbaird@brushtail.apana.org.au) |
| 15:37.32 | d-d-c | - |
| 15:37.44 | d-d-c | anyway, if you foun interesting, feel free to ask |
| 15:40.49 | prpplague | hmm |
| 15:40.54 | prpplague | anyone do avr stuff? |
| 15:42.21 | d-d-c | i will ... |
| 15:46.27 | *** join/#edev lyakh (n=lyakh@dynamic-unidsl-85-197-31-110.westend.de) |
| 16:54.29 | MonMotha | prpplague: I do... |
| 16:59.55 | MonMotha | prpplague: what kind of AVR stuff are you dealing with? |
| 17:23.17 | prpplague | MonMotha: i have a working project on a atmega128, wanting to get it running on a atmega38 |
| 17:23.22 | prpplague | atmega48 |
| 17:23.36 | prpplague | MonMotha: just wondering what the code differences are |
| 17:27.07 | *** join/#edev Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net) |
| 17:41.26 | d-d-c | - |
| 17:41.34 | d-d-c | is somebody working with http://www.tnkernel.com/description.html |
| 17:41.54 | d-d-c | it is a realtime (soft) kernel for arm |
| 18:07.18 | *** join/#edev ericho (n=erich@189.129.30.238) |
| 19:18.50 | *** join/#edev Chocobo (n=swinchen@strongbad.eece.maine.edu) |
| 19:19.21 | Chocobo | Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal |
| 19:19.23 | Chocobo | error, but for better emulation accuracy either use a 2.6 host Linux kernel or |
| 19:19.25 | Chocobo | type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. |
| 19:19.27 | Chocobo | I am using a 2.6 kernel... any ideas? |
| 19:23.38 | *** join/#edev AMDPenguin (i=nobody@nat/amd/x-2abf1fa9a46d818f) |
| 19:24.33 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 19:24.36 | Crofton | gm |
| 19:24.39 | *** join/#edev CP|too (n=nobody@www.crouse-house.com) |
| 19:25.04 | prpplague | Crofton: doh i read that is 30 business days not calendar days for delisting |
| 19:25.18 | Crofton | heh |
| 19:25.31 | Crofton | I don't really care about that today |
| 19:25.31 | chouimat | hi prpplague |
| 19:25.48 | prpplague | Crofton: oh? |
| 19:25.52 | prpplague | Crofton: whats up? |
| 19:25.57 | prpplague | Crofton: bad day? |
| 19:26.08 | chouimat | prpplague: check cnn.com |
| 19:27.00 | prpplague | wow |
| 19:27.17 | Chocobo | oops.. sorr |
| 19:27.32 | prpplague | Crofton: you there in the area? |
| 19:29.51 | Crofton | well, |
| 19:30.03 | Crofton | one of the guys from Norris is here now |
| 19:31.14 | Crofton | The major shooting was like 200 yards from my office |
| 19:31.21 | chouimat | ouch |
| 19:33.38 | prpplague | Crofton: holy cow |
| 19:33.44 | Crofton | Bob was in teh basement |
| 20:34.15 | prpplague | wow |
| 20:34.25 | prpplague | mallum has another notch in his belt - http://www.linuxdevices.com/news/NS8166710404.html |
| 20:35.37 | d-d-c | nice |
| 20:35.38 | d-d-c | :) |
| 20:37.15 | d-d-c | does somebody know what is the max temperature of ppc7410 die ? |
| 20:37.37 | d-d-c | i'm doing a safe-guard-temperature-daemon |
| 20:37.50 | d-d-c | i need the max value to shotdown the machine |
| 20:38.07 | d-d-c | i can't find the temperature information from freescale |
| 20:38.19 | prpplague | d-d-c: yea, the person who know that goes under the name "DATASHEET" |
| 20:38.46 | chouimat | prpplague: :D |
| 20:40.15 | d-d-c | <d-d-c> i can't find the temperature information from freescale |
| 20:40.19 | *** join/#edev ico2 (n=ico2@modem-2692.chimpanzee.dialup.pol.co.uk) |
| 20:40.21 | d-d-c | are you able to read ? |
| 20:46.42 | prpplague | d-d-c: i can.... can you? http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC7410&fsrch=1 |
| 20:47.02 | d-d-c | clap clap |
| 20:47.06 | d-d-c | thank you |
| 20:49.46 | prpplague | max rework temp is 250, standard junction working temp is 105 |
| 20:50.16 | d-d-c | i experienced a damaged at 60 |
| 20:51.04 | d-d-c | i'm talking about the die temperature |
| 20:51.19 | d-d-c | the one has been read by the internal temperature sensore |
| 20:51.38 | d-d-c | the linux kerenl are able to report it /proc/cpuinfo |
| 20:55.35 | *** join/#edev ericho (n=erich@189.129.30.238) |
| 20:56.12 | prpplague | d-d-c: i'd say it was probably due to something else beside temp if the max junction temp is 105 |
| 20:56.41 | d-d-c | junction temp is not a good value to project around |
| 20:56.51 | d-d-c | it is good to build up an heat sink |
| 20:57.05 | d-d-c | and i trust the heat sink has been made good |
| 20:57.31 | d-d-c | i need something to assure the machine is working in a safe way |
| 20:57.45 | d-d-c | the temperature read in the die is not the junction one |
| 20:58.00 | d-d-c | unfortunatly i can only have this information |
| 20:58.17 | d-d-c | and unfortunatly datasheet report junction one |
| 20:58.22 | d-d-c | no way, no good |
| 21:16.37 | CosmicPenguin | huh |
| 21:16.38 | CosmicPenguin | well |
| 22:05.47 | *** join/#edev ico2_ (n=ico2@modem-1601.cougar.dialup.pol.co.uk) |
| 22:12.01 | chouimat | http://www.thinkgeek.com/tshirts/generic/887e/ |
| 23:22.03 | *** join/#edev prpplague (n=dave@ppp-70-242-121-167.dsl.rcsntx.swbell.net) |
| 23:22.07 | prpplague | ho ho ho |
| 23:22.12 | prpplague | merry freakin monday |
| 23:23.06 | CosmicPenguin | dude |
| 23:23.08 | CosmicPenguin | don't do that |
| 23:25.29 | prpplague | sorry bad joke |
| 23:34.42 | MonMotha | prpplague: well, it depends on what hardware you're using and how the code is written |
| 23:34.57 | MonMotha | you're using avr-libc and gcc I presume? |
| 23:38.21 | prpplague | yea, i checked it out earlier |
| 23:38.31 | prpplague | i was able to get the code down to around 3k |
| 23:38.39 | prpplague | which will fit in the atmega48 |
| 23:38.58 | prpplague | what i need now is to just change the i/o ports to match properly |
| 23:39.03 | prpplague | i think it should run ok |
| 23:39.58 | prpplague | MonMotha: we have a legacy product that does unencoded barcode scanners, wands, and mag strips and outputs the data as a usb HID device |
| 23:40.12 | MonMotha | ug, you're doing the bit-bang low-speed USB thing? |
| 23:40.30 | prpplague | MonMotha: we are dropping the unencoded scanner, wand and mag and replacing it with a bt module |
| 23:40.44 | prpplague | MonMotha: naw, we are using a cypress usb slave device chip |
| 23:40.47 | MonMotha | oh |
| 23:40.52 | prpplague | MonMotha: cy7c63001 |
| 23:40.56 | MonMotha | you do know that Atmel has a series of AVRs with built in USB |
| 23:41.14 | MonMotha | they just came out with a smaller one that is supposed to be at a good price point |
| 23:41.20 | prpplague | yea but at what cost, plus we have stock of both the atmega48 and the cypress chip |
| 23:42.12 | MonMotha | the 64k part is $11.87 from Digi-Key in qty. 1. |
| 23:42.18 | MonMotha | they just came out with a smaller 16k variety |
| 23:43.11 | MonMotha | well, and an 8k, but the USB stack they provide takes 12k |
| 23:43.16 | MonMotha | it's poorly written, though :( |
| 23:43.22 | prpplague | doh |
| 23:43.29 | prpplague | pretty expensive |
| 23:43.42 | MonMotha | those cypress chips can't be cheap... |
| 23:44.11 | MonMotha | They're also SRAM based, which can be a blessing and a curse |
| 23:44.36 | prpplague | we are getting them for $0.98 |
| 23:44.45 | MonMotha | anyway, you should be able to port frmo the mega128 to the mega48 fairly easily. Just change all your IO ports in the code (since I'm sure they'll move) and attempt to compile it |
| 23:45.00 | MonMotha | you'll probably find that some of the other registers have been renamed slightly, but that's easy enough to fix |
| 23:45.07 | prpplague | http://www.digikey.com/scripts/DkSearch/dksus.dll?Detail?Ref=364834&Row=512276&Site=US |
| 23:45.18 | prpplague | MonMotha: cool deal |
| 23:45.24 | prpplague | MonMotha: thanks for the info |
| 23:45.30 | MonMotha | oh, those aren't the 8051s. That's why they're a little cheaper |
| 23:45.40 | prpplague | yea |
| 23:45.46 | MonMotha | I'm not sure on the pricing for the 90usb162 as they haven't made it into the distribution chain yet |
| 23:45.48 | prpplague | plus we both a WHOLE lot more than 1000 |
| 23:45.55 | prpplague | bought |
| 23:45.55 | MonMotha | well, I can get you in touch with an Atmel rep |
| 23:46.21 | prpplague | hehe, yea, we have one, just that our avr guy's last day was friday, he quit |
| 23:46.23 | MonMotha | he said he was confident that he could always do a fair bit better than digikey on anything other than teeny tiny orders |
| 23:46.23 | prpplague | doh |
| 23:46.34 | MonMotha | ah |
| 23:46.41 | MonMotha | AVR is pretty easy to code for, at least |
| 23:46.43 | prpplague | so guess who has to take over? |
| 23:46.52 | MonMotha | of course |
| 23:47.17 | prpplague | hehe we have atleast 5k of the atmega48 in stock |
| 23:47.42 | MonMotha | ah, well, then might as well use those |
| 23:48.08 | prpplague | so i have about $2.25 in the atmega48 and the cypress chip together |
| 23:48.18 | prpplague | MonMotha: always gotta reuse existing stock, hehe |
| 23:49.06 | MonMotha | the other thing to watch out for is how deep your stack gets |
| 23:49.14 | MonMotha | that's harder to see and causes all sorts of weird behavior if it gets too big |
| 23:49.25 | prpplague | ahh |
| 23:49.25 | MonMotha | the mega48 has a lot less RAM than your mega128 |
| 23:49.40 | prpplague | yea, the 48 has 512 and the 128 has 4096 |
| 23:49.45 | MonMotha | yeah |
| 23:49.55 | MonMotha | are you using malloc in this code at all? |
| 23:49.58 | prpplague | i can run the code in the mega32 without a problem though |
| 23:50.04 | prpplague | no |
| 23:50.07 | MonMotha | ok, that helps |
| 23:50.09 | prpplague | pretty simple code |
| 23:50.32 | MonMotha | meag32 still has 2k of RAM |
| 23:50.47 | MonMotha | how deep do your function calls get? |
| 23:50.59 | MonMotha | and is there any recursion |
| 23:51.24 | prpplague | none |
| 23:51.30 | MonMotha | that's certainly good |
| 23:51.37 | prpplague | yea pretty easy stuff |
| 23:51.52 | MonMotha | it's always best to avoid recursion when programming micros simply since the stack frames add up really fast |
| 23:52.04 | prpplague | a couple of interrupts and pretty straight forward processing |
| 23:52.16 | MonMotha | ok, so no calls more than a couple levels deep? |
| 23:53.55 | MonMotha | if you build with the -S option to gcc, it'll output assembly, and the comments will have the size of the stack frame for each procedure |
| 23:54.10 | MonMotha | you can add those up to get the most utilized stack. It sounds like you're not likely to get anywhere near 512 bytes |
| 23:55.12 | prpplague | yea, its pretty small, the only thing is i do have 256 byte buffer, that i'm gonna have to drop to 128 |
| 23:55.36 | MonMotha | oh, well, that takes some RAM :) |