6 years, 1 month ago.

EA LPC4088 HDK Serial (mbed serial port) stopped after a while.

Hi,

This program

Import programLPC4088test

sdram and cdc,hdk serial test program for EA4088 mbed. HDK Serial stopped after a while, but CDC Serial and LED HeartBeat is alive.

is test that allocate heap memory on sdram and output message.

Memory allocation is OK, but message from HDK (mbed) USB serial port was stopped after a while. I added "USBSerial(USBDevice ,CDC)", in order to compare, but USB CDC Serial works well.

I wrote a bad code?

Does someone see the same problem?

Thank you.

P.S. When this problem occured, The message from the program can be received by the external TTL-USB Serial Converter connected to Pin42(HDK Serial TX).

Comment on this question

2 Answers

6 years, 1 month ago.

We have tested your application on a couple of our boards and cannot reproduce your problem. We have a couple of questions.

  1. Do you see this behavior also with other applications (e.g. a simple app which only prints messages in a loop)?
  2. Is your PC running Windows, Linux or Mac (which version)?
  3. Have you tested on another PC?

We have tested your application on a couple of our boards and cannot reproduce your problem.

Thank you for answering.

1 .Do you see this behavior also with other applications (e.g. a simple app which only prints messages in a loop)?

Yes. Same problem occured.

Import programLPC4088test_ledonly

hdk serial test program for EA4088 mbed. HDK Serial stopped after a while.

Import programLPC4088test_deleteall

delete led heartbeat.

are stopped sending message via VCOM after a while.

And I noticed reverse direction (PC->mbed HDK) sending with typing keyboard, Blue HDK LED is blink.

2.Is your PC running Windows, Linux or Mac (which version)?

PC:Windows Note PC (Lenovo X220i : Model 42873LJ : Core i5-2520M)

OS:Windows7 Utilmate SP1 x64

driver is mbedSerial_x64.sys Vesion 1.73.0.0

Terminal Program:Tera Term Version 4.73 (SVN #4845)

3.Have you tested on another PC?

Not done yet, but I want to test.

posted by fuyuno sakura 07 Oct 2013
6 years, 1 month ago.

I try to test on the issue with Mac OS X 10.8.5(Mac Book Air Mid 2012), I saw another problem.......

USB Drive is not recognized and "dmesg" say below

USBMSC Identifier (non-unique): 01030200F83086860E6A41DE 0xd28 0x204 0x100, 1
[0xffffff803505dc00](1)/(5) Device not responding
       0        1 AppleUSBCDCACMControl: start - Failed to find the CDC driver
       0        2 AppleUSBCDCACMData: start - Find CDC driver for ACM data interface failed
       0        2 AppleUSBCDCECMData: start - Find CDC driver for ECM data interface failed
AppleUSBCDC: Version number - 4.1.23
USBMSC Identifier (non-unique): 01030200F83086860E6A41DE 0xd28 0x204 0x100, 1
com_protech_nosleepextension: setting state: 1, for mode: 0 (ac-mode)
[0xffffff8035093800](1)/(5) Device not responding
       0        1 AppleUSBCDCACMControl: start - Failed to find the CDC driver
       0        2 AppleUSBCDCACMData: start - Find CDC driver for ACM data interface failed
       0        2 AppleUSBCDCECMData: start - Find CDC driver for ECM data interface failed
AppleUSBCDC: Version number - 4.1.23
USBMSC Identifier (non-unique): 01030200F83086860E6A41DE 0xd28 0x204 0x100, 1
[0xffffff80323da000](1)/(5) Device not responding
       0        1 AppleUSBCDCACMControl: start - Failed to find the CDC driver
       0        2 AppleUSBCDCACMData: start - Find CDC driver for ACM data interface failed
       0        2 AppleUSBCDCECMData: start - Find CDC driver for ECM data interface failed
AppleUSBCDC: Version number - 4.1.23
USBMSC Identifier (non-unique): 01030200F83086860E6A41DE 0xd28 0x204 0x100, 1
USBF:	95831. 21	The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x14000000)
USBF:	95899.593	The IOUSBFamily was not able to enumerate the device (Port 1 of Hub at 0x14000000).
USBF:	95918. 86	The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x14000000)
USBF:	95968. 47	The IOUSBFamily was not able to enumerate the device (Port 1 of Hub at 0x14000000).
USBF:	96003.944	The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x14000000)
USBF:	96019.164	The IOUSBFamily gave up enumerating a USB device after 10 retries.  (Port 1 of Hub at 0x14000000)
USBF:	96019.164	The IOUSBFamily was not able to enumerate the device (Port 1 of Hub at 0x14000000).

This mbed's firmware is "LPC4088test_ledonly" version which written in windows machine.

I get confused...... I will retry later.

I found the procedure which this issue occurs in my Windows Machine.

1)Write Firmware (sending with HDK VCP)

2)Plug out mbed

2)Re-Plug in mbed

3)Start Monitering HDK VCOM with Tera Term

4)Open a Mbed drive with Explorer

5)After access the mbed drive, the message form VCP serial stop.

posted by fuyuno sakura 08 Oct 2013
5) After access the mbed drive, the message form VCP serial stop.

When accessing the mbed drive do you mean writing a file to the drive or is it enough to just access the drive? Writing a file will restart the HDK.

posted by EmbeddedArtists AB 08 Oct 2013
writing a file to the drive or is it enough to just access the drive?

I only opened the folder (mbed drive). I didn't write (drag n drop) a file.

posted by fuyuno sakura 08 Oct 2013

I am getting the exact same errors - and I seem to have narrowed it down to be a problem on the new Haswell Mac laptops (tried it on a new Pro 2013 and Air 2013 that shows the problem - and an old Pro and Air (pre-2013) that works just fine.

At the moment, I am trying to modify the kext "driver" files in /System/Library/Extensions to grab my particular VID/PID and force some USB serial driver/module. My guess:

1. the new macs use a new USB3 chip that - for some reason - is not compatible with the serial devices I have tried (google gives many examples of the same problem with e.g. Macbook Air 2013 and other devices)

2. the new macs are just more strict in the software so one needs to be 100% compliant with the USB CDC profile (somehow)

.. these are just guesses... digging further.

posted by Lars Knudsen 19 Feb 2014

Hi, Lars

I am getting the exact same errors .. .. these are just guesses... digging further.

Thanks for your information about 4088mbed with Mac.

I have not tried from that. if I found new information, I will also write.

posted by fuyuno sakura 19 Feb 2014

You need to log in to post a question