| 00:50.17 | *** join/#openjtag openocdn00b (n=ddkd@c-98-226-129-230.hsd1.in.comcast.net) |
| 00:52.04 | openocdn00b | Is there a different environment I can use to compile OpenOCD on windows other than cygwin? |
| 01:24.38 | flyback | probably not |
| 01:24.45 | flyback | what type jtag |
| 02:36.22 | *** join/#openjtag mgross (n=mgross@66-224-185-202.atgi.net) |
| 03:19.27 | flyback | is suddentely feeling like he is about to pass out |
| 03:39.46 | *** join/#openjtag dinomight (n=dnglaze@209.0.51.23) |
| 03:42.45 | flyback | would like to die for new years resolution |
| 03:43.19 | dinomight | Wow, I feel like I'm coming in late to some conversation. |
| 04:30.59 | flyback | wrists are almost usless now and he's starting to go numb, soon as he gets his a*** fixed this is the next thing that will need to be on the surgeon chopping block |
| 04:37.36 | openocdn00b | hello |
| 04:38.11 | openocdn00b | does anybody know how to enable the experimental support for SST flash memory 39VFxxx ? |
| 04:38.57 | openocdn00b | the comment says |
| 04:38.59 | openocdn00b | - added support for non-CFI compatible flashes to cfi driver (currently only SST39VFxxx devices supported) |
| 04:38.59 | openocdn00b | This checkin is experimental, not suitable for general use |
| 04:39.47 | openocdn00b | I'm lucky/unlucky to have a SST39VF1601 flash chip on my board |
| 04:50.19 | flyback | bbl |
| 05:56.17 | flyback | goodnight |
| 07:16.56 | *** part/#openjtag dinomight (n=dnglaze@209.0.51.23) |
| 07:22.09 | *** join/#openjtag georg (n=georg@f048233137.adsl.alicedsl.de) |
| 07:26.00 | *** join/#openjtag dirk2 (n=bmd2hi@p5B041606.dip0.t-ipconnect.de) |
| 08:23.40 | *** join/#openjtag pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 08:33.41 | *** join/#openjtag mgross (n=mgross@pool-71-117-215-6.ptldor.fios.verizon.net) |
| 09:34.12 | *** join/#openjtag rje`mac (n=rje`mac@c-67-185-128-239.hsd1.wa.comcast.net) |
| 13:37.08 | *** join/#openjtag pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 15:26.15 | *** join/#openjtag tjtag (n=tjtag@bhossman.user.matrix.farlep.net) |
| 15:47.39 | *** part/#openjtag tjtag (n=tjtag@bhossman.user.matrix.farlep.net) |
| 15:57.06 | *** join/#openjtag purl (i=ibot@rikers.org) |
| 15:57.06 | *** topic/#openjtag is this is the place to discuss bootloaders and JTAG |
| 15:59.31 | *** join/#openjtag prpplague^2 (n=dave@mail.americanmicrosystems.com) |
| 16:26.24 | *** join/#openjtag dirk2 (n=bmd2hi@p5B04325E.dip0.t-ipconnect.de) |
| 16:48.03 | *** join/#openjtag tjtag (n=tjtag@bhossman.user.matrix.farlep.net) |
| 16:50.03 | tjtag | flyback: Hello ? |
| 16:51.02 | tjtag | openocdn00b, figure out your problem ? |
| 17:26.09 | openocdn00b | nope |
| 17:26.15 | openocdn00b | well only partially |
| 17:26.53 | tjtag | You will figure it out ! |
| 17:27.01 | openocdn00b | I had to add some code to non_cfi and cfi.c |
| 17:27.24 | openocdn00b | and now it can recognize my flash |
| 17:27.33 | openocdn00b | but it still does not work :-( |
| 17:28.11 | openocdn00b | I do not know how people get .erase_region_info |
| 17:28.26 | openocdn00b | the stuff that is already there makes no sense to me |
| 17:28.45 | openocdn00b | nor the .num_erase_regions |
| 17:29.02 | openocdn00b | I think if I get those right the thing might work |
| 17:29.22 | tjtag | Well, maybe look at the datasheet for that flash |
| 17:29.55 | tjtag | but cfi should tell you, |
| 17:30.25 | tjtag | what flash chip was it ? |
| 17:35.05 | openocdn00b | it is the SST39VF1601 |
| 17:35.25 | openocdn00b | actually I just realized I cheated |
| 17:35.36 | openocdn00b | I hard coded the manufacturer and id |
| 17:35.43 | openocdn00b | that is why it recognize it |
| 17:35.50 | tjtag | heehe |
| 17:35.55 | openocdn00b | lol |
| 17:36.01 | openocdn00b | but you know why |
| 17:36.13 | tjtag | I don't think I have that flash in my program |
| 17:36.24 | openocdn00b | because cfi_info() in cf.c does not fill those values in for a chip of width 2 |
| 17:36.38 | openocdn00b | tjtag: I added it though |
| 17:37.08 | tjtag | heheh, yes I do |
| 17:37.12 | tjtag | { 0x00BF, 0x234B, size2MB, CMD_TYPE_SST, "SST39VF1601 1Mx16 BotB (2MB)" ,8,size8K, 31,size64K, 0,0, 0,0 }, |
| 17:37.33 | openocdn00b | hmm.... |
| 17:37.43 | openocdn00b | how come? where did you find it? |
| 17:37.51 | tjtag | In my program |
| 17:37.58 | openocdn00b | in which file |
| 17:38.06 | openocdn00b | is openocd your program? |
| 17:38.17 | tjtag | In the source that makes up my program Tjtag |
| 17:38.42 | openocdn00b | oh there is a program called Tjtag that is yours |
| 17:38.45 | tjtag | found on dd-wrt, its my program for debrciking routers |
| 17:38.50 | tjtag | yes |
| 17:38.53 | openocdn00b | I thought you meant openocd |
| 17:39.16 | tjtag | its a fork of wrt54g from hairy dairy maid |
| 17:39.23 | tjtag | no, sorry |
| 17:39.38 | openocdn00b | cool |
| 17:40.03 | tjtag | I just released a Tjtagv3-RC-1 with serial flash support for ATheros and Broadcom |
| 17:40.47 | tjtag | And we just got into the { 0x1438000D, 5, "LX4380"}, |
| 17:40.50 | tjtag | today |
| 17:41.01 | tjtag | its on an IP phone |
| 17:41.34 | openocdn00b | nice |
| 17:41.46 | tjtag | iTS FUN |
| 17:42.15 | tjtag | next I have to get into the IXP |
| 17:42.31 | openocdn00b | lots of work |
| 17:42.33 | openocdn00b | but fun |
| 17:43.16 | tjtag | Thats what makes it fun for me, if it was easy, it would not be any fun, I like figuring things out |
| 17:43.52 | tjtag | Took me two weeks to figure out the broadcom 5354 serial flash |
| 17:44.32 | tjtag | It would probably take some of these guys, in this forum an hour |
| 17:47.56 | openocdn00b | well that is because of experience |
| 17:48.04 | openocdn00b | now it will not take you that long either |
| 17:51.43 | openocdn00b | hmm... I see why it cannot find my chip |
| 17:52.09 | openocdn00b | It is returning cfi_info->manufacturer=0xb,cfi_info->device_id=0xea00 |
| 17:52.30 | openocdn00b | but in my entry i used a manufacturer = 0xbf |
| 17:52.42 | openocdn00b | and device_id = 234B |
| 17:52.48 | openocdn00b | ox234B |
| 17:52.59 | openocdn00b | that is what I read from the datasheet |
| 17:53.01 | openocdn00b | this is weird |
| 17:53.08 | tjtag | yep |
| 17:53.38 | openocdn00b | you see the entry you gave me from your program right |
| 17:53.46 | openocdn00b | { 0x00BF, 0x234B, size2MB, CMD_TYPE_SST, "SST39VF1601 1Mx16 BotB (2MB)" ,8,size8K, 31,size64K, 0,0, 0,0 }, |
| 17:53.46 | tjtag | yes |
| 17:53.53 | openocdn00b | BF and 234B |
| 17:54.10 | openocdn00b | so I do not know why openocd is getting a different value here |
| 17:56.37 | openocdn00b | this is going to be a pain to get it to work |
| 17:56.52 | tjtag | Its probably something simple |
| 17:57.37 | tjtag | ahh, looks like 8bit instead of 16 |
| 18:01.10 | openocdn00b | ah? |
| 18:01.26 | openocdn00b | isn't a 16bit wide? |
| 18:01.44 | tjtag | Well Im wondering why only 0xb |
| 18:01.59 | tjtag | and not 0xbf or 0x00bf |
| 18:02.46 | openocdn00b | nah it looks like it got |
| 18:02.48 | openocdn00b | value: 0x000b |
| 18:03.02 | openocdn00b | and |
| 18:03.03 | openocdn00b | address: 0x00000002, value: 0xea00 |
| 18:03.07 | tjtag | and no f, strange |
| 18:03.16 | openocdn00b | yeah |
| 18:03.22 | openocdn00b | but the id is even more strange |
| 18:03.33 | openocdn00b | very different than 234B |
| 18:06.13 | openocdn00b | I hate SST chips with their non-standard 0x2aaa and 0x5555 |
| 18:06.30 | openocdn00b | they are 3 cycles to get into cfi query |
| 18:06.36 | openocdn00b | which makes them non-standard |
| 18:14.33 | openocdn00b | tjtag: do you know who are the openOCD people in this channel? |
| 18:15.28 | tjtag | nope, I only joined up a few days ago |
| 18:18.05 | openocdn00b | :-( |
| 18:20.28 | openocdn00b | I think the latest svn is just not working |
| 18:20.59 | openocdn00b | because I have an older binary version and it detects my nand flash just fine and work perfectly |
| 18:21.05 | openocdn00b | but this latest svn doesn't |
| 18:22.34 | tjtag | hmm, well at least you know ! |
| 18:32.52 | tjtag | is that from a freash compile ? |
| 18:32.57 | tjtag | fresh |
| 18:35.18 | openocdn00b | yes |
| 18:35.44 | openocdn00b | I am going to get me the source for Open On-Chip Debugger 1.0 (2008-10-04-10:00 |
| 18:35.53 | openocdn00b | that build date/time will save me |
| 18:35.55 | tjtag | k, I guess they broke something |
| 18:36.03 | openocdn00b | yeah they sure did |
| 18:38.39 | *** join/#openjtag mgross_ (n=mgross@pool-71-117-215-6.ptldor.fios.verizon.net) |
| 18:39.19 | openocdn00b | is that april for october for the month? |
| 18:39.30 | openocdn00b | I always get confused we do it backward |
| 18:39.57 | tjtag | me to |
| 18:40.20 | tjtag | has to be tenth month |
| 18:40.33 | openocdn00b | to me too |
| 18:40.39 | tjtag | but its been updated since then |
| 18:40.48 | openocdn00b | but in america they use month/day/year for some reason |
| 18:41.02 | tjtag | Thats what Im used to :) |
| 18:41.22 | tjtag | I have been living in Ukraine now for 4 years, still messes me up |
| 18:41.28 | openocdn00b | so how come you se the tenth month? |
| 18:41.46 | openocdn00b | 04/10/2008 |
| 18:41.55 | tjtag | heheh, see I told you |
| 18:42.02 | openocdn00b | lol |
| 18:42.14 | openocdn00b | yeah I got all of them mixed too |
| 18:42.31 | tjtag | Have to run eat something, be back shortly |
| 18:42.40 | openocdn00b | ok |
| 18:42.43 | openocdn00b | see you later |
| 19:16.21 | tjtag | back |
| 20:12.27 | openocdn00b | tried older version and I get the same :-( |
| 20:12.38 | openocdn00b | oh he's gone :-( |
| 21:28.09 | rje`mac | anyone here using a jtagkey with an stm32 ? i'm having an issue with the reset not setting the program counter propperly. |