5 years, 6 months ago.

fail.txt > Timeout on Windows 8.1(LPC800)

Hello everyone.

So today i was trying to setup LPCxpresso so that i could program offline but before i started i decided to update the firmware on my LPC800 board.

That is where my problems started. At the time i was using my linux system (Fedora 20) and everything seemed to work. However after the update i can no longer use the board.

When i am on linux and try to use LPCxpresso to program the board, it works the first time i upload code (in pure C) but after that the IDE cannot comunicate with the board any longer (i need to reboot the PC). No even drag and droping code generated by the mbed online compiler works.

Also when i'm on linux, if i flash the HDK firmware, i can then upload code (e,g, Blinky) from mbed online compiler by drag and dropping, but if i then plug the board on the windows machine, the code dosen´t (?) run (no led flashing, but the 3 leds, cmsis-dap, usb disk and usb com, work as normal.)

When i am on Windows, the explorer window keeps poping up every few seconds and the drive contains the text file "fail.txt" with "TIMEOUT" inside. The timeout is refering to what exactly? I can´t find any info ou documentation.

Is there any solution? I did find two other threads about the timeout but none of them helped.

I'm also not shure if this is important but i haven't changed the resistors yet (from what i understant that is only necessarie for serial communications)

Well a little update. Whenever the board reset it self, mbed.html gets currupted and when open, displays a string of random numbers and letters. for example (one line for each reset):

{E1B31324-7FCB-46C0-9107-9E8CBC9DC16C}

{A9CBB51B-4F42-4BD2-8974-2B462B4626DE}

{9916C7CA-AD3C-46EA-B6B8-A899E1C98F62}

{29AE3A33-45DD-4B93-8B07-14B47997DDAD}

{004D6042-4E52-4B83-972D-BE967DFC9458}

{41D3DA09-A82D-4D7E-B142-4EE96B9674C4}

{E9B7BF75-3948-427A-B382-7C0F4A19A6F9}

{A3C8DB60-955B-4A58-87F6-7019B45C3017}

{9B66C9FD-CC77-411D-AE6F-9AF29AC8AF79}

Does anyone know if this means anything?

posted by Tiago Costa 08 May 2014

Problem solved. It looks like the firmware didn´t support windows 8.1. With the new release allis working fine.

posted by Tiago Costa 01 Aug 2014
Comment on this question
Be the first to answer this question.

Assigned to Tiago Costa 5 years, 3 months ago.

This means that the question has been accepted and is being worked on.

You need to log in to post a question