STM CircleOS forum / My Device have some problem(OPI Driver)

LEEHwaYong · 2007-11-08 07:52:11

I uploaded example what in the library examples folder for look at interworking of driver-library.
( \raisonance\lib\st32f10x_lib\example\usart\example1\ )

Example1 of usart is hasn't rprj. So i make build-project with use 'main.c'.

Interrupt functions are used at 'st32f10x_lib\ project' and

libraries are used source file in 'st32f10x_lib\inc' and 'st32f10x_lib\src'.

After copied all of source file, maked new project.

when making project, i was selected to no use deault ST library.

And edited some build option accociated with debug.

It was not error with compiling but poped error message like below.

(
unable to read IdCode
Please check that the target is connected.
)

After that action, all of debugging program was'nt work(command line uploader tool, ride7)

What can i do for this case?

Was embedded in flash area broken?

Please help me~~

Francis · 2007-11-08 10:08:31

The USB connection is not correct. Very often, we plug the cable to the wrong USB connector on the Primer (teh RLink connector is close to the Irda footprint, NOT the orange button).
Is it your problem?

Francis · 2007-11-08 13:47:32

My colleagues just told me that I was wrong. This message means that there is a problem within the JTAG connection between the embedded RLink and the STM32.... It could be a hardware problem (a JTAG pin that is not properly soldered between the RLink (ST72651) and the STM32.

Francis · 2007-11-08 14:12:10

Just to check that there is no problem with RLink, could you try to get the serial number of the embedded RLink (in the Debug| RLink options, you have a push button to launch this request).

LEEHwaYong · 2007-11-09 00:21:50

Francis :
The USB connection is not correct. Very often, we plug the cable to the wrong USB connector on the Primer (teh RLink connector is close to the Irda footprint, NOT the orange button).
Is it your problem?

Of course USB connection is corrected(at the debug port), and used right USB cable.
And power was correctly on.
Thank you for apply.

LEEHwaYong · 2007-11-09 00:28:08

Francis :
My colleagues just told me that I was wrong. This message means that there is a problem within the JTAG connection between the embedded RLink and the STM32.... It could be a hardware problem (a JTAG pin that is not properly soldered between the RLink (ST72651) and the STM32.

Oh, I'm affraid that.Because i have not hardware debugger.

It worked correctly before at another project building and test.

But i affraid what i moved battery pin when power is on.

If Jtag has problem. What can i do for this case?

LEEHwaYong · 2007-11-09 00:45:54

Francis :
Just to check that there is no problem with RLink, could you try to get the serial number of the embedded RLink (in the Debug| RLink options, you have a push button to launch this request).

In advanced options of project's properties, there are six button about jtag like next.

1. View Rlink REva jumpers configuration for STM3x
2. Connect to Rlink and read serial number
3. Read target IDs and option bytes (check connection)
4. Erase target now
5. write target FLASH now!
6. Dump target FLASH to Hex

BUT, anyone of these are not working. Only error message is pop-up like this

'Unable to read IdCode'.

I looked couple of time USB connection and power of machine. It was fine.

is JTAG hardware problem?

Francis · 2007-11-09 07:17:28

No... the problem is not with JTAG, but with USB.
It could be:
1. the USB connector itself (I know that sometimes the factory encounter some problems with soldering these connectors)
2. or "something" (probably a pin that is not properly soldered) on the ST72F651 device (the embedded RLink).
If you have a good binocular and you can check them... if not, you will have to ship it back to your distributor.

LEEHwaYong · 2007-11-09 08:24:11

Francis :
No... the problem is not with JTAG, but with USB.
It could be:
1. the USB connector itself (I know that sometimes the factory encounter some problems with soldering these connectors)
2. or "something" (probably a pin that is not properly soldered) on the ST72F651 device (the embedded RLink).
If you have a good binocular and you can check them... if not, you will have to ship it back to your distributor.

When i buyed this machine, it works correctly.
And i tested with another USB cable.But it works not correctly now too.

In the case of 2, i have not checking tools.
So i will send my machine to distributor and take a service.

Very Very Thank you for your apply~!

cederom · 2010-01-15 02:48:55

hey ive got the same problem!

on the one usb connector on my laptop there is no connection to the rlink at all.
on the other connector rlink can be accessed and serial can be read but no access to the target device is available, I get:

"Cortex Drv error: Unable to read IdCode. Please check that target is connected."

This happens in both of my Primer2 - one required U17 to be replaced, but the secon one was working fine. Now both have IdCode error :-(

Please advise,
Tomek

# 1 2007-11-08 07:52:11 My Device have some problem(OPI Driver)

My Device have some problem(OPI Driver)

# 2 2007-11-08 10:08:31 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

# 3 2007-11-08 13:47:32 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

# 4 2007-11-08 14:12:10 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

# 5 2007-11-09 00:21:50 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

Francis :

# 6 2007-11-09 00:28:08 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

Francis :

# 7 2007-11-09 00:45:54 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

Francis :

# 8 2007-11-09 07:17:28 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

# 9 2007-11-09 08:24:11 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

Francis :

# 10 2010-01-15 02:48:55 My Device have some problem(OPI Driver)

Re: My Device have some problem(OPI Driver)

Board footer