you firmware are based on free communiti code
you don't have any rights to sale it
I am ashamed of what makes my former compatriots.
[i]Таких как ты мы в детстве называли курками. Это от слова куркуль. Руки им никто не подавал.[/i]
как же называются те кто ничего не делает , и хочет пользоваться бесплатно тем что другие делают?
а самое главное я платил за осциллограф вместе с ( открытой прошивкой ) деньги и как оказалось с кучей багов , за что надо возвращать товар, и до сих пор официальная прошивка непригодна для использования.
я знаю много людей которые покупали осциллограф только из-за моей прошивки, так скажите кому я сделал плохо, кроме тех кого жаба давит?
Люди здесь делятся наработками бесплатно. Но тебя это делать никто не заставляет - написал мод, сиди и жмись сколько угодно.
А вот продавать его ты не имеешь права. Хочешь продавать - пиши всё с нуля, иначе это элементарная торговля краденым.
Люди здесь делятся наработками бесплатно. Но тебя это делать никто не заставляет - написал мод, сиди и жмись сколько угодно.
А вот продавать его ты не имеешь права. Хочешь продавать - пиши всё с нуля, иначе это элементарная торговля краденым.
если я увеличиваю кол-во продаж осциллографа , то у кого я что украл?
functions that I implemented are not based on GPL,
Where are your sources, I want to see your firmware version for DSO, possible without the source code.
You added some functions to GPL code. So the whole thing is GPL. You are in violation if you don’t release your changes.
[code]
v1.26
v1.25
[code]
v1.27
Thanks very much for this and thanks to Wildcat for the material merged in.
Loaded up and running OK.
Hi PMOS,
WOW! What a tremendous amount of work you’ve put into this! Thank you soooo much for making this scope so much better.
Dan
Nice one!
I notice channel B is still noisier than A. Maybe there’s a bug in the PCB.
Another thing! I can’t find how to enable and change manual trigger threshold in this version. Can you explain me how to do it? Thanks!
Nice one!
I notice channel B is still noisier than A. Maybe there's a bug in the PCB.
Another thing! I can't find how to enable and change manual trigger threshold in this version. Can you explain me how to do it? Thanks!
Thanks Jack,
I finally had some free time that I could spend with this. All thanks to Wildcat though. He did a tremendous job.
To change to manual trigger adjustment:
[code]
v1.28
[code]
v1.29
Hi,
I tried to upgrade my firmware, for the first time.
The hardware is v2.6.
I followed this wiki:
<LINK_TEXT text=“http://www.seeedstudio.com/wiki/DSO_Qua … g_Firmware”>http://www.seeedstudio.com/wiki/DSO_Quad:Upgrading_Firmware</LINK_TEXT>
I downloaded this files:
http://pmos69.net/dso203/
(SYS25116.hex, APP_G251.hex, FPGA261.zip)
wget http://www.seeedstudio.com/wiki/images/3/31/Dso.img.zip
I go to the upgrade mode (>|| button holding while powering up).
I copied SYS25116.hex to /mnt/dso (linux), I powered off an on again the dso (slide-switch), the file was renamed to .RDY. I have not unplugged the mini-usb cable.
Then I copied APP_G251.hex, the file has been disappeared, after on-off cycle, instead of renamed to APP_G251.rdy.
Before upgrading the FPGA, I tried to power on the device and see the new app in action.
I powered on, and the dso quad stuck at the INIT SCREEN.
I see this:
[code]
DSO QUAD
Hardware Ver 2.6 Serial No: E9A0B87E
DS203 Mini DSO SYS Ver 1.31
GCC v1.29 APP Community Edition
[/code]
After I did copied the FPGA files too (CFG_FPGA.ADR, power cycle, V261FPGA.BIN).
Still no luck.
When I plug into computer (while this init screen is showing), the computer does not recognize it.
So I could not copy Dso.img.zip file with dd command to the device.
I tried to dd the Dso.img.zip while in DFU mode, I got this:
</s><i>
</i># bunzip2 Dso.img.zip --stdout | dd of=/dev/sdb
dd: writing to: ”/dev/sdb”: No more space left on device
1025+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 2,03603 s, 258 kB/s
<e>
Any helping hands?
Ok, before power cycle, I can do a umount/mount cycle, and check of the upgrade result:
SYS25116.hex -> SYS25116.RDY
APP_G251.hex -> APP_G251.RDY
CFG_FPGA.ADR -> CFG_FPGA.ERR
Dunno, should I proceed with V261FPGA.BIN too?
Why the error?
Ok, I proceeded:
V261FPGA.BIN -> V261FPGA.NOT
Any hint?
Some more tries:
downloaded FPGA_v222:
http://garden.seeedstudio.com/images/2/23/FPGA_V222.rar
CFG_FPGA.ADR -> CFG_FPGA.SET
V222FPGA.BIN -> V222FPGA.NOT
downloaded FPGA_V25:
http://garden.seeedstudio.com/images/1/12/FPGA_V25.rar
CFG_FPGA.ADR -> CFG_FPGA.SET
FPGA_V25.BIN -> FPGA_V25.NOT
Ok, I really stuck.
Maybe the firmware upgrade is too old?
I see this:
[code]
DSO QUAD
Device Firmware Upgrade V3.10
Please copy .Hex/.Bin file to
DFU virtual USB disk.
[/code]
Best,
Laszlo
Reading the wiki one more time, I got the idea, what if I reupload an older sys, app, fpga firmwares in that order, and maybe the fpga down the line success.
So, downloaded:
http://garden.seeedstudio.com/images/c/c4/SYS_B134.rar
http://garden.seeedstudio.com/images/f/f9/APP_B232.rar
http://garden.seeedstudio.com/images/2/23/FPGA_V222.rar
And uploaded to the devices, one by one:
SYS_B134.hex -> SYS_B134.RDY
APP_B232.hex -> APP_B232.RDY
CFG_FPGA.ADR -> CFG_FPGA.SET
V222FPGA.BIN -> V222FPGA.NOT
Also tried these too:
Sys_151: <LINK_TEXT text=“http://www.seeedstudio.com/forum/downlo … php?id=857”>http://www.seeedstudio.com/forum/download/file.php?id=857</LINK_TEXT>
App_252: <LINK_TEXT text=“http://www.seeedstudio.com/forum/downlo … php?id=856”>http://www.seeedstudio.com/forum/download/file.php?id=856</LINK_TEXT>
FPGA261: <LINK_TEXT text=“http://www.seeedstudio.com/forum/downlo … php?id=858”>http://www.seeedstudio.com/forum/download/file.php?id=858</LINK_TEXT>
SYS_B151.hex -> SYS_B151.RDY
AP1_B252.hex -> AP1_B252.RDY
CFG_FPGA.ADR -> CFG_FPGA.SET
V261FPGA.BIN -> V261FPGA.NOT
Still no luck. Any more ideas?
Best,
Laszlo
Bravo to the authors for the great work.
When can we expect a new version.
Regards, Peter!
Available time has been quite rare, so I can’t really say.
I have a few things in the development ToDo, but haven’t been able to get anything done.
(unless more code contributions come in, and in that case I’ll have to find the time)
This DSO203 GCC APP works with hardware 2.7 ?
pmos69, thanks for the great work and fast response.
If I can give some suggestions: