PNP Hack on Jaguar board

[Kennybug]

Here is the PNP USB modification if you don't use the Opto-isolator circuits:

See the attached image...

The blue hand drawn line is to connect the MCU ground and the USB ground together, just use a piece of jumper wire soldered to the two pads of U8 and U9.

The yellow hand drawn lines show the connection points for the PNP transistor (I used a 2N3906 transistor). This is necessary to pull the RX line of the MCU high if the USB cable isn't plugged in.

PNP Transistor connections:
The Emitter goes to the +5v side of R60.
The Collector goes to the RX side of R60 or the RX pad of U8.
The Base goes to 5v-USB side of R56 (this is powered only when the USB cable is plugged in.)

I had did the hack with 2n3906. My prelim test shows the FTDI chip still not talk with the MCU.
Only the sending LED flash. will take time to check soldering and trace tomorrow.

[Fred]

You don't need the hack to talk to the serial monitor, only to the firmware. So you can use a serial terminal to send prerolled SM packets to verify comms before you do the transistor thing.

[Kennybug]

Thanks Fred.
I did not hv a native serial port on all my computers. I will take time to install a HL-340 serial2USB driver on my debian tonight. CuteCom and the serial.mon.reset stuffs are ready.

I always did my development on sleepy mid nights (the only silent moment @home when kid slept).
You can see that i havn't link up the RX & TX pads to the FDTI

But i am still quite confused that you said.
You said i do not need the PNP to talk SM.
So, should I remove it for testing SM & loading firmware to MCU?

[Fred]

I did not hv a native serial port on all my computers. I will take time to install a HL-340 serial2USB driver on my debian tonight.

This doesn't make sense. Puma = ft232r = ftd_sio driver built into all kernels for ages. It's automatic.

CuteCom and the serial.mon.reset stuffs are ready.

Cool

I always did my development on sleepy mid nights (the only silent moment @home when kid slept). :oops:
You can see that i havn't link up the RX & TX pads to the FDTI :lol2:

LOL! Good that you found it :--)

You said i do not need the PNP to talk SM.

It's true.

So, should I remove it for testing SM & loading firmware to MCU?

Not if you think it's right. You could try lifting the pnp leg off of the cpu rx if you think that it's a problem, but try with it in place first.

[Kennybug]

bad news.

I have the s19 SM loaded to MCU. Hiwave said the device is running.
TX/RX pads connected to FDTI chip.
shell dmsg shown the FDTI chip worked as tty/USB0

Both CuteCom & FreeEMS Loader cannot talk to the SM

only 1 led flashing.

[Fred]

Which LED? If you loaded firmware to it, then there i no SM and I'm surprised that it works at all. If you loaded SM, then there is no code and you'll have to be in load mode or it will do nothing. If you loaded both (unlikely) then it should do something either way. Where did you get the file to load from?

Try:

A) verify the sm image
B) load the firmware without erasing the sm
C) Check the state of your load/run jumper
D) Check your PNP mod
E) Talk to me after I've been in the shower and to the post office! :-)

Fred.

[Fred]

Also, SM doesn't flash any LEDs. Code flashes CEL LED. Code shouldn't work without SM in place, though.

[Kennybug]

everytime i send something in cutecom or connect MCU by FreeEMS Loader.
D33 (Ftdi Cbus0) flashed.
Am I flashed theSM wrongly?

A) my SM is freeems.serial.monitor.s19, i checked it is a bunch of hex code without reading error.
B) do you mean loading the firmware from Hiwave by BDM plug?
C D E) will do it on weekend. It's my time to sleep (& I needed to complete some tax forms asap coming few days )

[Fred]

A) I meant using the BDM and associated application (IF it has this function (the foss bdm app does))
B) Yes, but specifically doing so without erasing the SM. Again, the foss bdm setup can do this. http://issues.freeems.org/view.php?id=225 "erase selective" screenshot from it.
C/D/E OK :-)

LED flashing = FTDI working. Thus either sm load is bad (hence A = verify it) OR mode = run, not load (hence C = check mode)

Fred.

[Fred]

Any news?