MC13192-SARD - Accelerometer Program ... Please help a desparate group of students!!

[Charleson]

Help!  We're college students trying to graduate!

I have downloaded the accelerometer firmware (Accelerometer V_2) to both of my MC13192-SARD boards.  How do you set which board is the reciever and which board is the transmitter.   I know I have to press a combination of the buttons on the boards.  How do you get them to talk to each other?

Please Help Us!!

Group 17!!!

[Alban]

Hello Group 17,

May be you could tell us which steps you already did in term of research.
We would also need to know which datasheet you have reviewed.

This way the group here can advise a way forward... But we need to know what your investigations have been.

Alban.

[Alban]

For instance,

A Read The Book like:

MC13192SARDUG
Sensor Applications Reference Design User's Guide 

And the AN3230 is given as dedicated to explain how to do the setup...

Alban.

Message Edited by Alban on 2007-04-07 10:09 PM

[Charleson]

Hi!

So we've already been in contact with Freescale technical support and this is what he suggested:

"The way the Accelerometer works is very simple; you can get the data from the accelerometer board using HyperTerminal in the receiver board. Just follow these steps:
1)      Download the accelerometer firmware to both boards
2)      Press button 1 in transmitter board
3)      Connect receiver board to the serial port
4)      Open Hyperterminal (or a program that allows you to see the printed bytes of the serial) at 38400 8N1N
5)      Press ‘V’ (Capital V)
6)      The board will print something like this: xfypzº; this means:
x(the value of x axis) y(the value of y axis) z(the value of z axis)
(you will see some “garbage” as data because hypertminal can not represent the actual value of the byte)

 So I suggest you to make simple program in any language like C, Java or Visual Basic and store the values in a txt file.
I hope this information helps. Please let me know if you have another question. Have a nice day!"

So... we have successfully downloaded the firmware and written the computer program but we can't set the boards to be transmitter and reciever (steps 2 and 3), thus preventing us from even using hyperterminal to see if this process works (step 4, 5, and 6).

We tried the above procedure (steps 2-6) but nothing appears on the hyperterminal program when we press Capital V.

Please help us graduate!  Thanks!!!

Group 17!!!!

[peg]

Hi Charleson,

I just did what you are trying to do from scratch without any problem.

This is what I did.

1. Programme both boards with the output of Accelerometer V2_SE.mcp

2. Connect one board to a PC running a terminal emulator at 38k4 N81

3. Turn on this board, nothing happens.

4. Turn on the other board whilst holding down any one of the pusbuttons. This board will rapid flash LED 4

5. LED 3 on reciever board connected to PC will now rapid flash and data will be transmitted to PC.

If this doesn't work try the following:

A. Disconnect serial cable.

B. Take board 1 and turn on with one button depressed, LED 4 should flash.

C. Turn it off

D. Turn it back on without pressing any buttons, only the power LED should be on. Leave it on.

E. Take board 2 and turn it on without pressing a button, only power LED should be on.

F. Turn it off.

G. Turn board 2 on whilst pressing any pusbutton, LED 4 should flash and LED 3 on board 1 should start to flash also.

If this does not happen there is no use trying to connect a PC etc.

In the A to G test which board is one or two does not matter.

Let us know what you find with these procedures.

[Charleson]

Hi!

So I followed the first protocol and everything worked fine until I turned on board 2... LED 3 failed to start flashing on board 1... and then the LED 4 on board two stop blinking after a few seconds.  Therefore... I followed the A through G protocol.  Everything was working fine until... again... LED 3 failed to start flashing on board 1.

Is this because we downloaded the firmware wrong (i.e. I used the USB Multilink Interface with Codewarrior and.. opened Accelerometer V2_SE project... pressed the green compile button... another screen popped up showing source and a bunch of run time stuff... after the runtime stuff stopped I unplugged the 6 pin ribbon cable and closed the runtime pop up window and assumed everything was downloaded... I did this for both boards)?  Is it a hardware problem?

We heard that maybe we dont have the right HCS08 V5.1 license (professional vs. special edition)?  Could this be the problem?

Please Help Us!  We are desperate!

Thank you so much for you help!

Group 17!!!

[peg]

Hi,

Can you get both boards to flash LED 4 by turning them on with a butten depressed?

It seems as though you are not actually transmitting but other things don't make sense.

Once I start one as master and it flashes LED 4 I can't get LED 4 to stop flashing no matter what I do (short of turning it off). If I fire up a second one as reciever LED 3 flashes and if I put too much distance between them then there is no effect on LED 4 but LED 3 will stop either on or off but closing the distance simply restores the flashing of LED 3.

The procedure you have outlined for programming them was exactly what I did.

However, I used Codewarrior 3.1 as I know that this is what this code expects. I will give it a try from 5.1 later.

Special edition is OK, that is what the SE is on the end of the filename for, it is a version particularly designed for compiling with special edition.

[peg]

Hi,

I compiled the Accel project using CW5.1 and there were no complaints, errors or warnings.

Just did everything the same as 3.1 and it works the same as well!

So I don't really understand what you are doing wrong.

[Charleson]

Ok...

So... we got a new set of boards and the exact same thing is happening.  For both the accelerometer V2 program AND the TRIAX trial accelerometer program... the reciever board LED3 will not blink - in fact - nothing happens on the reciever board... do you have any idea what could be causing this?  Please.  This is our last chance.

Group 17

[peg]

Hi,

I still don't know what you are doing wrong.

I have included the s19 file here that I have compiled with CW5.1

Download this into both boards and see what happens.

[Charleson]

Hi!

So... our embedded bootloader doesn't work (it says operation timeout) so we can't even upload this .S19 file.  We've tried numerous ways of getting this to work.  I've attached what Fresscale Technical Support told us to do.  Do you have any other idea what we could possibly do to get this to work.  Is there anyway you could walk me through this process?

Group 17

[Charleson]

Hi,

Sorry to keep bothering you... but... is there anyway we can get the TRIAX demo to start working again?  Is there anyway we can erase what we downloaded and then put the TRIAX demo software back on the boards.  We want to be able to at least show the demo.  Thanks.

Group 17

[peg]

Hi,

You said you had a multilink BDM before, so why are you concerned that you have lost the embedded bootloader?

The file I posted is meant to be downloaded via BDM.

I'm confused by your last posting. We have been talking about the firmware that operates with the Triax software all along, haven't we?

The assistance from Freescale is irrelevant until you get some flashing LED's.

Also I have not experienced the need to sent anything in order to initiate the data stream.

[Charleson]

Hi!

Is there anyway we could reset the board memory back to the way it was when it was manufactured and shipped?  Is there like a restore procedure?  At this point, all we want is the demo trial version to work.  Thank you so much for the time you have taken to help us out!

Group 17!

[peg]

Hi,

Yes there is! That is what we are trying to do already!

I think that the boards are actually shipped with the serial monitor in it as well, but if you can't get this to go on its own its no use trying to load the serial monitor and then the application.

[Charleson]

Hi,

Excuse me for my ignorance but what do you mean by serial monitor?  I'm just trying to figure out your last response.  Thank you so much!

Group 17!

[peg]

Hi G17,

By "serial monitor" I meant "embedded serial bootloader/monitor", sorry!

This is some code that gives functionality like a BDM module via the serial port. It resides in block protected flash.

Demo boards and the like usually have it preloaded for people that don't have a BDM adapter. If you have one you likely erase it the first time you use the BDM module.

They only have two uses (as I see it)

1. For people too poor to buy a BDM adapter

2. For products that need to be field upgraded by people (users?) that don't have a BDM adapter.

As I don't believe you are either of these two I think you should just concentrate on getting the application in there via the BDM and forget the bootloader/monitor.

[Charleson]

Hi!

Someone suggested that we should remove the jumpers from the reciever board.  Should we do this?  What are jumpers, where are they, and what are they for anyway?  Thanks! Only a week left!!!!

Group 17!

[peg]

Hi,

In the middle of the SARD board there is a row of double pins, 13 pins long. Some of these are shorted together by "jumpers".

On both my boards the fitted jumpers are the same.

One end is marked with a '1'.

If we call the positions 1 to 13, I have 1, 2 and 6 fitted. No time to check now, but from memory this is just connecting the analogue outputs of the 3 accelerometers to the GB's analogue inputs.

[J2MEJediMaster]

Bear with me because I'm familiar with the HC(S)12 CodeWarrior, and there's bound to be differences between it and the HC(S)08 version of CodeWarrior. I'm just trying to confirm that your download went correctly. Did you use the hardware target, or the simulator target? If the hardware target, did you get any messages where it erased memory and downloaded the firmware to Flash?

---Tom