Re: [OpenOCD-devel] Problem using stlinkv2 with the new change for armv6 instruction

2012-02-08 Thread Peter Stuge
Jonathan Dumaresq wrote: > > you should re-check your real device ram size (0x2000???) and the > > work area size (0x4000) in your configuration. > > You are right I set it on my main cfg file but I forget to > check in the lower level of the cfg file. I thing the lower config > file should

Re: [OpenOCD-devel] generating svf files

2012-02-08 Thread Peter Stuge
Attila Kinali wrote: > Is there an easy way to generate an SVF file from an OpenOCD script? No. The closest you get is OpenOCD being able to play back an SVF. For or after libswd-induced redesign it may be relevant to consider this. I think it would be a neat feature if it will generally work.

[OpenOCD-devel] How to enter debug mode

2012-02-08 Thread jana1972
Which EJTAG Control Register Fields must be set so that a processor will enter the debug mode? I tried the following fields of the EJTAG Control Register PrAcc( bit 18) ProbEn( bit 15) ProbTrap( bit 14) and EjtagBrk( bit 12) but without success. I used a code like this ... set_instr(INST

Re: [OpenOCD-devel] FTDI automatisation PID

2012-02-08 Thread Peter Stuge
Hi, Vivien Giraud wrote: > I'm trying to make a patch that detect the pid of a plugged FTDI chip Why? I mean, what will be the benefit? > but I have some trouble with compilation. > It's say "undefined reference to sessPid", sessPid is my found PID > I'm searching it on openocd.c and I want to

Re: [OpenOCD-devel] sudo openocd Was: iMX53 support

2012-02-08 Thread Peter Stuge
Attila Kinali wrote: > > It may be necessary to log out and log in for the new setting to take > > effect. > > You need just to log in again, no log out required: > $ su - `whoami` Add an exec, to replace the current shell: exec su - `whoami` Note that this of course only applies to a single p

[OpenOCD-devel] FTDI automatisation PID

2012-02-08 Thread Vivien Giraud
Hi, I'm trying to make a patch that detect the pid of a plugged FTDI chip but I have some trouble with compilation. It's say "undefined reference to sessPid", sessPid is my found PID I'm searching it on openocd.c and I want to put it on ft2232.c. I think it's a problem with my makefile because I

Re: [OpenOCD-devel] Correct procedure for JTAG bits reading

2012-02-08 Thread 吴亚杰
> From: [email protected] > To: [email protected] > Date: Tue, 7 Feb 2012 21:31:52 +0100 > Subject: [OpenOCD-devel] Correct procedure for JTAG bits reading > > I started developing my own JTAG program for my particular needs( my MIPS CPU) > It works OK for IDCODE and IMPCOD

Re: [OpenOCD-devel] sudo openocd Was: iMX53 support

2012-02-08 Thread Attila Kinali
On Tue, 7 Feb 2012 08:29:38 + John wrote: > It may be necessary to log out and log in for the new setting to take > effect. You need just to log in again, no log out required: $ su - `whoami` Attila Kinali -- The trouble with you, Shev, is you don't say anything u

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread luca ellero
On 08/02/2012 4.49, Fabio Estevam wrote: > Hi James, > > On Mon, Feb 6, 2012 at 11:43 PM, James Robinson wrote: >> Hello, >> I see that there is an imx53.cfg in the target directory. Is anyone >> using this with a board configuration? I am trying to connect to an >> iMX53qsb and I am getting the

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread John
On Wed, Feb 08, 2012 at 06:57:23AM -0500, James Robinson wrote: > >From the olimex data sheet: > "VREF ? voltage follower input for the output buffers adjust JTAG signals > as per your target board voltage levels" Where is that data sheet, please? I didn't find it on the olimex we site. I would

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread Fabio Estevam
On Wed, Feb 8, 2012 at 10:29 AM, James Robinson wrote: > Fabio, > I just did a pin check on arm-usb-ocd and pin 1 and 2 are tied > together (0 ohms) . I would be VERY careful plugging it into our eval > boads. On my imx53qsb, it would short (SH20) the 1.8V bus to the 3.3V > bus. I do see that on t

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread James Robinson
Fabio, I just did a pin check on arm-usb-ocd and pin 1 and 2 are tied together (0 ohms) . I would be VERY careful plugging it into our eval boads. On my imx53qsb, it would short (SH20) the 1.8V bus to the 3.3V bus. I do see that on the schematic that it is possible to remove a short (SH20) and conn

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread Fabio Estevam
On Wed, Feb 8, 2012 at 9:41 AM, James Robinson wrote: > Fabio, > It looks some of the differences in the JTAG on the imx28evk and the > imx53qsb are: > 1) Reference voltage is 3.3 on imx28evk and 1.8 on the imx53qsb. Yes, we need to make sure our interfaces support 1.8V, > 2) pin 11 JTAG_TRST on

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread James Robinson
I was looking over the schematic for my 53qsb and saw that pin 1 and pin2 are running at different voltages. Is this going to be an issue with the arm-usb-ocd? >From the olimex data sheet: "VREF – voltage follower input for the output buffers adjust JTAG signals as per your target board voltage lev

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread James Robinson
Fabio, It looks some of the differences in the JTAG on the imx28evk and the imx53qsb are: 1) Reference voltage is 3.3 on imx28evk and 1.8 on the imx53qsb. 2) pin 11 JTAG_TRST on the imx28evk is going to the cpu and on the imx53qsb it is pulled to ground. 3) pin 17 JTAG_DE is floating on the imx2ev

Re: [OpenOCD-devel] iMX53 support.

2012-02-08 Thread Fabio Estevam
On Wed, Feb 8, 2012 at 2:30 AM, Marek Vasut wrote: > I don't have mx51evk, sorry. Ok, if only the efika JTAG connector schematics could be shared, then I can compare it against mx51evk JTAG. Right now, I am not able to read/write to any register because the mx51 is not halted, so I would like t