All tests result in IOERR_SERIAL on Linux about greentea HOT 6 CLOSED

Probably you have K64F with faulty firmware (interface chip).
I should send you firmware you can flash to your K64F.

PS: Next time please put more details in Issue report. For example console output etc.

from greentea.

@hasnainvirk Please check your mailbox :)

from greentea.

Hi,

Its still the same issue, even with the new firmware.

From: Przemek Wirkus [mailto:[email protected]]
Sent: 28 August 2015 17:03
To: ARMmbed/greentea
Cc: Hasnain Virk
Subject: Re: [greentea] All tests result in IOERR_SERIAL on Linux (#18)

Closed #18#18.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#event-395097698.

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

from greentea.

Here is the console output.

hasnain@ubuntu:~/Documents/mbed-drivers$ mbedgt --target=frdm-k64f-gcc
mbedgt: yotta search for existing mbed-target
mbedgt: current yotta target is: not set
mbed-ls: detecting connected mbed-enabled devices...
detected K64F, console at: /dev/ttyACM0, mounted at: /media/hasnain/MBED
mbedgt: scan available targets for 'K64F' platform...
mbedgt: yotta search for mbed-target:k64f
mbedgt: using 'frdm-k64f-gcc' target, prepare to build
mbedgt: calling yotta to build your sources and tests: yotta -v --target=frdm-k64f-gcc,* build
info: generate for target: frdm-k64f-gcc 0.0.23 at /home/hasnain/Documents/mbed-drivers/yotta_targets/frdm-k64f-gcc
GCC version is: 4.9.3
-- Configuring done
-- Generating done
-- Build files have been written to: /home/hasnain/Documents/mbed-drivers/build/frdm-k64f-gcc
ninja: no work to do.
mbedgt: yotta build successful
mbedgt: running tests for 'frdm-k64f-gcc' target
running host test...
test 'mbed-drivers-test-echo' .......................................................... IOERR_SERIAL in 17.34 sec
running host test...
test 'mbed-drivers-test-time_us' ....................................................... IOERR_SERIAL in 16.84 sec
running host test...
test 'mbed-drivers-test-serial_interrupt' .............................................. IOERR_SERIAL in 17.37 sec
running host test...
test 'mbed-drivers-test-blinky' ........................................................ IOERR_SERIAL in 16.87 sec
running host test...
test 'mbed-drivers-test-functionpointer' ............................................... IOERR_SERIAL in 16.84 se

from greentea.

@hasnainvirk If problem persists, please reopen this issue and provide details of firmware (there's html file which should contain that information)

from greentea.

@0xc0170 I can't see any option to re-open the issue. And also there is no need to re-open this issue. As with new firmware, it works fine for GCC now. I am using the latest firmware, 0225_k20dx128_k64f_0x5000. The problem is with ARMCC. And STM32F429i target is not supported in linux yet. Moreover it is mentioned in the README.md that the test frameowrk is still experimental for Linux. Here is the link to the new issue, I created. #20

from greentea.