Problem with LA 104 firmware via USB about la104 HOT 14 OPEN

@gumalexgum It seems that the shell.elf file is corrupted. Start the device with 4th button pressed (or 3rd, I can't remember exactly) to enter safe mode. Delete everything from the usb drive and copy the shell.elf again.

from la104.

Safe mode. Windows: USB device not recognized!

from la104.

@gumalexgum It seems that the shell.elf file is corrupted. Start the device with 4th button pressed (or 3rd, I can't remember exactly) to enter safe mode. Delete everything from the usb drive and copy the shell.elf again.

Sorry! Does not work! The USB device is not recognized by Windows.

from la104.

Show me screenshot of device manager. If the drive is just not accessible, try formatting it

from la104.

Show me screenshot of device manager. If the drive is just not accessible, try formatting it

I can't format my device!

from la104.

That is weird, can you try attaching it to another computer?

from la104.

Yes, I tried connecting to a Windows 7 x 32 laptop. Same thing. In my opinion, there was a failure during the transfer of files and an incorrect file name. Because of this, the USB is not connected.

from la104.

When copying system_la104.hex, system_la104.err appears first, which I will rename to system_la104.hex, after which system_la104.rdy appears. I don't know if this file is correct or not? And copy is obtained only in VirtualBox with Ubuntu x64.

from la104.

No, do not rename them. Just copy for the first time, wait util the device gets disconnected, then copy the file again. Try copying the file twice, and without VM

from la104.

I used firmware LA104_APP_V1.03.hex to restore the logic analyzer. After that, I went to the FileSys settings menu, where I turned on SaveCsv to 1. After that, the driver for the device was loaded and the Undefined device was defined as: "Mini DSO Disk USB Device 8.0 Mb".

The opened USB drive contained three files:

1. bmp
2. csv
3. shell.elf with size 0 bytes

I deleted all files from the disk. I think the problem was the 0-byte shell.elf file, which prevented the device driver from being connected. The disk was not identified.

from la104.

My working system is Windows 7x64. All manipulations were done in it.
How did I start the project? There is one more unresolved bug.

1. Turn on the power while pressing the first SMPL button.
2. Copy the LA104_APP_V1.03.hex file to the Virtual DFU Disk USB Device.
3. Turn off the device.
4. Turn on the power and do not press the button. The logic analyzer device starts up. Mini DSO USB Device 8.0 Mb appears.
5. Copy the files from the la104apps folder to this USB Disk.
6. Turn off the device.
7. Turn on the power while pressing the first SMPL button.
8. Copy the system_la104.hex file to the Virtual DFU Disk USB Device.
9. Then the download fails, a long wait, and the file system asks to cancel or retry the file download. Press repeat once. There will be another download failure. Click cancel.
10. Turn off the device.
11. Turn on the power and do not press the button. The author's project is launched. But the USB Disk is not recognized. Although all the files copied earlier should work.

The author has a big request to give a driver for the USB Disk Device. Can someone suggest other solutions?

from la104.

from la104.

What USB device should LA104 detect when connected to a computer? And why does Windows 7 not detect the device ID?

from la104.

people seeing this issue cd to the LA104 drive and run find . -type f -name '.*' -delete

from la104.