members.png
Jun 13

Firmware update fails if using new exfat format in V-52 firmware

6 comments

Edited: Jun 14

@Rock Liu

I just tested the new V-52 firmware and discovered, that firmware updates fails if the sd card is formatted in the new exfat format. The K2.bin on the sd card is simply deleted, but no update occurs. This could bring new customers/users into trouble, as the V-52 firmware now always formats the sd card as exfat when using the app.

 

Means: If someone installs the new V-52 firmware and formats his sd card using the app, he will not be able to do any further firmware updates, as long as he does not re-format the sd card as fat32 (or use a different sd card).

 

Flashing-Log looks like this

NP>T
Loader Start ...
663_DDR3_LV1_587_2048Mb 05/10/2018 11:33:42
R
card open fail

 

It seems that the bootloader, which is responsible for flashing, cannot handle the exfat format ("card open fail") and therefore fails. After that, the normal boot process deletes the K2.bin.

 

 

Normal flashing-log looks like this

NP>T
Loader Start ...
663_DDR3_LV1_587_2048Mb 05/10/2018 11:33:42
RRRRWDT init
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRFullComp
SPI NOR detected
Ud FW
eeeeeeeeEEEEEEEEEEEE...and so on. 

 

 

I'm not sure if your developers can fix this, because as far as I know (and understand the K2), the bootloader cannot be flashed using the normal update process. It can only be flashed using the usb port and a special program.

 

 

 

Jun 15

Thank you for such finding.

Will do further check Monday and keep you updated.

Good find Frostie! I'll hang fire updating the firmware until it's been looked in to.

N.

Jun 19

Frostie, You are right!

 

It is clear from below, fixed one problem but create other. I would like to learn that if it is necessary for such update.

 

 

 

Jun 19

 

One thing you should mention in the firmware notes is, that the user has to format the SD Card using the App, if he wants to use the EXFAT format.

Simply formatting a FAT32 card to EXFAT on the PC will not work, because the K2 expects a different partition layout for EXFAT than for FAT32

 

SD Card with FAT32, formatted by V49-Firmware looks like this

<----4MB unallocated space---->|<----Partition---->

 

SD Card with EXFAT, formatted by V52-Firmware looks like this

<----16MB unallocated space---->|<----Partition---->

 

So if you simply format a FAT32 Card as EXFAT on the PC, the Partition layout is incorrect for the K2 and it will not start recording (lots of error messages in Log).

I found myself in this same situation that Frostie referenced, but on 57.

Updated to 57 (frostie-modified version for higher bitrate) then formatted the SDcard via the app. Was scratching my head for a bit wondering why it was not recording footage. Aside from not recording, I was also not able to flash to an earlier version or even the base version.

I found this thread and realized what that my partitioning might be the problem. I ended up deleting my partition table and used rufus (on the PC) to get FAT32 on my card. Flashed back to 49 (frostie-modified w/higher bitrate). Everything looks good.

Out of curiosity, is there an official procedure for downgrading if on EXFAT (formatted via app).

Also, Frostie, what "special program" can be used to do it via USB?

Jul 10

 

Out of curiosity, is there an official procedure for downgrading if on EXFAT (formatted via app).

As far as I know, there is no official way. But the only possible way is to use a FAT32 formatted SD Card for flashing. Regardless whether up- or downgrading.

 

Also, Frostie, what "special program" can be used to do it via USB?

This is a misunderstanding. You cannot flash the firmware of the K2 via USB.

My comment was about the bootloader, which can probably only be flashed via USB. This was more towards Rock to show that the they cannot solve this problem by simply updating the bootloader. as the customer wil not be able to flash it.

 

 

New Posts
  • Had the K2 for 5 days now. Overall its pretty good. I have a few issues that I need to look into. 1 - The lens seems to black out in the bottom (say 4 and 8 O'Clock) A bit like the lens has Glaucoma... 2 - I start my bike, put helmet, gloves on, ride off, but recording doesn't start until I am a few miles away, has to be at least 5 minutes after setting off, and maybe 6 minutes after starting the bike. An I supposed to wais 6 minutes before setting off? 3 - I have to do something with how I transfer the files, WiFi just doesn't cut it. My bike (R1250GS Adventure) automatically powers off after X minutes, not sure exactly how many, to preserve the battery, the WiFi hasn't managed to transfer a 3 minute file before the bike powers off. I cant view from the bike, stream, as it doesn't stream, it just jitters from frame to frame. I have an iPhone XS Max if that makes any difference. So far I have not been able to download or view any recording, only when setting up on live view. On the plus side, it only took 30 minutes to set up on the bike, only having to remove the tank panel. Does anyone have any thoughts on my three issues?
  • After the firmware v61 update, I noticed the blue light on the power transformer never goes off - no matter how long the bike is off. Is this normal? What could possibly be powering this other than my battery?
  • I'm at a slight disadvantage, as my bike is still in a container ship, travelling back to the US, but I'll see if I can make my point clearly enough. I've been told that if I connect to the K2, using WiFi, and the K2 App on my cell phone, that the time would be correctly set within the K2. I'm afraid that this is not correct, at least it's not correct under a few sets of circumstances. First of all, in certain parts of the world, you need to set your phone to override the current time, and set it manually. For instance, all of China uses a single timezone (Beijing time), but my iPhone got confused, and thought that there were multiple time zones, and so, I had to override the time setting. As a result, although I connected my iPhone to the K2WiFi, and then enabled the IOS app, and selected settings, I still ended up with a situation where the time on the K2 was at least 1 hour different from the time on my phone. Throughout my trip, I often tried to get the time of the K2 to be properly set, and I think that I achieved it only once. In all other cases, it was between 1 and 2 hours off. So, my question is, why don't you allow me to set the time, or select the time zone within the K2, rather than relying on using the Phone? As IOS versions on the phone change, it is likely that they'll handle time zones differently, perhaps forcing you to make odd choices in some cases, but if I was able to manually set the time zone in the K2, we eliminate any chance that the system will have the wrong time. The outcome, if you want to set the time, connect to the K2 over WiFi, set the time, and exit. It's just about perfect, and it addresses all of the possible irregularities that exist as we travel around the world. Thoughts?
© INNOVV TECH CO., LTD @ 2013~2019
  • w-tbird
  • w-facebook
  • w-googleplus