Issue with two exactly the same EvoPrimers. Help, anyone?
Hi all,
I have two EvoPrimer base units and two daughter boards. Unboxing and testing, they are ok. I swap the daughter boards, nothing unusual happens. I keep one daughter board untouched with its original firmware on it (as precaution) and used it as reference in case unusual thing happens.
I download the example with CircleOS, build it, and load it. It seems to work just fine with one base unit but not ok with the other one. Both base units seem to be able to flash, debug, etc, but on one of them I'm not able to access the peripherals on the base unit (not even turning on LEDs). At this point, I suspect that one base unit is faulty. But the funny thing is, when I put the daughter board with the untouched firmware on it, both base units are able to run just fine.
I open the case, they are of the same hardware version and components. No difference at all. I am able to flash the daughter board with the "suspected faulty" base unit without any problem, but the base unit itself is not able to run it.
So, which one is faulty? daughter board... base unit... daughter board... base unit... (I am in total confusion by now
Anyone?
Offline
#
2
2011-06-14 09:23:27Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
I'm not sure I've all understood. You can program both daughter cards, but one of them does not work with the example ? The card with the factory firmware runs on both bases ? Which example did you program, and did you try this example on the second card (it looks like a software issue).
Offline
#
3
2011-06-14 16:15:24Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
Well, let say I restore both EvoPrimer to the factory setting. Let's name it one base unit A with daughter board A, and the other as base unit B with daughter board B.
Base unit A is able to run the demo with daughter board A and B. Base unit B is able to run the demo with daughter board B only.
You say that daughter board B is faulty, but how come a faulty daughter board can run the demo? Let's say the base unit B is faulty, I could debug my application without any problem on it.
As long as base unit A stays with A, everything runs fine, and the same thing as base unit B and daughter board B.
Offline
#
4
2011-06-15 06:31:08Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
I did not say that daughter B was faulty. I supposed a software issue. Anyway, may be it is a mismatch problem between daughter B and base A. We met some connection problem cases between some target boards and some bases. Which type of daughter board you have, STM32E or STM32C ?
Offline
#
5
2011-06-15 09:23:46Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
The STM32E. As long as I don't swap them, everyone is happy. If it was connection issue, I should be able to use at least the joystick, or LEDs, but none of them are accessible, let alone the LCD.
What am I supposed top say to ST to get replacement since I don't know which one is faulty? FYI, I measured the daughter board thickness and they are exactly the same.
OOT: One design flaw I noticed from the daughter board. The JTAG/Trace connector is mirrored! I can't use trace connector to debug since I need to flip all pins. I guess I am lucky not to burn my JTAG/Trace hardware.
Offline
#
6
2011-06-15 11:45:46Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
What do you mean by mirrored ? Is the connector not conform to the schematics ? Because the schematics matches the ARM ETM & SWD 20 pins connector. FMY, which trace hardware do you use ?
Offline
#
7
2011-06-15 15:11:54Issue with two exactly the same EvoPrimers. Help, anyone?
The schematic is correct, but the PCB layout is mirrored. By looking at the daughter board, I had no idea of what orientation to plug JLink in. In fact, I had to create a converter (which basically mirrors the layout).
I have STM3210C-EVAL board which is working just fine with JLink.
Offline
#
8
2011-06-16 07:04:14Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
The target voltage sense pin on the JTAG connector on the target board is floating (pin 1). While it is connected in the schematic to "VCC3", the intention probably was to connect it to "VCC3V1". As a result, when an external plug is plugged into the JTAG connector, the emulator may detect a low voltage on the target board.
Connecting VCC to VCC3V1 on the target board solved a target low voltage sense error.
Offline
#
11
2011-06-22 10:58:36Issue with two exactly the same EvoPrimers. Help, anyone?
Re: Issue with two exactly the same EvoPrimers. Help, anyone?
What do you mean with sensing the JTAG connector?
FYI, as I wrote above, I don't have issue with debugging/flashing, but a pair of base and daughter units just don't run. Could you please explain about this VCC3V1 pin?
In fact, I had to create a converter (which basically mirrors the layout).