![]() ![]() Make the downloaded AppImage file executable 3. However, if one insists to use PulseView in Linux: 1. However, the latest PulseView might have some extra protocol decoders that were not yet ported to DSView. Even after installing the firmware files and giving access to the device, PulseView / Sigrok will still have only a fraction of the DSView features and settings. To run PulseView instead of DSview, it will need to install the DSlogic firmware files and to create a udev access rule. ![]() The easiest way would be to make a virtual machine with Windows 7 and install DSView in the virtual machine. DSView has way more acquisition modes, triggers and features than PulseView has, also DSView works properly, while PulseView sometimes returns fake signals or works erratically. I don't recommend to use PulseView, try to use DSView instead. VID:PID of the device is 2a0e:0003, with no device description. When it is recognized, it appears as DSLogic Pro, so nothing to upgrade. Turned out my DSlogic already has 256Mbit SDRAM, and it is not a clone, it was made by DreamSourceLab in 2015. Because DSLogicPlus.bin changed, not work good with U2B version, you can copy older to latest 'res' folder. Change DSView from latest 1.0.1 to 0.9.9, work ok. I use other plus firmware from this post, DSView shows Plus, also not work. Modify pid/vid, DSView shows Plus, but push start, only wait, not work. Yes, 64Mb -> 256Mb Using U2B origin eeprom firmware, use buffer mode, test new SDRAM(256Mb) is ok. Upgrading DSLogic Basic to Plus without EEPROM modification ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |