Problem with USB/OpenSDA interface on FRDM-KEAZ128

[adamjohnson]

I purchased a FRDM-KEAZ128Q80 from DigiKey. The OpenSDA portion of the board appears to be nonfunctional. The demos work if I connect a 12V source, but connecting a USB cable doesn't power the board or enumerate with a computer. When connected only to USB, I can probe that power is getting to the OpenSDA MCU, but the main power busses are not on. Is my board just defective, or am I missing something obvious?

[kerryzhou]

Hi Adam,

    I check your video again, it seems your reset hold time is not long enough, so please hold it about 10 seconds after you plug the usb again, check whether you can find the bootloader device or not. After you test it, please let me know the test result.

    My new board still on the way.

Have a great day,
Kerry

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[adamjohnson]

Mahmoud,

Thanks for your help. This is my first foray into the world of Cortex and NXP KE, so my apologies if I'm missing some thing straightforward. I was under the impression that the secondary microcontroller attached on the circuit board, the one connected to USB, was pre-burned with firmware to act as a programmer/debugger for the main microcontroller, the KEA128.

Since my original post, I've received a second replacement board from DigiKey, and it acts the same way. In both cases, the demo application on the KEA128 appears to work properly when connected to an external power supply, but the programmer/debugger and USB interface seem to be nonfunctional.

a. How can I verify the bootloader? I was expecting that the board would appear as a mass storage device and serial port out of the box. Currently, none of the LEDs light up at all when connected to USB, including the OpenSDA LED.

b. My board only has a single microUSB connector, and I'm connecting to that one.

c. I probed a few test points on the board to see if the USB connector was bad. P5V_SDA and P3V3_SDA have power, but P5V0 and P3V3 do not.

Kerry,

The J107 jumper is connected to 2-3, I did try 1-2 also. None of the LEDs on the boards come on when they are connected via USB. For host devices, I've tried Windows 10, Windows 7, MacOS, and connecting directly to a USB phone charger.

[kerryzhou]

Hi Adam,

   Now, please follow my step to test the board again, please use the win7 system to test it at first.

1. Download the according software

  1) Download Pemicro driver and install it from this link:

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

   2) Download the firmware

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

   Unzip it, find file:MSD-DEBUG-FRDMP-KEAZ128Q80_Pemicro_v118.SDA , this is the opensda firmware, will be used.

2. Change the on board bootloader to opensda

 1) Power off the board, then press the on board reset button, hold on it, plug the USB cable to J7, release the button

   You will find your PC have a device named as "BOOTLOADER"

  2) Send file MSD-DEBUG-FRDMP-KEAZ128Q80_Pemicro_v118.SDA to your "BOOTLOADER",  and wait the sending finished.

  3) Unplug the USB and plug the USB cable again

     You will find your board is a device named as "FRDMPKEA128", just like this picture:

Until now, your on board bootloader is changed to the opensda, you may also find the com port in the device manager:

3. Download the KEA app code to your MSD board.

 FRDMPKEA128 is also a MSD device, you can send the KEA app to this device directly.

Please check my attached Lab1_Blinky_Loop_KEA128.srec, this code will blinking the D11

Unzip my attached code, then send Lab1_Blinky_Loop_KEA128.srec to your FRDMPKEA128 .

The following picture is my test result":

Please follow my above steps try it on your side carefully.

Besides, If it works, you can updated your bootloader to the latest version, just follow these step:

Issue: Bootloader versions 1.10 and earlier are not allowing firmware update and MSD FLASH programming on ...

Solution: Support for Windows 8/8.1, MacOS and Linux operating systems was added to Bootloader version 1.11 and MSD firmware version 1.14. Please make sure that your board is programmed with Bootloader version 1.11 or higher prior to attempting to update your OpenSDA board with a new firmware application.

Important: If you are currently running Bootloader version 1.10 or earlier, you will need to find a Windows XP or Windows 7 PC to perform this update.

Please follow these steps to find out what version of Bootloader your board is programmed with:

1. Start your board in Bootloader mode by holding down the RESET button prior to plugging it into USB port.
2. Open the SDA_INFO.HTM file, which will contain version numbers of Bootloader as well name and version of current OpenSDA firmware you are using. If your board is not running Bootloader version 1.11 or higher, please download the latest OpenSDA Firmware Apps from P&E website and follow instructions in corresponding documentation to update the Bootloader using the BOOTUPDATEAPP_Pemicro_v111.SDA application. Once the Bootloader is updated via BOOTUPDATEAPP, the OpenSDA board can then be upgraded to the latest combined MSD/DEBUG OpenSDA firmware 1.14 or greater.

Wish it helps you!

Have a great day,
Kerry

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[adamjohnson]

Kerry,

I followed your instructions and installed the drivers on Windows 7, however, neither board appears as a device after reset. Nothing shows up in Device Manager, and there are no new drives that appear. Here's a video--you can see that there are no LEDs on at all when connected via USB.

https://drive.google.com/file/d/11OEOkk-AXcoV-C5sa_Y-b12mdOltZTeQ/view?usp=sharing

I suspect the programming/debugging firmware was never loaded on these boards. Would that make sense, and, if so, is there a way to program them without additional hardware?

[kerryzhou]

Hi Adam,

   Please check J107 on your board, you need to connect pin2,3.

  If you just connect the USB cable, whether your D2 is lighting or not?

 Please also tell me what the PC operation system you are using?

Have a great day,
Kerry

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[mahmoudsherrah]

Hello Adam,

I've had a lot of issues with FRDM boards initially. Some bootloaders (like DEBUG-APP_Pemicro_v102.SDA) do not enumerate the board on connection to USB. Also some boards do not come with the example application burned, hence the only LED that will light up is the OpenSDA LED.

Therefore, a) make sure that you have the correct bootloader burned. b) make sure you're using the SDA onboard USB port. c) How exactly did you measure the "main power busses"?