| 01:14.52 | *** join/#edev jayabharath (~jayabhara@nat/ti/x-jjjdcczsrpdfhhee) |
| 02:23.45 | *** join/#edev JoeLlama (~snork@unaffiliated/joellama) |
| 02:37.29 | *** join/#edev djerome (~djerome@ip24-251-158-189.ph.ph.cox.net) |
| 05:41.07 | *** join/#edev JoeLlama (~snork@unaffiliated/joellama) |
| 07:03.49 | *** join/#edev JoeLlama (~snork@206.169.63.10) |
| 07:03.50 | *** join/#edev JoeLlama (~snork@unaffiliated/joellama) |
| 07:27.42 | *** join/#edev calculus (~calculus@gentoo/user/calculus) |
| 08:02.47 | *** join/#edev sndcrb (~sndcrb@easy-ff00c200-144.dhcp.inet.fi) |
| 08:42.46 | *** join/#edev penguinece (~penguinec@2610:48:100:8da:213:20ff:fe0a:7c8f) |
| 10:43.55 | *** join/#edev pirho (debian-tor@gateway/tor-sasl/pirho) |
| 11:38.59 | *** join/#edev jnd (~jenda@unaffiliated/jnd) |
| 12:45.01 | *** join/#edev roxfan (dunno@59.183-66-87.adsl-dyn.isp.belgacom.be) |
| 12:51.24 | *** join/#edev roxfan (dunno@59.183-66-87.adsl-dyn.isp.belgacom.be) |
| 16:27.03 | *** join/#edev madsy (~madsy@ti0207a340-0264.bb.online.no) |
| 16:27.04 | *** join/#edev madsy (~madsy@fu/coder/madsy) |
| 16:30.35 | *** join/#edev madsy (~madsy@ti0207a340-0264.bb.online.no) |
| 16:30.35 | *** join/#edev madsy (~madsy@fu/coder/madsy) |
| 17:01.56 | *** join/#edev kergoth_ (~kergoth@ip24-251-170-95.ph.ph.cox.net) |
| 17:13.16 | *** join/#edev jnd (~jenda@unaffiliated/jnd) |
| 17:34.32 | *** join/#edev avinashhm (~avinash-h@192.163.20.231) |
| 18:05.23 | *** join/#edev NightMonkey (~NightMonk@173-164-139-193-SFBA.hfc.comcastbusiness.net) |
| 18:05.23 | *** join/#edev NightMonkey (~NightMonk@pdpc/supporter/professional/nightmonkey) |
| 18:12.46 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 18:32.45 | *** join/#edev djerome (~djerome@ip24-251-158-189.ph.ph.cox.net) |
| 18:34.35 | *** join/#edev prpplague (~danders@nat/ti/x-bghrqsxoadzfjylx) |
| 18:44.49 | *** join/#edev avinashhm (~avinash-h@192.163.20.231) |
| 20:13.26 | *** join/#edev jayabharath (~jayabhara@nat/ti/x-zkocbouubcigfpwp) |
| 20:17.58 | *** join/#edev kergoth_ (~kergoth@ip24-251-170-95.ph.ph.cox.net) |
| 20:58.19 | *** join/#edev coafcv (~mmm@p4FFE3AF9.dip.t-dialin.net) |
| 20:59.39 | *** join/#edev oberon (~oberon@DSL217-132-38-72.bb.netvision.net.il) |
| 20:59.43 | oberon | hi |
| 20:59.58 | prpplague | oberon: greetings |
| 21:00.09 | oberon | I have an IAR evaluation board with stm32f103vc chip on it |
| 21:00.25 | oberon | it has a segger jlink programmer on board |
| 21:01.06 | oberon | now, I use the IAR development env to work under M$ windows, but I consider switching to Linux |
| 21:01.33 | oberon | are there tool for flashing/debugging under Linux for my hardware ? |
| 21:01.37 | oberon | tools |
| 21:01.48 | prpplague | oberon: i'm not famliar with the tools available for the stm32 under linux |
| 21:02.07 | oberon | it's an ARM Cortex-3 chipset |
| 21:02.09 | prpplague | oberon: might check some of the sparkfun.com forums to see what others are using |
| 21:02.14 | prpplague | oberon: indeed |
| 21:02.41 | prpplague | oberon: generally anything that supports ARM should work for the stm32, just not familiar with the JLinking jtag programmer |
| 21:03.51 | oberon | openocd supports it |
| 21:04.02 | oberon | can I flash using openocd ? |
| 21:04.32 | prpplague | if openocd supports the jlink you should be able to do just about anything you need, including flash support |
| 21:05.17 | oberon | well, I just need to learn how to use openocd .. |
| 21:05.28 | oberon | are you using openocd ? |
| 21:10.53 | prpplague | hehe, yes |
| 21:11.23 | oberon | are you the developer ?! |
| 21:12.07 | oberon | it has a single command line executable "openocd" |
| 21:12.59 | oberon | that looks for openocd.cfg |
| 21:14.04 | *** join/#edev jnd (~jenda@ip-86-49-42-157.net.upcbroadband.cz) |
| 21:14.08 | *** join/#edev jnd (~jenda@unaffiliated/jnd) |
| 21:14.52 | prpplague | oberon: i was one of the original developers for openocd, but haven't done much with it in a few years |
| 21:15.12 | oberon | why not ? |
| 21:15.23 | oberon | using other tools ? |
| 21:15.39 | prpplague | no, just been too busy with other kernel development |
| 21:22.57 | oberon | hmm, is there a firmware for an arduino that turns it into a JTAG programmer ? |
| 21:23.41 | prpplague | oberon: i have not heard of one, but that doesn't mean there isn't |
| 21:23.50 | prpplague | later |
| 21:24.13 | oberon | thanks for the help |
| 21:45.55 | *** join/#edev r56q (~pku@DSL01.83.171.178.90.ip-pool.NEFkom.net) |
| 22:05.41 | Mirell | Hmm... |
| 22:16.38 | *** join/#edev JoeLlama (~snork@unaffiliated/joellama) |
| 22:42.09 | *** join/#edev prpplague (~Dave@ppp-70-242-121-21.dsl.rcsntx.swbell.net) |
| 22:42.49 | *** join/#edev SpeedEvil (~user@tor/regular/SpeedEvil) |
| 22:59.38 | *** join/#edev m4t (matt@theorize.org) |
| 23:01.03 | NightMonkey | prpplague: Thanks for openocd! :) |
| 23:04.52 | prpplague | NightMonkey: ?? |
| 23:05.35 | NightMonkey | prpplague: Just saw the conversation earlier, and thought I'd thank you for your work on openocd. :) |
| 23:05.53 | NightMonkey | prpplague: I just recently started using it, and it works fairly well. |
| 23:06.01 | Mirell | Hmm...I need to learn how to use JTAGs at some point. |
| 23:06.03 | prpplague | NightMonkey: ahh ok, i was more of a stealth developer on the original dev |
| 23:06.34 | prpplague | NightMonkey: did alot of hardware testing and flash support |
| 23:06.50 | NightMonkey | prpplague: And it shows. Lots of good device support. |
| 23:06.52 | prpplague | NightMonkey: hope you are using a flyswatter! *cough* |
| 23:07.41 | NightMonkey | prpplague: I'm a newb to ARM/uboot devices, but I can figure out bug workarounds pretty quick. |
| 23:08.09 | prpplague | http://www.elinux.org/Flyswatter |
| 23:08.22 | NightMonkey | prpplague: Besides, OpenOCD doesn't come with a warranty. ;) |
| 23:08.36 | NightMonkey | prpplague: Oh. |
| 23:09.36 | NightMonkey | prpplague: I'm just using it with FTDI USB JTAG stuff now (SheevaPlug, GuruPlug). I'm not deep enough yet to go beyond those. |
| 23:10.38 | NightMonkey | While the GuruPlugs are proving to be rather unusable, the little JTAG Board that I got with them works well. |
| 23:11.08 | NightMonkey | (Unusable in the field, that is) |
| 23:11.24 | NightMonkey | Heat dissapation no bueno. |
| 23:15.13 | m4t | hey, on the subject of jtag...which (if any) of these is the parallel port address? [ 1806.662602] usblp0: USB Bidirectional printer dev 7 if 0 alt 1 proto 2 vid 0x067B pid 0x2305 |
| 23:15.24 | m4t | 0x2305? |
| 23:18.55 | *** join/#edev SpeedEvil1 (1000@tor/regular/SpeedEvil) |
| 23:19.49 | NightMonkey | m4t: Hrm. Not really related, but I would think you'd see something like this in dmesg: |
| 23:19.53 | NightMonkey | parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] |
| 23:20.20 | NightMonkey | and maybe before this: |
| 23:20.23 | NightMonkey | parport_pc 00:06: reported by Plug and Play ACPI |
| 23:20.28 | NightMonkey | (but that's x86" |
| 23:20.29 | NightMonkey | ) |
| 23:20.36 | m4t | this is usb |
| 23:21.23 | NightMonkey | m4t: Don't you still need parport module loaded? |
| 23:21.50 | m4t | it is loaded |
| 23:22.32 | NightMonkey | m4t: Sorry I couldn't help more. |
| 23:23.43 | m4t | :/ |
| 23:23.47 | m4t | its a PL2305 |
| 23:23.54 | m4t | most of the usb jtag i see are ftdi |
| 23:25.58 | m4t | from what im reading its supposedly too slow for practical use |
| 23:27.18 | m4t | oh well, was only 5$ |
| 23:30.16 | NightMonkey | m4t: You could turn up usb debugging; perhaps there's a clue in there. |
| 23:30.54 | m4t | the way it sounds itd be a few hundred baud max |
| 23:31.13 | m4t | 1-5ms delay on each cmd |