A licence code please!

sam

Hi there! I finally got the flasher working; can someone please provide me with a licence code?
HW 2.72
Serial 4A02A87F
sys 1.62
Thanks in advance

minidso

sermartynov 发表于 2016-12-15 03:46
Hi guys,

could you help me with license number for my DS203 v2.72

Try F321706B

flagmax

try CB6FB99C

sam

Fantastic, that worked. Thanks flagmax

sam

okie dokie, so:
- I was trying to fix a problem that when I plug my unit into the computer in 'Upgrade mode' (holding the >|| button down on startup) Windows (7, and tried XP also) only recognise the DFU virtual disk (labelled DFU V3_14_C) as being 503,808 Bytes/492KB - too small for an image
- I have reflashed my DS203V2.7B DFU firmware using the guide in Tutorial: How to flash/debrick/update DFU on DSO203 HW V2.81 (using the v2.7 firmware provided at the end)
- Plugging in with the upgrade mode again, the virtual disk is *still* 492KB (again, both W7 and XP)...
- So this means I can't install any other firmware on the device...
- In addition to above info, Device firmware upgrade V3.14C, APP (PLUS A1) V1.12. I also have a message 'Parameter record not found' on startup.


I'm all out of ideas, but I really hope someone else isn't! Can anyone please provide some help?
Thanks!

sagittarius

sam 发表于 2016-8-29 17:59
okie dokie, so:
- I was trying to fix a problem that when I plug my unit into the computer in 'Upgra ...

DFU virtual disk is a virtual disk, can satisfy the firmware upgrade, disk size is not important, can upgrade the firmware.
Not storing firmware, images is what you say, what to do.

Parameter record not found, this mean can not find a personal set of Parameter file, you can save Param again.

sam

Thanks for your response Sagittarius. I'm confused now; if my .hex file is say 2Mb, windows will not allow me to place the file onto the virtual disk because of a check of available space. Are you saying there is some bypass for placing the .hex files into the dfu disk? Cheers, Sam

sagittarius

sam 发表于 2016-9-1 06:27
Thanks for your response Sagittarius. I'm confused now; if my .hex file is say 2Mb, windows will not ...

. Hex file cannot be greater than 2 m, MCU is no storage space, the size of DFU mode is a transfer space, put. Hex file storage to MUC, are stored in multiple division, he is not a one-time storage. Hex file

sam

Thanks again Sagittarius, I appreciate your time. Unfortunately, I don't understand your previous post sorry!

The size for example,
- The 'gabonator' program is ~ 2.31MB
- The APP_G251 program is 677KB
so neither of those files will copy to the DFU upgrade virtual disk in widows (see the attached screen shot)

By transfer space, do you mean that disk is a ring buffer which is unloaded by the MCU? If so, how would anyone copy files to the unit using the 'standard' windows copy+paste?

PS i successfully upgraded the SYS version from 1.62 to 1.64 using the file supplied in this link; http://minidso.com/forum.php?mod ... &extra=#pid2038

Cheers
Sam

sam

Bah, I have proven the saying 'there's no such thing as stupid questions, only stupid people'. Sure enough, I'm not downloading the firmware files correctly. So, @Sagittarius, please forgive my previous dumb question and thanks for your patience.
However, I've now found a new problem!!! (Again, which i need help with Please let me know if I should start a new thread)

I have tried loading the GCC community firmware, and the gabonator firmware, received the *.rdy upload confirmation, however whenever I try and restart the DSO (in any of the 'memory slot' modes, I am only ever presented with the default application. Furthermore, if I try and load a program in slot 2, 3 or 4 the thing just continually beeps at me and shows a screen with HW, Serial and SYS numbers.
Any ideas on this one?

sagittarius

sam 发表于 2016-9-6 17:54
Bah, I have proven the saying 'there's no such thing as stupid questions, only stupid people'. Sure  ...

Upgrade, the .hex file name not more than 8 characters. Gabonator firmware is not the official firmware, we can't ensure that he can run normally. Some firmware capacity beyond the scope of an APP, he will take up the position of the next APP, if it is too big, is likely to take up the position of the 4 APP.