**** BEGIN LOGGING AT Mon May 04 02:59:57 2009 May 04 14:49:30 keesj: ping May 04 16:29:40 yo May 04 16:38:34 keesj: If I remember correctly, you used Saleae for OMAP3 JTAG debugging? May 04 16:39:10 keesj: There is now some discussion at beagle ml that Saleae doesn't Support 1.8V. Any idea? May 04 16:41:30 keesj: http://groups.google.com/group/beagleboard/msg/a3f44b7ce5be9b33 May 04 16:47:33 dirk2: yes I saw that disc, it was monitoring the jtag signals indeed, May 04 16:49:21 zeroplus looks good May 04 16:49:52 for zeroplus there are a lot of devices, and I can't find the prices. They link to resellers May 04 16:50:22 the jtag signals: At 1.8V level or behind any level shifters? May 04 16:52:16 btw: Are you on the Saleae Linux notification list? Any news regarding Saleae and Linux support? May 04 16:56:19 dirk2: but the thread initialy was not about logic analyzer if you ask me May 04 16:57:11 I started reverse engineering the protocol but I don't have a vista machine any more (still have the traces) May 04 16:57:33 let met ask them again. last time they said "comming" bug that is way to long ago May 04 16:59:38 keesj: Sorry, I just wanted to know if you can remember if you used Saleae with 1.8V JTAG signals (i.e. proving that statement at mailing list is wrong) or if you measured at some other voltage levels? May 04 17:02:59 the specs here http://www.saleae.com/logic/specs/# say it should not work but this cleary is not true May 04 17:05:25 dirk2: the openocd discs just makes me even like openocd less May 04 17:23:19 keesj: yes, I looked at the code and it is not easy to understand. But Magnus does really help! May 04 17:24:42 keesj: and, while I haven't read all of Zach's discussion, it seems he has an idea what to improve May 04 19:16:58 Hi, I request some help. I probably have ytouble installing drivers for ft2232 on ubuntu, since openocd tell me " No valid jtag interface found (ft2232)". Can anyone put some light on this problem? May 04 19:17:28 Im using a USB-TINY jtag from Olimex. May 04 19:19:43 try as root May 04 19:22:14 As root didnt help. May 04 19:22:29 I dont have /proc/usb/devices, since my system uses udev. May 04 19:22:34 Is that a problem? May 04 19:29:09 Ah, I found a way to see the usb devices, and I see that " Driver=(none)" for the Jtag Tiny. May 04 19:29:51 Now I need a way to tell what driver it should use... May 04 20:38:22 o you need to mount the usbfs .... May 04 20:38:29 that is that libusb is using May 04 20:53:42 Hmm, I did, still no good result. May 04 20:54:26 keesj: Mount point is /proc/bus/usb/, right? May 04 21:46:56 I b back 2morrow May 04 23:49:12 Hello. May 04 23:49:46 Question: Running the Segger Jlink "Beta Software for Linux" while connected to my target hardware tells me I have two devices with a total IRLen of 16. May 04 23:50:01 Does that mean that the sum of the IRs of the two devices is 16? May 04 23:50:56 sounds like it May 04 23:52:16 It also told me the IDs of the two devices. Any idea where I could look them up to determine the proper jtag_device lines for them? May 04 23:52:37 I know the part number of the chip, but I can't find datasheets for it anywhere. May 04 23:53:12 One device is an arm946ij-s, the other is a DSP that I don't care to touch. May 04 23:54:08 i think you can figure out arm part from the manufacturer id May 04 23:54:29 are there openocd folks here? May 04 23:54:51 # Id of device #0: 0x29DD202B May 05 00:00:01 and the other one? May 05 00:00:10 # Id of device #1: 0x25A6802B May 05 00:02:13 hmm this one looks like arm but i seem to get arm10... May 05 00:02:42 The chip is an NXP cellular baseband processor. May 05 00:02:59 104Mhz Arm946ejs May 05 00:03:33 http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/3843.html May 05 00:04:33 i wonder if there was a glitch May 05 00:04:42 and it should read 2596802B May 05 00:05:01 no wait... that's still not 946 May 05 00:05:04 No chance the other one is the ARM? May 05 00:05:14 pretty unlikely May 05 00:05:26 http://www.nxp.com/#/aip/aip=[aip=429]|pp=[t=aip,i=429] May 05 00:05:28 that technote says arms should have 0 in bit 27 May 05 00:05:58 do you have a datasheet? May 05 00:06:10 no. May 05 00:06:15 pity May 05 00:06:24 The link I just sent you is the closest thing I have to a datasheet. May 05 00:09:51 And, now I feel dumb. May 05 00:10:16 The "JTAG Debug Application Note" from the module provider includes an openocd config file in the pdf. May 05 00:10:39 heh May 05 00:10:46 Granted, it makes the assumption of an "Amontec JTAGkey A", but that's easy enough to change. May 05 00:11:03 manufacturer id matches 00000010101 philips Philips Semi. (Signetics) May 05 00:11:32 hmm, although both ids have the same manuf id... May 05 00:11:46 so i guess dsp is also from philips? May 05 00:11:50 er, nxp May 05 00:12:01 It's a single-chip with two devices. May 05 00:12:05 ah May 05 00:14:03 Has jlink support been removed from the latest openocd? May 05 00:14:53 i think it's in a state of flux May 05 00:15:39 it was working for some people... not working for others... then someone rewrote the whole thing or something like that May 05 00:17:11 I just don't see it listed after doing ./configure --help May 05 00:17:43 weird May 05 00:18:14 AS_HELP_STRING([--enable-jlink], [Enable building support for the Segger J-Link JTAG Programmer]), May 05 00:20:31 Oh well. I'll wait for my co-worker to arrive with the Olimex probe tomorrow and try it then. May 05 00:20:57 Thanks. May 05 00:22:13 Iyi geceler May 05 00:39:05 hello, I'm new to openocd, I just got a signalyzer JTAG and I will be using it on a new open hardware imx27 board we're developing, but for now it's hooked up do an ilogic dev board. I pulled and compiled the latest SVN, and that worked. openocd started OK. May 05 00:39:58 Now I want to load a redboot image to ram, but before that I'd just like to test out the ram. Is the some sort of memory info or memory test with openocd? May 05 00:41:10 there is mdw May 05 00:42:11 ram info is not available using jtag... so you either have to know it from some other means May 05 00:42:18 so I guess I need to know where the external ram is mapped to? May 05 00:42:43 yes May 05 00:47:31 the manual says it's at 0xA000_0000, and when I look there I get stuff back. May 05 00:48:51 in the help fast_load_image says "same args as load_image", but I don't see an entry for load_image? May 05 00:50:15 i think it's load binary May 05 00:50:56 I lied, I do see load_image May 05 00:57:35 I get this error, May 05 00:57:39 > load_image /home/raid5/imx27env/redboot_200719/bin/mx27ads_redboot.bin 0xA000_1000 May 05 00:57:40 memory read caused data abort (address: 0xffff4c00, size: 0x4, count: 0x6) May 05 00:57:42 no working area available, falling back to memory writes May 05 00:57:43 TAP imx27.cpu: May 05 00:57:45 value captured during scan didn't pass the requested check: May 05 00:57:46 captured: 0x03 check_value: 0x01 check_mask: 0x0F May 05 00:57:48 in_handler: w/o "in_value", mismatch in SIR May 05 00:57:49 Runtime error, file "command.c", line 456: May 05 01:02:06 weird address May 05 01:02:32 what's weird? May 05 01:06:58 0xffff4c00 May 05 01:13:10 yeah, I don't know where that came from **** ENDING LOGGING AT Tue May 05 02:59:57 2009