Main Board Index Forum Index

Device: SkyTC - KMP510 (Envivo Otek Xenta Arnova) Forum:   Device: SkyTC - KMP510 (Envivo Otek Xenta Arnova)

Topic: File Error

January 6, 2012, 11:11 am #1
Had a same problem. Tried symlink method and install from SD. At the end I ended up formating internal memory(it showed 39MB when mounted to ubuntu but only 14MB were available) after reformat I copied firmware file to it from sin XP. Eject did not work so I just pulled it out. Then I tried to upgrade it and it got stuck on upgrading screen for hours at the end I power cycled it and it booted to new firmware(1.0) then I upgraded to 1.2 without problems.
December 28, 2011, 2:24 pm #2
I have tried many, many times to update to 1.0 strictly following the installation guide on my Wiwa ertv 208. I have copied it under windows explorer, chosen 'eject' from my computer menu.
The file size on the internal memory is exactly the same as in zip... I have no clue what to try next. Everytime I got 'file error'. The file fits fine into internal memory (it's 34.7MB).
I have FAT original file system. Any help would be appreciated.
Thanks
December 15, 2011, 1:12 pm #3

I can solve that differently for you. Contact me via email..

December 15, 2011, 11:05 am #4
Quote:

Hi, what is it exactly that you try to do? 

wd: Install replacement firmware.
There is firmware for the Wiwa, both a patched 1.8.4 and the new 1.0 firmware.

wd: Actual: 1.84 (i have). I want to instal 1.0 without succes (look at post up)

Your internal memory is damaged/not working? 

wd: working on 1.84 ver.
What is your current version? 

wd: 1.84
Does your current firmware have an option to update from SD card?

No. This is the reason why I tried symlik (See the description in the post above ...)

Wlodek

 

 

December 15, 2011, 10:01 am #5
Just a point, probably irrelevant, but might save heartache.

My Xenta was fussy about which SD card I used. It wouldn't recognise media files on a Kingston 1GB (speed 2or 4), but was happy with cheap Veho 2 and 4GB cards.
Have people who are having firmware-update problems tried several different SD cards? If the machine is just fussy, it'd be far safer to try out a few different cards before poking around the internal OS.
December 15, 2011, 9:06 am #6

Hi, what is it exactly that you try to do?
There is firmware for the Wiwa, both a patched 1.8.4 and the new 1.0 firmware.
Your internal memory is damaged/not working?
What is your current version?
Does your current firmware have an option to update from SD card?

 

 

December 15, 2011, 9:00 am #7
Hello,
Failed to install alternate firmware. Details in the post above. Can anyone help?
Wlodek

PS I'm not a Linux expert but I have an idea associated with the 'fstab'. Unless there are written rules of access to "mtdblock9". In the evening I'll try to - the outcome will inform. I hope that my equipment will survive ...
December 14, 2011, 10:18 am #8

Thanks!
In the evening after upgrade I will know if my equipment is still alive ...
Wlodek


2011-12-14 - Edit:
Without success! I have WIWA eRTV 208 with modified Firmware update for the Wiwa eRTV208. This same after using 'su' command ...

Below my session:

Ingenic linux machine
Kernel 2.6.24.3 on an mips
(none) login: root
# ln -s /mnt/mmc/update-firmware.bin /mnt/mtdblock9/update-firmware.bin
ln: /mnt/mtdblock9/update-firmware.bin: Operation not permitted
# mount -rw /dev/mtdblock9 /mnt/mtdblock9
mount: mounting /dev/mtdblock9 on /mnt/mtdblock9 failed: Device or resource busy

and finally (perhaps this will help solve the problem?):


# ps
  PID  Uid        VSZ Stat Command
    1 root       4176 S   init
    2 root            SW< [kthreadd]
    3 root            SW< [ksoftirqd/0]
    4 root            SW< [events/0]
    5 root            SW< [khelper]
   32 root            SW< [kblockd/0]
   40 root            SW< [kseriod]
   44 root            SW< [kmmcd]
   66 root            SW  [pdflush]
   67 root            SW  [pdflush]
   68 root            SW< [kswapd0]
   69 root            SW< [aio/0]
   70 root            SW< [cifsoplockd]
   71 root            SW< [cifsdnotifyd]
  149 root            SW< [udc_workqueue]
  167 root            SW< [wpen_workqueue/]
  176 root            SW< [mtdblockd]                 {wd: ???}
  213 root            SW< [fm_rda580x_work]
  244 root       3288 S < /sbin/udevd --daemon
  269 root       4176 S   /sbin/telnetd
  272 1          2588 S   /sbin/portmap
  282 root            DW< [SDIO Helper]
  286 root            DW< [SDIO IrqHelper]
  299 root      69764 S   ./jz-media-app
  300 root       4240 S   -sh
  302 root       1804 R   ./system-daemon
  325 root      69764 S   ./jz-media-app
  326 root      69764 S   ./jz-media-app
  327 root      69764 S   ./jz-media-app
  328 root      69764 S   ./jz-media-app
  329 root      69764 S   ./jz-media-app
  334 root      69764 S   ./jz-media-app
  340 root      69764 S   ./jz-media-app
  351 root       2188 S   ./wpa_supplicant -i eth0 -D wext -c /mnt/mtdblock7/w.conf -B
  354 root      69764 S   ./jz-media-app
  363 root      69764 S   ./jz-media-app
  392 root       4240 S   udhcpc -i eth0 -h iRadioAA61D3
  399 root      69764 S   ./jz-media-app
  400 root      69764 S   ./jz-media-app
  401 root      69764 S   ./jz-media-app
  402 root      69764 S   ./jz-media-app
  403 root      69764 S   ./jz-media-app
  406 root      69764 S   ./jz-media-app
  417 root      69764 S   ./jz-media-app
 2988 root            SW< [mmcqd]
 3287 root       4240 S   -sh
 3574 root       4240 R   ps
 3575 root             []
 3576 root             []
#

(Last Edited by wdobry on December 14, 2011, 5:25 pm)
(Last Edited by wdobry on December 15, 2011, 8:46 am)
(Last Edited by wdobry on December 15, 2011, 8:51 am)
December 14, 2011, 10:06 am #9
Warning: Don't do this unless you're happy "fiddling" in Linux.. the wrong move, and you could destroy everything!

All commands are written in italics...

  1. turn on your radio, and connect it to your network.
  2. From a desktop computer also on your network, open the command prompt / terminal, and telnet into the radio (for me the command is telnet 192.168.0.3 , but the ip address depends on your network, how many machines are connected, etc)
  3. username is root
  4. type su (not sure if this is needed, but it's what I did!). [then Enter].
  5. type ln -s /mnt/mmc/update-firmware.bin /mnt/mtdblock9/update-firmware.bin [ then Enter] (note - that's a lower case "L" not a capital "i" at the start!)
If that doesn't work, you may need to mount the internal partition. If so, after point 4 type mount -rw /dev/mtdblock9 /mnt/mtdblock9 [then Enter] then do step 5 as above.

After this, ensure that update-firmware.bin is in the root directory on your SD card in the radio, and then run the update.

Good luck!

(Last Edited by slaphead on December 14, 2011, 10:26 am)
(Last Edited by slaphead on December 14, 2011, 10:27 am)
December 14, 2011, 8:37 am #10
Hello,
This is my first post on this forum. Welcome. I have a request to Slaphead. Can I ask for a detailed description of how to make a symlink to install new software? Thanks in advance. Wlodek


Quote:
WooHoo! It's sorted!

Why didn't I think of this before! I created a symlink from the "small" internal directory to the SD card, and it updated fine.. I now have the all singing / dancing new firmware!

Thanks both for your help, and thanks penbex for the very smart firmware!
(Last Edited by slaphead on December 13, 2011, 12:46 pm)
December 13, 2011, 4:03 pm #11
Indeed woohoo.. great idea congrats!
December 13, 2011, 12:26 pm #12
December 13, 2011, 9:28 am #13
If you need some direct comparison data from a working Xenta, ask away. But, I'm not a Linux expert, so everything will take me rather longer to do.

B
December 12, 2011, 3:40 pm #14
Cheers Penbex - that's getting somewhere! I had to empty the lost+found directory in mnt/mtdblock9 but even then, there's not enough space in there to copy the update-firmware.bin file to...

cat /proc/partitions gives mntblock9 as 35584 blocks which is roughly 17Mb... Hmm, no other partitions reported are in the 40Mb range, as they're supposed to be...

At least, you've given me something to think about... I'll keep on poking around to see if I can get anywhere!

Thanks,

Edit: Yay!  I've managed to get v1.8.4 onto the unit using telnet and the cp command... Now, just need to find a way to get the drive to the right size so I can get the custom firmware on....

(Last Edited by slaphead on December 12, 2011, 4:41 pm)
December 12, 2011, 1:57 pm #15

/mnt/mmc is the SD card
/mnt/mtdblock9 is the internal flash memory.

If mtdblock9 does not have your files, then they are probably in the lost&found or some place in outerspace

 

 

December 12, 2011, 1:37 pm #16
I'll give it a go... Problem is, I can't see where the internal is mounted. fdisk -l doesn't give any response, and all the various options in /mnt doesn't seem to be the internal storage (mnt/mtdblock9 seems to have the right size/capacity, but all that's in there is a full lost+found directory. Not the items I've copied to internal in the past...)

Thanks,
December 12, 2011, 10:12 am #17
Thinking of it, there might be an alternative.
Did you already try to connect via telnet?
In that case you can copy a file from the SD card to internal memory at linux level.
Parhaps that works..
December 12, 2011, 9:55 am #18
Yes, it seems that the internal memory is hosed, and the radio isn't "seeing" it.

It won't load the new firmware either. "ejecting" from XP doesn't work, on 2 different machines.

So it seems like I'm stuck on the crappy old firmware
December 9, 2011, 12:55 pm #19

I would be extremely careful with formats and file changes on the Xenta.
First thing you should try to do is connect the device to a different Windows XP (maybe 7) computer. If you dont have one around, visit a friend or relative.
On that PC try to do the eject from "My Computer" after copying the firmware.
Another thing you could try is a factory reset.

Note that the original firmware has a check for some of the internal file systems.
If this check fails the firmware tries to repair it automatically. Sounds good..
However, this repair is not going to work. It will only make the problem worse!!!!


This is most likely the thing that causes the bootup with a logo and then hanging the device.
At that point the flash memory is erased and it is close to impossible to repair it.
I have an Arnova board on my workbench that is also in this state. So far all (regular) attempts to fix it failed.

 

 

 

December 9, 2011, 12:23 pm #20
I'll connect mine up some time over the weekend, and get as much infomation on file type, name, size, etc. at some point today and post back. If you can re-re-reformat yours to an identical version of mine, I guess it should work.

If you post any detailed info on yours here, we can compare like-for-like.

(Mine is already running William's first version of the software (not the latest all-singing one), so it's not Ebuyer - fresh, as it were. Might help, though.

I'll get back later this weekend with as much info as I can find out!

Ben

EDIT: Can't give you numbers & data yet, can confirm mine plays mp3 files & displays photos (not too large images) from both the internal memory and SD card. However, when I mis-ejected having written MP3 file to internal memory, on restarting the radio, the MP3 wasn't visible to the Xenta, although it was there when re-attached to the computer... and the computer could play it from the Xenta.... so all the problems you have could be related to the "eject" problem.  OK, I need to sort out the files on the Xenta drive, copy them somewhere, then re-format for a clean drive. I'll do that this evening.

Just to reiterate (the bleeding obvious, I'm sure, so sorry), I copy MP3 and photo files (640X480 jpeg) to the internal memory of the Xenta, then go to "My Computer, and right click on the Xenta, choose "eject", then get a "you can safely disconnect..", so I then power off the Xenta (which has batteries in it as well) then power it up again, and get it to play internal memory photos & pictures. It'll do both at the same time).

So, does yours behave, or should you hit it?

Ben

(Last Edited by benjh on December 9, 2011, 12:41 pm)
December 9, 2011, 11:04 am #21
OK,

It seems that when I formatted the internal drive, I've knackered something. To test, I copied a couple of MP3s to the internal drive, and when I select "play stored media" (from internal memory),  I get an error of no media found...

So, I think formatting it may have changed the name / partition table of the drive, and as a result the unit can't read it... Can read SD card fine (even through telnet), but obviously can't update firmware from SD...

Anyone got any ideas? Grr. Just when the new firmware arrives too!



(Last Edited by slaphead on December 9, 2011, 12:09 pm)
December 7, 2011, 5:00 pm #22
Looks like William's Firmware is just on the point of being released, so I'm guessing you might as well have a go with that rather tahn the older one. I'm at a loss as to why it isn't working - but I'm no expert. When I update mine, I'll make careful note of what I do, what happens, and when, in case that helps you - or any other poor sod!

I keep looking for more (cheap ) versions of this radio... no real luck yet. Oh, and I do mean cheap.... Ebuyer sold off some of their Vistron IR's for £8.99 a few days ago... and I missed them!
December 6, 2011, 3:24 pm #23
Thanks for your help, still no luck.

I've used telnet to get into the machine and have poke around. From what I can tell, the machine cannot see the internal memory... I've looked in every directory under /mnt and none have the update-firmware.bin in. Obviously, I may be barking up the wrong tree, but thought it worth a mention.

Is it worth trying the WIFI hijack thing that I've seen mentioned for other models?

Edit: I tried the wifi hijack (ish - I spoofed the webaddress in the Xenta's hosts file to point to my webserver), and it still failed with File Error.

Oh well, the new firmware is here now, so I'll give that a go ASAP. Really hope this works!

(Last Edited by slaphead on December 7, 2011, 10:43 am)
December 5, 2011, 4:17 pm #24
Mine is formatted as FAT...

Just had a look, and it still throws up the error as well, even though I "fixed " it! Indeed, it re-finds an error each time, but none reported as found to fix when I accept scan.

Might be worth a reformat in FAT, and shove the update-firmware across again. My primitive logic suggests that if you can't easily get the currrent update across, the new one might struggle for the same reason.

Give it a reformat, see what happens!


December 5, 2011, 10:45 am #25
Thanks benjh,

That MD5 is the same as mine. Nevermind... the major release seems to be coming very soon, hopefully I'll get that to work!
December 2, 2011, 6:05 pm #26
Yes, will do, but it's on another machine... be Monday before I can get at it (unless I left the computer on, in which case I can get it remotely tonight!). Best thing for work computers is downloading stuff!


Edit:
It was still on... checksum is
e166d59917d9aeee0861332246a2a1fc
Xenta_FW184
(13,891,521 bytes)

(Last Edited by benjh on December 2, 2011, 6:10 pm)
December 2, 2011, 2:49 pm #27
Nope, turning off the computer after "eject" didn't do anything, still gave a file error. Thanks for the suggestion anyway.

I compared the MD5sum of 3 different downloads, so I would assume that one was successful? Any change you can give me the MD5 of yours?

Thanks,
December 2, 2011, 12:08 pm #28
A boring answer to ensure safe ejection would be to power down the computer. My Xenta was also from Ebuyer, 1.7 installed. There were errors on the  drive, according to Windows, and I let it fix them. The upgrade did work for me.

By the way, I haven't seen an MD5 checksum for the download....
December 2, 2011, 10:42 am #29
I've tried it on XP, and the Eject link in my computer doesn't do anything... the drive remains in my computer and the only way to eject is via the "safely remove hardware" in the panel...

December 1, 2011, 4:36 pm #30
Yes, it seems the file is always corrupted when using Linux.
December 1, 2011, 3:59 pm #31
Yes.

I'm primarily on Linux and it didn't work there, but have also booted into Microsoft (XP & 7) and it doesn't work from either!

Thanks.
December 1, 2011, 3:21 pm #32
You are currently on 1.7 firmware?
December 1, 2011, 2:50 pm #33
Afraid that didn't work either.

Oh well, I'll wait for the "big" firmware, and hope that works!

Thanks any way.
December 1, 2011, 1:46 pm #34

Label does not matter.
In most cases the reason this file error appears is because of how the device handles the PC connection and how this connection is ended.

The only way that works correctly is to go into "My Computer" and "Eject" the flash drive you just copied the firmware file to.

If you use eject from the taskbar it fails. So you really need to eject via"the "My Computer" panel.

~W.

December 1, 2011, 1:37 pm #35
I've been trying to update the firmware on my ebuyer Xenta KMP510 but I get "file Error" on doing so. MD5sum matches that on my harddrive and the unit, and I've downloaded 3 times to ensure it wasn't corrupt download.

The only thing I can think is that I had to reformat the internal drive space to get it to copy. I've formatted to fat32 (which I believe was the same as original), what label should I give? Or will the label not matter?

Thanks!
Main Board Index Forum Index
 
 

Get notified of new forum posts via