This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
DS203 missing shell.elf #28
Comments
|
Try this firmware: And copy these files to devices: If it won't work, please send here screenshot of the root of the device's filesystem |
|
Hi gab, |
|
I just tried the files I provided and with the same result as in your case. For some strange reason, the filesystem gets corrupted when I copied all the files at once. After reconnecting I saw only empty root folder. But when I copied only the shell.elf to the disk, it worked. And then when the shell was loaded I copied remaining elf files. So please try to delete all *.elf files you copied before and copy only "shell.elf". Or try copying the file until the device will find it, possibly device format could help (dont forget to backup your CALIB.DAT and CONFIG.DAT) |
|
Unfortunately no luck always missing shell.elf (tried to format both quick and standard). I tried either pressing f1 directly after copying or doing power cycle (several times). |
|
Just out of curiosity, please drop here screenshot of the disk root and hex view of the shell.elf |
|
Hi,
thank you! |
|
try running "fsutil fsinfo sectorInfo e:" and "fsutil fsinfo ntfsinfo e:", this should show us how the disk is formatted, the disk should have 4096 sectors and every sector should have 512 bytes, on OSX: |
|
Hello gab, |
|
Yes that is a problem, the disk parameters are hard coded in the firmware. I do not own DS203 with 8MB disk, but if you can tell me what is the sector size and how many sectors are in that disk, I can prepare a build for you (and for others who own this newer version of DSO203), on linux try this command "fdisk -l" |
|
From what I can see from windows it is exactly 8.388.608 byte with 4096 byte/sector and 2048 total sectors. |
|
Try this |
|
Copied in DFU mode the new system, now it goes directly in file manager mode.
|
|
Try one of these, maybe it will work. Their (minidso's) bios use different memory layout, because it needs bigger buffer for the filesystem (4k vs. 512), so I tried to build the app for different memory locations: |
|
No luck always hardware fault :-( |
|
Without having access to your device it is very difficult to fix this issue. And when it says that there is problem with FPGA, then also the oscilloscope functions wont work even when the application was running. |
|
Ok thanks a lot anyway. The FPGA error has been resolved with the recovery with serial. Do you know if I can copy the old version of your system on the 8m version? (the GAB_N1.hex, N2, N3 and N4) |
|
I did quite the same as @Compycompy and ended up with the FPGA configuration error and corrupted logo. I have HW version 2.72. Any chance to get this working or revert to the old version? First try:
Next try:
Starting webosc using the file manager didn't work with Chrome and https://l.valky.eu/webusbds203v2. So I tried with PulseView and selecting "Openbench ...(ols)" as input and got this error: Trying to revert: //edit: |
|
@Compycompy can you tell me how you did the recovery with serial? Where did you get the binaries for the FPGA? |
|
Hello guys, do any of you have working 8MB device with original fw? Could you please share flash image of your device? I am trying to put together all flash images for recovery purposes. Thank you! (fyi: @nutz88) |
|
Hi. |
|
You can find the original fw for HW version <= 2.72 here: http://jpa.kapsi.fi/dsoquad/ as DS203.V2.72.zip |
|
Forgot to mention: My Hardware version is 2.82, Sys ver 1.64. |
|
You can find Firmware 2.81 with FPGA binaries for HW version >= 2.82 here: http://minidso.com/forum.php?mod=viewthread&tid=666&extra=page%3D1 |
Hello @acidg Thanks so much for putting this together. Really appreciate it. |
Hi @Compycompy Could you please point us or share how to proceed with the serial recovery to fix the FPGA issue? Thank you. |
|
@Sergio- it is nearly impossible to brick the device, DS203 can be recovered using the internal uart connection: https://github.com/gabonator/LA104/tree/master/tools/stm32flash |
Hi @gabonator! First of all, thanks for the reply. I'll explain below what I did to recover from UART, hoping that others can user the information too. I then disconnected the B0 from VCC, powered off the device and on again. The other issue is that, when booting pressing F1, the DFU disk is not being mounted anymore. The logs shows the message below: To summarize: The device now boots up, but it seems it's not working as intended still. |
|
@Sergio- During powerup, what does it say about FPGA configuration? When you connect CH1 to signal generator, does it show any signal? If you are using FW from jpa, he made there a little hack that skips license verification, with original fw it wouldn't let you go further. If you are having problems with DFU drive, you can try uploading new firmwares (HEX files) through this utility https://github.com/gabonator/LA104/tree/master/tools/dfuload It seems you just need to find the right fw for your device. Or maybe just fpga image. Maybe we could ask guys here for a help: Anyone here with working DS203 V2.82 8MB and willing to share its flash dump with us? |
Hi @gabonator Thanks for the reply! |
|
@Sergio- |
|
not sure, if this is worth anything but seems related and maybe it gets you a tiny bit closer: #26 |
|
I am using this command to format LA104 fs, and the DS203 8MB has the same sector size, so maybe it will help: sudo newfs_msdos -F 12 -v la104 -O "MSDOS5.0" -S 4096 /dev/disk2 -F 12 (fat12) edit: @Quas7 shows in his post how to format on ubuntu if newfs_msdos is not available, so just ignore my message |
|
Hi Folks. Thanks for the suggestions. The command below did the trick on my Linux machine: I believe with that all the functions are back to normal. I didn't start using the device, but I believe it should be fine. Thanks a lot @MotoMaxis @gabonator @Quas7 for the effort in helping restoring the device. I believe this thread now contains a good knowledge to help others with similar issues. :-) @gabonator Back to the original theme of this thread... Is there a way to install your version on the v2.82 Hardware? Is there any information I can extract from my device that can help you with that? Thanks a lot. |
|
@sergio, Finally words of success. I am glad to have been able to participate. @gabonator I am also interested in beta testing your firmware on my DS203 HW2.83 8MB flash. The DFU V3.46C stores the License code of a device at 0xFC to 0xFF in reverse (Little Endian) format. You can use a hex editor to enter your own code. A stock DFU has FFFFFFFF in said location. As far as I know, the only known way to flash DFU is by UART. WARNING |
|
Hi Sergio and anyone else, could you test this Wildcat V6.5 modified firmware on a 2.81 or 2.82 device? Make sure there are no CONF00x.CFG files on 8MB drive. We are testing new file creation. Thank you. |
|
Hi @MotoMaxis Yes. It worked. |
|
Actually the before version only works for default 000.cfg. But fails for others unless conf001.cfg to 009 already exist. The test version has a minor update to automatically create new files for 001 to 009. Edit: Uploaded both fixes to https://github.com/MotoMaxis/DS203-DSOQuad as well as compiled hex. |
|
Also trying to run webosc on my DS203 hw2.83 8mb. Windows 7 can't find the driver. |
|
@MotoMaxis it is mentioned in the project readme: https://github.com/gabonator/LA104/blob/master/system/apps_featured/69_webusbosc/readme.md On windows machine you will need to generate "winusb" driver. And this tool does it for you: https://zadig.akeo.ie/ |
@MotoMaxis What's the link to the compiled Hex files? |
|
Thank you for the tip. While testing yesterday I noticed one issue. After flashing the system_ds203hd.hex and trying all the elf files I flashed back the Wildcat6.5 expecting it to work but it was stuck on FPGA error. Flashing the FPGA fixed the error. So it seems it got corrupted somehow. The area in question is 0805C800 - FPGA - 0807D7FF. You main app loads to 0800C000 - 08012740. @sergio |
|
@MotoMaxis |
|
What about these? They fit in 0805C800 - FPGA - 0807D7FF 135K Only DS203 Hardware Ver 2.81 and 2.82 8MB flash Perhaps these elfs can be moved to |
|
Aaah, I see now. I put wrong addresses in the script which checks the collision. Yes, they can be moved. Or in better, I will make separate builds for ds213 hd, sice at those addresses it was tested on ds203/ds213. |
|
Sorry, I was wrong in saying that available space starts at 08080000. That is actually the end of the eeprom on a 512KB chip. We can possibly use 1.9KB after the LOGO at 0807F880 to 0807FFF . About 11.7KB after SYS at 08009190 to 0800BFFF. And all of 329.7KB of APP space from 0800C000 to 0805C7FF. As far as I know, thats it. Happy New Year everyone. |
|
So I've relocated WebOsc to 08023000 to not corrupt the FPGA at 0805C800 on DS203 2.82 8MB. Now flashing back WC6.5 works. Anyways, after opening the site, it shows DS203 paired but stuck saying Connecting... Now not sure whats wrong. If anyone want to try, DFU copy the system. Restart normally nd copy 2 elf files. Restart the run webosc. Fyi, I had to format 8MB before files showed up. |
|
Happy New Year everyone! I hope all of you and your families are safe and healthy. @MotoMaxis, what does chrome say in the debug console? When you try to connect (through the webosc html interface), does it show the DS203 in list of available devices? I dont know if it is the same in windows, but the firmware just uses a regular CDC (serial link) usb. So you can open the port as serial port and then communicate with it. And you can easily verify if it is communicating by sending
and it should reply
Do you have memory layouts also for other DSxxx devices? I would like to put together this information from each device to improve the app placement. Ideal case would be achieved when no application would be overlapping any other, so you can switch between them even without flashing the eeprom. |
|
Happy New 2021 Year everyone. @gabonator, Thank you for the tip. Originally I installed WebUSB driver using zadig-2.5.exe but now installed CDCSerial and see Com34 in device manager. I no longer get the popup when plugging in the DSO. Here is what chrome says. So next I used HyperTerminal to connect to that port. As soon as I press a key, it Hard Faults. Happens with stock and relocated webosc. I do not have info about other devices. But do own DS201, DS202 and DS203. Thank you for your hard work. Update: I don't understand why failing at 080233A8. A Push command. Maybe stack overflow? Segmentation from elf |
|
GetRpcAddress is called when a line was received over serial link (line ended with \n). After typing a single letter, it should not call this function. I looked at the disassembly and got different one. Mine says 080233A8 is in _ZN4BIOS3LOW8SetParamEii after relocating ROM begin to 0x08023000 (compiling with gcc-arm-none-eabi-9-2020-q2-update on osx) In the build folder, there is also assembly listing file, just for such cases when we need to trace the error. It could be caused by stack size. Hard to tell, you can try changing the stack size here, if it helps: system/os_host/app_ds203.ld: Reading the documentation about HFSR/CFSR (https://www.keil.com/appnotes/files/apnt209.pdf), it says this: |
|
I came across a nice small FLDump utility by bobtidey that lets you make a full image dump of your DSO. I modified it to dump 512KB instead of 256KB. You simply copy FL_DUMP4.HEX or (FL_DUMP4.ADR then FL_DUMP4.BIN) to device. Reboot with Button 4 pressed. When it's done you should see FLASH.BIN on the drive. credits: bobtidey |
|
Hi! Have you got this fw running on DS203 2.82 hw? In spite the fact that I could not use our fw. I'm still interested in an potion how I could use it on my device. I need a solution to be able to make long time aquisitions, and I hope taht I will be able to do that with your fw or at least that It I will be able to write an app to to that. Another question would be if it is possible to run four fw. in slot 3 or 4? Thanks! |
|
Hi, I was not able to make webosc.elf to work on DS203 2.82 hw. Always get HARDFAULT. I tried moving it to different area but it didn't help. We are waiting for gabonator to look into it. On a side note, Wildcat fw has the Chart mode with extended time base of 100mS/div to 10min/div and the ability to Auto save to .csv until memory full. Check out -CHART MODE: in https://github.com/MotoMaxis/DS203-DSOQuad/blob/master/WildcatV6.5/User%20Guide%20V5.6-6.5.pdf I am not sure if we can squeeze both firmwares on same device. It will require recompiling Wildcat to shift it to unused areas. But gabonator is one to know the answer. |
Oh, thanks for that! |
|
On screen with meters off we see 13 divisions so that's 130 minutes. But if you enable auto log to .csv files then its until the flash drive becomes full. I think its over 6 full days on a 8MB device. Each file has 4094 samples that are about 100KB in size. |
|
I got that but not idea on how much fits on an empty flash drive?
Can I store for example 24 hours?
…On Sun, Feb 7, 2021 at 10:52 PM MotoMaxis ***@***.***> wrote:
On screen with meters off we see 13 divisions so that's 130 minutes. But
if log to .csv then its until flash drive becomes full.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA224X3HY7LHEPRFCOIM4ILS54DQTANCNFSM4TJ32HXA>
.
|
|
Oh 24 hours is easy to do. Chart mode works only in Full size buffer mode orange with scrolling rectangle at the bottom. . Which is 13 divisions times about 10 screens. That's about 4094 samples I think. |
|
I might be wrong but I just try to understand the math behind :-)
We have 13 divisions, so the buffer is enough for:
@ 100ms/div (0.1sec/div) we should get 0.1 x 13 = 1.3sec (not 13)
@ 10min/div x 13 = 130min = aprox 2.1hr (not 20)
Assuming that the buffer space buffering the 13 divisions uses 100kb then
the 8Mb will last for
80 x 1.3sec (approx 100sec)
to
80 x 2.1hr (approx 168 hours)
Am I wrong?
…On Mon, Feb 8, 2021 at 9:28 AM MotoMaxis ***@***.***> wrote:
Oh 24 hours is easy to do.
It will depend on how fast you tell it to acquire a reading. The fastest
time in Chart mode is 100ms/div and slowest is 10min/div which is a range
of 13sec to about 20 hours to fill in the buffer. This will use up about
100KB of space. So I think you could max our in 20 minutes with fastest
speed to something like 60 days with slowest speed. .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA224X44EFI3VH6KGMRMO4TS56OCTANCNFSM4TJ32HXA>
.
|
|
Once the screen fills up it will start scrolling through 10 more screens then loop back to the beginning. . |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello,
I have a DS203 currently with wildcat 6.5 hw 2.81 sys 1.64
I went in DSU mode and copied the ds203.hex file, all went fine.
Disconnected, restarted and asked for shell.elf, I copied the elf files but still keeps on asking for the shell.elf file.
I believe there is some issue with the memory location as it seems to look in another part but I am not sure.
Any suggestion?
The text was updated successfully, but these errors were encountered: