OSJTAG issues.

[KarlMarx]

Summary:

After updating the OSJTAG firmware, I am no longer able to connect to the serial-over-usb functionality in the pemicro terminal, etc.

Background:

I started by installing the tower toolkit off of the included cd, and followed along with the demo lab. At this point I was able to connect to the teminal, run the accelerometer demo, etc. I then installed codewarrior (10.1 se) and attempted to load/run one of the demos. At this point codewarrior brought up a notification to update the board firmware (which successfully brought me from rev. 27 to rev. 29.) The demo seemed to run fine, but I was never able to get terminal output from it; so I tried to connect from the pemicro terminal again, which also failed.

Details:

I checked the drivers, and noticed the usb serial port device was missing (but the debug port and jungo windriver were still there.)

I then followed the "troubleshooting serial driver" instructions here:

http://www.pemicro.com/osbdm/Installation_and_Operation_of_the_OSBDM.pdf

Specifically, I installed the pemicro firmware update tool, and updated to firmware rev. 30.

Once I reconnected the board, all three devices showed up in Windows device manager. Attempting to update the drivers returned that they were all the most recent versions.

I still could not connect to the USB serial terminal at this point. The terminal also occasionally reports read errors (I can't remember the exact wording, however.)

I've uninstalled all of the related tools and drivers from my system, and verified that I have the latest versions of all the installers. I will try reinstalling everything tomorrow, and see if it makes a difference; pending any advice I receive here.

TLDR;

Can anyone who has gotten the board to work with the rev. 30 firmware recommend an installation procedure/software combination that works? Has anyone else even had these problems?

[DangerMouse]

Having the exact same problem as you Karl.

Firstly could not see PEmicro USB serial port (i1) driver, then used P&E Firmware Update Utility to update to firmware version 30.0 and now have all 3 drivers installed.

PEmicro terminal is still not recognising PC to USB connection. 

Have tried reinstall of all of tools but getting the same result.

Using window 7 x64 and flash chip is MC9SO8JM60 on the Kinetis K40x256 tower board. 

Anybody any ideas?

[nadav]

I had the same problem.

I found that I had to choose COM5 instead of USB COM.

Try this:

Open Device Manager ->  Ports (COM & LPT) -> OSBDM/OSJTAG

and check which COM is defined

[TonyA]

Hello All,

I am brand new to this. Already very disappointed...

Have Win7 64-bit, admin rights, using Tower K60N512 connected via USB cable.

Ran pemicro_osbdm_osjtag_tower_toolkit.exe, PEDrivers_install.exe (latest downloads, avoilded programs folder)

Updated fw in target to 31.21, but cannot get:

1. USB driver to show under Jungo

2. Terminal utility, v.2.05 does not connect (tried changing duplex to half, no luck).

3. I did not even get to install CodeWarrior and QMX yet...

Any advice, info much appreciated!!

Thank you.

Tony Ander

[evgenyerlihman]

Hi Tony,

Any chance you got it working?

Thanks,

Evgeny

[Zahar]

Hello DangerMouse,

Did you install the latest Kinetis Kit from the link in my previous post? An older version of the Kinetis kit is not compatible with OSBDM firmware version 30.0 and higher.

Best Regards,
Zahar

P&E

[DangerMouse]

Yes that is what  i did and it worked great. Thanks again

[Zahar · Accepted solution]

Hello Karl,

Please try updating your Kinetis tower toolkit to the latest version found in the link below.

http://www.pemicro.com/downloads/download_file.cfm?download_id=332

Only the newest kinetis_tower_toolkit software works with firmware version 30.
--
Best Regards,
Zahar
P&E Microcomputer Systems

[MK_User]

I am still experiencing problems.

I am running Windows 7 Professional SP1, x64.

I have updated the firmware to ver 30, and verified it with the PE Micro Firmware Information Utility.

All 3 drivers are present.

Jungo - Win Driver, ver 10.1.0.0, 9/2/2009

Jungo - PEMicro USB Serial Port (i1), ver 6.2.0.0, 9/21/2010

LibUSB - Win32 Devices - Open Source BDM - Debug Port, ver 1.2.2.0, 1/7/2011

I have downloaded the latest OSBDM Virtual Serial Toolkit from the PE Micro website.

When I run the Terminal Utility, I will ocassionally get the following error:

"Access violation at address 004051A9 in module 'TerminalWindow.exe'.

Read of address 6B757571."

When I click the Open Serial Port button, regardless as to whether the above error appears, the program indicates that the port is open.

However, there is no output.

I know the code is correct because it used to work with the old firmware on an XP machine that I first tried the board out on.

However, since updating the firmware and the Terminal Utility, it does not work on the XP machine either.

I don't know if there a driver conflict with the old ones or somethign else, but this is extremely frustrating!

[DangerMouse]

Hi MK_User

I have exact same issue as you regarding pemicro's "Terminal Utility" virtual serial port.

Earlier i mistakenly thought (see ealier post)  i had configured virtual serial port correctly as i got it the port to open and all

the drivers had enumerated correctly.  However the next day when i ran some programs i

realised that there was no serial output on the terminal.

The osbdm firmware .30  works fine for downloads so I have just been using the physical  serial port on the tower board instead.

I had no previous such problems with earlier versions of osbdm firmware (.27 and .28)  and Terminal Utility.

Has anybody got the "Terminal Utility"  virtual serial port to work with codewarrior v10.1 and Kinetis Tower board ?

Running win 7 x64 host, Teminal utility v2.03 and osmdens_arm.3005 firmware.

[DangerMouse]

Hi MK_User

I have exact same issue as you regarding pemicro's "Terminal Utility" virtual serial port.

Earlier i mistakenly thought (see ealier post)  i had configured virtual serial port correctly as i got it the port to open and all

the drivers had enumerated correctly.  However the next day when i ran some programs i

realised that there was no serial output on the terminal.

The osbdm firmware .30  works fine for downloads so I have just been using the physical  serial port on the tower board instead.

I had no previous such problems with earlier versions of osbdm firmware (.27 and .28)  and Terminal Utility.

Has anybody got the "Terminal Utility"  virtual serial port to work with codewarrior v10.1 and Kinetis Tower board ?

Running win 7 x64 host, Teminal utility v2.03 and osmdens_arm.3005 firmware.

[swohler]

MK_User and DangerMouse,

Unfortunately I'm having the same issue. I'm running Win7 Home Premium x32. Using the serial terminal, opening the port works fine but I get no response from the Tower.

Everything else seems to be okay, the drivers are all installed correctly, etc.

Don't know what's going on just yet.

-Scott

[DangerMouse]

So it looks like this is a win 7 issue then maybe.

Codewarrior v10.1 needs osbdm firmware .29 or .30 i believe, however i could

not get all 3 drivers to install correctly until i used the .30 firmware.

Can anybody confirm that they have pemicro virtual port (v2.03) working on win XP and if so

which osbdm firmware version are they using ?

Also has anyone got all 3 drivers installed correctly on win 7 while using osbdm version .29 ?

I have left service request with pemicro,so far have received no solution but will post back

here if i find one.

[Dilomos]

I don't think it's a Win 7 issue because I'm on Win XP and have the same issue.

I successfully used the PEmicro terminal v2.00 with firmware v.27 or .28 (don't remenber exactly the one that worked)

Then, I update my firmware to .29 using codewarrior (I don't think I try the terminal with this version)

Then I update to firmware .30 because I did'nt get the serial port working well.

I updtae the terminal to v2.05 at the same time as I read that it's the only version working with .30 firmware.

Now, All driver seams ok in control panel (jungo and libusb) I can open the port in terminal v2.05 but nothing output in.

I can't even open the port in terminal v2.0.

I try downgrade the firmware to .29 don't change output issue but I can open again the port in terminal v2.0

I don't have lower version of the firmware to try (.27/.28 or even lower).

So I think the issue don't depend of the windows version.

[DangerMouse]

Yes you may well be correct.

I have tried with XP aswell, with terminal utility v2.01, v2.03 and 2.05 and same as before,

can get the port to open - depending on which firmware used .29 or .30) but no output.

Is this a lost cause, nobody seems to confirm it working and the last i heard pemicro

said v2.05 fixes the issue.. well not for me anyway.

[J2MEJediMaster]

Some suggestions:

1) If your host has USB 2.0, try backing off on the transfer rate. We had situations where the maximum USB 2 transfer rate causes problems.

2) There is a support board for various OSBDM implementations. Maybe you are already aware of it. If not, take a look.

---Tom

[MK_User]

Can you clarify "USB Transfer rates"?

Are you referring to the actual USB interface, or the virtual serial port's baud rate?

If you are referencing the actual USB interface, where can I adjust that?

Which forum for the OSBDM board is most applicable to the Kinetis chipset?

I see forums for Coldfire, S12, HCS08, and DSC.

Thanks for any additional info.

[J2MEJediMaster]

It would be the actual USB interface rate. See this FAQ for information on how to change the USB speed. (Note: this FAQ was written for a Windows XP system, but a cursory check of Windows 7 seems to indicate it may still be of use. Your mileage may vary.)

Since you are talking about OSJTAG, I would start in the DSC forum because it uses a JTAG interface.

---Tom

[MK_User]

I feel that this answer is unacceptable for two reasons.

1) I should not have to downgrade my computer to a standard which is 13 years old to get this product to work, which would now affect all other USB products I use, if I am understanding the FAQ  correctly.

2) This board worked previously with an XP machine and the previous firmware. Once I upgraded the firmware to support the Windows 7 instantiation problem it stopped working on XP and Win 7 platforms.

If, as the FAQ suggests, disabling the 2.0 USB hub works, it would reassociate the drivers with the new 1.1 USB Hub. If this method works, then it suggests that the problem is likely related to the old VID/PID entries in the registry from the previous firmware.

Who is responsible for the firmware? PE Micro or Freescale? Who can we talk to to get this resolved?

[admin]

Try setting the terminal to connect using half duplex mode (Duplex: Half) and then open the serial port.  It works this way for me.

I'm running on Windows 7 64-bit with Terminal Window v2.05 and OSBDM Firmware v30 (osbdmens_arm.3005).

[admin]

Spoke too soon. Half duplex isn't working either.

[MK_User]

I spoke with PE Micro at FTF and they provided me with an updated firmware, v30.07, which fixed my issues on the K40 board.

Hopefully it will be posted on their website for download soon.