Forum : ST7/STM8
| Post Information | Post |
|---|---|
|
October 31, 2007 - 2:35am
|
I recently took delivery of a REva w/ ST7263B-DB. In working through the ST7 Quick Start example (switches and LEDs), I seem to be having difficulty with the "Debug > Start" step. Despite having the Rlink power and regulator jumpers in the appropriate positions (both power jumpers in the "topmost" position, RIDE seems to believe that the ST7263B daughter board is unpowered as I get the following message upon commencing with "Debug > Start": Target CPU is not powered. This daughterboard does not appear to be 1.8V and therefore would not require separation of the Rlink and REva boards. The RLink "Power" and REva "VDD" LEDs are both lit. Anyone else encounter this and have insights on triaging? |
Hi,
This looks like the connections between the RLink and the REva have been damaged. It has never happened before, but who knows what happens during transportation...?
Can you please measure the voltage between GND and VCC (on both sides of the wrapping zone) with a voltmeter? (this is the power that goes to the ST7263B)
Please also measure the voltage between pins 3 and 7 of the 10-pins ICC connector of the RLink. (this is the power that goes to the RLink IOs)
If you measure two different values, (good for REva, wrong for RLink, I guess) then you should be able to solve the problem by plugging the 10-pins ICC ribbon cable between the ICC connectors of the RLink and the REva.
If you measure two wrong values (like 0.5V), then you'll probably be able to work by powering the board with an external power on the jack connector.
If you measure two correct values (like 5V) and still get the message, then there is probably a problem in the RLink. We'd have to exchange the whole board.
If you are not sure, just tell us what you measure and we'll give you more hints.
Best Regards,
Vincent
In the wrapping zone, I get 4.78 V between all combination of GND and VCC vias.
Between pins 3 and 7 of the HE10 2 x 5 ICC connector, I read 4.75 V.
If I bridge the RLink and REva boards with the supplied 10-pin cable, the debugger is successfully able to attach and run the Quick Start exaple (though LED D6 seems inoperative when switch S3 is asserted). However, in this mode, it only seems to work intermittently. The first time though I saw:
Emulator Driver
Initializing the emulator...
Emulator Driver
Downloading code...
Please Wait...
Erasing FLASH.
and then successfully started a debug session. After stopping the debug session, I see:
OPI Driver
Unable to retrieve context from the monitor.
OPI Driver
No response from the DTC
OPI Driver
No response from the DTC
Terminating debug session.
Then, the second time I attempt to start a debug session, I get the following error:
OPI Driver
This version of the software only handles RLink with firmware version up to 0.0.255.
If I quit RIDE, disconnect the RLink board's USB cable and then reconnect and restart RIDE, I can connect again, but not 100% of the time.
Recommendations? Next steps?
Hi,
The fact that the cable makes things better confirms that the ICC connections between the REva and the RLink are damaged. There could also be problems for the power signals that go through these bridges. I suggest you use both the ribbon cable and an external power. (change the jumpers accordingly) You can even break the RLink apart from the REva, to avoid any interference due to an intermittent connection.
If there are still problems, then we'll need more information on your system. (Serial number of RLink, versions of RIDE and Windows, etc.) Then, please answer this form and send the answers to :
http://www.raisonance.com/Forum/punbb/viewtopic.php?id=2231
Best Regards,
Vincent