IsoPodV2 with PCMaster problem

[pgruebele]

Hi,

I recently got my IsoPodV2 exchanged because of some AD problems and now I am having a completely different problem.

I used CodeWarrior with JTAG and PCMaster (from SDK) with the serial cable to talk to the IsoPodV2.

With the board that I returned, PCMaster worked 100%, but with this new board I always get a "Cannot detect the board information! The communication will be paused." error.

It appears that every time I try to connect PCMaster to the new IsoPodV2, the IsoPodV2 resets, therefore never responding to the PCMaster serial command.

Anyway, this did not happen with the previous IsoPodV2 that I sent in. From the NewMicros docs I know that the DTR signal can generate resets. Perhaps this is it. I am using the NewMicros serial cable so this signal must be connected.

I just don't understand why this worked with the previous IsoPodV2 that I had and not with this new one. Has there been any change to the logic/layout in the IsoPodV2? Or was the old one somehow immune to this happening?

Anyway, I never need to reset the IsoPodV2 through the serial port, so I can somehow disable this feature? Are others using the IsoPodV2 with PCMaster?

Thanks

Philip Gruebele

[nmitech]

I never need to reset the IsoPodV2 through the serial port, so I can somehow disable this feature?

I wonder If you can reconfigure the DTR to low on the PCMaster and save the new configuration so that next time you run the PCMaster it will not reset the IsoPod.

Or use the exacto knife to lift the plastic pin lock and remove the ATN wire off the serial cable shell holder.

I just don't understand why this worked with the previous IsoPodV2 that I had and not with this new one. Has there been any change to the logic/layout in the IsoPodV2?

No change on the Ispod production V2. This is mystery, i can't tell until i have both of them here to check out.

[pgruebele]

Hi,

I have a prototype board and removed jumper J2 from it as a test. You web site has no schematic for this board posted, but I guessed that this would disable serial based resets, so I tried it. When I do this, the board no longer resets when I try to connect using PCMaster, but PCMaster still says it cannot communicate with the board. Serial communication seems to be cut completely.

Can you explain to me what J2 does?

Also, how does the IsoPod get reset from the serial signals. When you say "ATN", which pint is that on the DB9 incoming connector? I am not aware that there is an ATN wire in the serial protocol....

Thanks

Philip

[nmitech]

J2 jumper on the prototype board (interface board) when connects it allows us to use the DTR signal from the PC serial to reset the IsoPod by pressing the ALT+T keys twice to toggle the reset signal. You can remove the jumper J2 if you do not want to use the DTR signal for this purpose.

The schematic of the Interface board_V1 is on the download page. The circuit are identical with Interface board V2. The difference are the mouting holes location and instead of J2 on V2 it labeled J1 on V1. I will try to add the schematic of the interface board for V2 soon.

[pgruebele]

So if DTR/ATN is the cause of the reset then removing this jumper should get rid of this problem, right?

Given the fact that this problem did not exist with the last board I had and that is persists when I remove J2, is it probable that the IsoPod I have is defective?

Don't know what else to do or test...

Thanks

Philip

[nmitech]

Since I am not familiar with the PCmaster communication, therefore i can not make any more comment or suggestion on this. One thing I know from your very first post, you have a JTAG cable, CodeWarrior software, and SDK software on CD. With these tools, you can check the serial port of the Isopod without using the PCmaster software. Here is how,

Open the Serial_Bootloader.mcp project from the SDK disk by using the CodeWarrior to compile it and download (flash) via the JTAG interface. Once you have have the serial_bootloader code flashed, remove the Jtag cable off the isopod, run the Hyperterminal program (or NMITerm) and set the baudrate for 115,200. When you reset the IsoPod, you will see message:
"(c)2001 motorola serial bootloader V1.x"
Everytime you hit the Space Bar on the keyboard it will send an error message to the screen. If you see these messages, the IsoPod serial is responded properly. Ignoring the Hyperterminal DTR set high or low and ignoring jumper J2 on the interface board is open or close, you will see those messages each time you reset (or cycle the power) and press the Space Bar key to get the response from the serial.

If you can't get this working, i will send you new code to test during the office hour to determine if the isopod is defective or not.

[pgruebele]

I loaded this boot loader and I do get the

"(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3" string in NIMTerm under the following conditions:

1. I reset the IsoPOD
2. I go to "settings" and either change any of the settins or leave them the same and click "OK"

I do not get the version message/reset when I type stuff in.

I don't know why I get a reset/version when I just click OK on the settings dialog... However, if this means that the serial port is working, then can you tell me specifically how to disable the reset via serial port functionality on the IsoPod or the breakout board so that I can test with NMITerm and then with PCMAster?

Thanks

Philip

[nmitech]

how to disable the reset via serial port functionality on the IsoPod or the breakout board so that I can test with NMITerm and then with PCMAster?

Just removed jumper J2 on your interface board.


"(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3"

This means the Serial Out is working. If you hit the Space Bar key and it responds with,

Error # 0002
Restarting.

(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3

This means the Serial In is also working.

Here is a leds test program for you to try. No JTAG requires once you have the serial bootloader code loaded. Download and unzip the srecord file from the link below,
http://www.newmicros.com/temp/v2leds.zip

Connect your serial cable,

Run the NMITerm and change the Serial Comport and Ascii setting in the properties box as below,

First, start from
Serial comport and set the baudrate: 115,200
Click on APPLY button, then go to Ascii Setting tab,
ASCII Receiving:
Wrap lines that exceed terminal width: Optional
Character Pacing: unchecked box
Line Pacing: Decimal 0

ASCII Sending:
Send Line End with Line Feed: unchecked box
Line Delay: 100ms
Character Delay: 0

Click on Apply button then click OK button.

Now turn on the IsoPod power, you will see this message,
"(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3"
Now click on the SEND icon and look for the v2leds.s file you just downloaded to send. You will see square boxes display on the terminal while the program is flashing via serial. It take couple seconds and it will automactic run the program as soon as it is finish flashing. This is what you will see if you setup everything correctly,

(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3

Loaded 0x0380 Program and 0x0079 Data words.
Application started.

LED Test (serial bootloader version) ready
1=RED ON, 2=RED OFF, 3=Yellow ON, 4=Yellow OFF, 5=Green ON, 6=Green OFF


press 2 to turn off the red led and 1 to turn it back on, etc...

If yours is worked as described above, your serial port is functioning properly.

[pgruebele]

I get the "(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3" every time I reset the board.

I do not get any response to hitting the space bar (or any other keys, including enter, for that matter). Does this mean that serial out is not working?

Thanks

Philip

[nmitech]

After the bootloader V1.3 message is displayed you need to wait for 10 seconds before you start to enter the space bar on the keyboard. Note, some keys are ignored by the serial bootloader. Please use the space bar key for this test only. But i would like you to try the v2leds.s test srecord i posted earlier. If the leds don't response accordingly to key number 1,2, 3,4,5,or 6 then the serial input is defectived.

[pgruebele]

I tried the following:

1. I download your s file
2. I set all the NMITerm settings like you said
3. I powered up IsoPOD
4. I got the "(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3" message
5. I clicked the "Send File" button and selected the S file
6. the NMITerm says "Transmitting Data ... Press any key to Cancel. I do not press any keys, but no squares are printed out by NMITerm.
7. I press 1 or 2 but nothing happens
8. I reset the IsoPOD and get the "(c) 2000-2001 Motorola Inc. S-Record loader. Version 1.3" message again...

So it does not appear to work...

Philip

[nmitech]

The Serial Input is not working. Before you send the IsoPod back, please do this test to check out the serial cable and your PC serial ouput.

Remove the IsoPod off the interface board.

Use a piece of wire wrapping and connects (short out) on pin 1(sout) & pin 2(sin) on J4 of the interface board.

Connect the serial cable to the interface board

Plug in the power to the interface board

Run NMITerm program and enter any alphanumerical key and it should echo back on the terminal program each key you entered.

If it echoes back, the IsoPod Serial Input is defectived for sure.

If it does not echo back, use the DVM meter and ohm out the serial cable and serial connection on the interface board. If it has all the continuities as expected then your PC serial comport is bad, or vice versa.

To return for repair, please email to nmiproduction@newmicros.com to obtain a RMA number and instruction to return

[pgruebele]

Yes, it echos back when shorting and does not when not shorting, so the cable and interface board appear to be OK....

Do you give me an RMA or how does that work?

Thanks

Philip

[nmitech]

To return for repair, please email to NMI's Production Dept. at nmiproduction@newmicros.com to obtain a RMA number and instruction to return