Author Topic: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown  (Read 4835 times)

0 Members and 3 Guests are viewing this topic.

Offline EEVblog

  • Administrator
  • *****
  • Posts: 24761
  • Country: au
    • EEVblog
The new Siglent SDS1104X-E $499 4CH oscilloscope is a new contender for Rigol's DS1054Z dominance. What's it like inside?



Boot log:

Code: [Select]
Config AXI VDMA...
Start menu vdma done.


U-Boot 2014.07-svn6402 (Jul 06 2017 - 00:17:05)

Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 243 MiB
NAND:  256 MiB
MMC:   zynq_sdhci: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
lcd_init++++++++++++
lcd_init----------
Net:   Gem.e000b000
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1:   ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
       scanning usb for storage devices... 0 Storage Device(s) found
Copying Linux from USB to RAM...
** Bad device usb 0 **
Download Linux from USB to Nandflash...
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Copying Linux from NAND flash to RAM...

NAND read: device 0 offset 0x780000, size 0x400000
 4194304 bytes read: OK

NAND read: device 0 offset 0xb80000, size 0x80000
 524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-3.19.0-xilinx-svn7597
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3396064 Bytes = 3.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
   Loading Kernel Image ... OK
   Loading Device Tree to 0e00e000, end 0e014dab ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.19.0-xilinx-svn7597 ([email protected]) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #189 SMP PREEMPT Fri Jul 28 23:53:53 CST 2017
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Zynq Zed Development Board
[    0.000000] cma: Reserved 16 MiB at 0x0d000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] PERCPU: Embedded 9 pages/cpu @4f0ea000 s8128 r8192 d20544 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 61722
[    0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=07
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 223532K/248832K available (4202K kernel code, 228K rwdata, 1688K rodata, 196K init, 222K bss, 8916K reserved, 16384K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0x4f800000 - 0xff000000   (2808 MB)
[    0.000000]     lowmem  : 0x40000000 - 0x4f300000   ( 243 MB)
[    0.000000]     pkmap   : 0x3fe00000 - 0x40000000   (   2 MB)
[    0.000000]     modules : 0x3f000000 - 0x3fe00000   (  14 MB)
[    0.000000]       .text : 0x40008000 - 0x405c8aa4   (5891 kB)
[    0.000000]       .init : 0x405c9000 - 0x405fa000   ( 196 kB)
[    0.000000]       .data : 0x405fa000 - 0x40633320   ( 229 kB)
[    0.000000]        .bss : 0x40633320 - 0x4066ae38   ( 223 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[    0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[    0.000000] slcr mapped to 4f804000
[    0.000000] zynq_clock_init: clkc starts at 4f804100
[    0.000000] Zynq clock init
[    0.000010] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000135] timer #0 at 4f806000, irq=17
[    0.000497] Console: colour dummy device 80x30
[    0.000517] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090276] pid_max: default: 32768 minimum: 301
[    0.090434] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090448] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091105] CPU: Testing write buffer coherency: ok
[    0.091324] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.091408] Setting up static identity map for 0x3f5c78 - 0x3f5cd0
[    0.240265] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.240344] Brought up 2 CPUs
[    0.240364] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[    0.240374] CPU: All CPU(s) started in SVC mode.
[    0.240900] devtmpfs: initialized
[    0.241731] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.247849] NET: Registered protocol family 16
[    0.249975] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.281225] cpuidle: using governor ladder
[    0.311194] cpuidle: using governor menu
[    0.319515] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.319533] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.319676] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4f880000
[    0.337205] vgaarb: loaded
[    0.337668] SCSI subsystem initialized
[    0.338098] usbcore: registered new interface driver usbfs
[    0.338193] usbcore: registered new interface driver hub
[    0.338303] usbcore: registered new device driver usb
[    0.338472] phy0 supply vcc not found, using dummy regulator
[    0.338565] phy1 supply vcc not found, using dummy regulator
[    0.338677] --------------usb_udc_init ------
[    0.338910] pps_core: LinuxPPS API ver. 1 registered
[    0.338923] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[    0.338972] PTP clock support registered
[    0.339128] EDAC MC: Ver: 3.0.0
[    0.340898] Switched to clocksource arm_global_timer
[    0.353329] NET: Registered protocol family 2
[    0.354180] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.354231] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.354288] TCP: Hash tables configured (established 2048 bind 2048)
[    0.354341] TCP: reno registered
[    0.354357] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.354393] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.354616] NET: Registered protocol family 1
[    0.354959] RPC: Registered named UNIX socket transport module.
[    0.354972] RPC: Registered udp transport module.
[    0.354981] RPC: Registered tcp transport module.
[    0.354989] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.355436] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.356878] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.358650] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.359757] io scheduler noop registered
[    0.359778] io scheduler deadline registered
[    0.359832] io scheduler cfq registered (default)
[    0.362954] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.362977] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.363496] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 6249999) is a xuartps
[    0.934931] console [ttyPS0] enabled
[    0.939115] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4f878000
[    0.945883] [drm] Initialized drm 1.1.0 20060810
[    0.958598] brd: module loaded
[    0.965735] loop: module loaded
[    0.977230] libphy: MACB_mii_bus: probed
[    1.060828] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 150 (00:0a:35:00:01:22)
[    1.070665] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.082216] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.088668] ehci-pci: EHCI PCI platform driver
[    1.093264] usbcore: registered new interface driver usbtmc
[    1.098848] usbcore: registered new interface driver usb-storage
[    1.105018] e0002000.usb supply vbus not found, using dummy regulator
[    1.111708] ci_hdrc ci_hdrc.0: EHCI Host Controller
[    1.116527] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[    1.140719] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[    1.146865] hub 1-0:1.0: USB hub found
[    1.150571] hub 1-0:1.0: 1 port detected
[    1.155039] e0003000.usb supply vbus not found, using dummy regulator
[    1.163200] i2c /dev entries driver
[    1.167480] cdns-i2c e0005000.i2c: 20 kHz mmio e0005000 irq 144
[    1.174727] zynq-edac f8006000.memory-controller: ecc not enabled
[    1.180999] Xilinx Zynq CpuIdle Driver started
[    1.186028] ledtrig-cpu: registered to indicate activity on CPUs
[    1.192139] usbcore: registered new interface driver r8188eu
[    1.198559] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.204923] nand: Micron MT29F2G08ABAEAWP
[    1.208845] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.216419] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.227913] Bad block table found at page 131008, version 0x01
[    1.234169] Bad block table found at page 130944, version 0x01
[    1.240280] 11 ofpart partitions found on MTD device pl353-nand
[    1.246138] Creating 11 MTD partitions on "pl353-nand":
[    1.251349] 0x000000000000-0x000000780000 : "fsbl"
[    1.257256] 0x000000780000-0x000000b80000 : "kerneldata"
[    1.263571] 0x000000b80000-0x000000c00000 : "device-tree"
[    1.269861] 0x000000c00000-0x000001100000 : "Manufacturedata"
[    1.276530] 0x000001100000-0x000001600000 : "reserved1"
[    1.282695] 0x000001600000-0x000003e00000 : "rootfs"
[    1.288637] 0x000003e00000-0x000004800000 : "firmdata0"
[    1.294842] 0x000004800000-0x000007000000 : "siglent"
[    1.300922] 0x000007000000-0x00000d400000 : "datafs"
[    1.306963] 0x00000d400000-0x00000fc00000 : "upgrade_cramdisk"
[    1.313864] 0x00000fc00000-0x000010000000 : "reserved2"
[    1.322033] TCP: cubic registered
[    1.325278] NET: Registered protocol family 17
[    1.329718] lib80211: common routines for IEEE802.11 drivers
[    1.335810] Registering SWP/SWPB emulation handler
[    1.347543] cramfs_fill_nand blocks is 320-----------------------
[    1.347543]
[    1.347543]
[    1.347543]
[    1.360982] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[    1.367837] devtmpfs: mounted
[    1.371093] Freeing unused kernel memory: 196K (405c9000 - 405fa000)
[    1.470798] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    1.622124] hub 1-1:1.0: USB hub found
[    1.625912] hub 1-1:1.0: 3 ports detected
Starting rcS...
 Mounting filesystem
[    1.788494] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[    2.187088] UBI-0: scan_all:scanning is finished
[    2.199416] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[    2.206869] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.215425] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.223928] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.232619] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[    2.240319] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.249276] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 4/1, WL threshold: 4096, image sequence number: 1174617309
[    2.260124] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[    2.271077] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 649
[    2.275415] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[    2.435476] UBI-1: scan_all:scanning is finished
[    2.447203] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 40 MiB)
[    2.454654] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.463214] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.471716] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.480381] UBI-1: ubi_attach_mtd_dev:good PEBs: 320, bad PEBs: 0, corrupted PEBs: 0
[    2.488133] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.497064] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 4/2, WL threshold: 4096, image sequence number: 166915174
[    2.507826] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 320, PEBs reserved for bad PEB handling: 40
[    2.518777] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 653
[    2.523152] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[    2.565113] UBI-2: scan_all:scanning is finished
[    2.575838] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    2.586923] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[    2.594527] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.603105] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.611609] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.620277] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.627927] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.636869] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 1044444380
[    2.647737] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.658499] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 657
[    2.736804] UBIFS: mounted UBI device 1, volume 0, name "siglent", R/O mode
[    2.743715] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.752821] UBIFS: FS size: 33775616 bytes (32 MiB, 266 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.762449] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.767478] UBIFS: media format: w4/r0 (latest is w4/r0), UUID CB8C2D55-7B90-4921-B20B-3818373CC8E2, small LPT model
[    2.843157] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.849865] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.859010] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.868365] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.873404] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C19D5CB3-831B-4B44-950C-7A0C94BC5EF7, small LPT model
[    2.887103] UBIFS: background thread "ubifs_bgt0_0" started, PID 662
[    2.918483] UBIFS: recovery needed
[    2.993217] UBIFS: recovery completed
[    2.996884] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.002916] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.011987] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.021608] UBIFS: reserved for root: 0 bytes (0 KiB)
[    3.026636] UBIFS: media format: w4/r0 (latest is w4/r0), UUID E0FF57F6-4C55-4611-B74D-F2754AB10FAF, small LPT model
Upgrade start
 Configure eth0
Starting mdev
[    4.007790] xilinx-dma 40400000.dma: Probing xilinx axi dma engine...Successful
[    4.033627] xilinx-vdma 43010000.dma: Xilinx AXI VDMA Engine Driver Probed!!
[    4.048954] sigdma_init++++++
[    4.072010] siglentkb probe
[    4.074814] ##### siglentkb registers 4fc1e580 4fc365a4 4fc385b8
config read
###### Config vdma for wave transform #######
config write
config read
dump s2mm registers
dump mm2s registers
####### done! ########
Segmentation fault
[    4.290210] UBIFS: background thread "ubifs_bgt1_0" started, PID 741
ln: /usr/bin/siglent/config/www/web_img/usr: File exists
Starting Lighttpd Web Server: [    4.405947] random: lighttpd urandom read with 17 bits of entropy available
lighttpd.
[    4.543757] UBIFS: background thread "ubifs_bgt1_0" stops
rcS Complete

Processing /etc/profile... Done

/ # [1B][34m[INFO]:[1B][0mcalibrate_t():line=81:calibrate_t::calibrate_t()
lib_product_t::set_product_type 4CH
4CH key XXXXXXXXXXXXXXXxxx
[    5.445350] UBIFS: background thread "ubifs_bgt1_0" started, PID 761
mkdir: can't create directory '/usr/bin/siglent/wifi/': File exists
rm: can't remove '/usr/bin/siglent/wifi/wpa_supplicant': No such file or directory
[    5.483311] UBIFS: background thread "ubifs_bgt1_0" stops
clear done



                                                       $Task start:: SCPI
 
                                                       $Task start:: Devce
 msp430_power_off

vxi11_main = 6679.07

                                                       $Task start:: Udisk&Lan
 XXX  other_main 0: 10 :d1 :0 :0 :32  010d10032
sh: write error: Invalid argument
drv_instance_manage_t: produce_id: 13501
(DRV_PRODUCT_PIKACHU)
_drv_product=4
power_off_cycle

                                                       $Task start:: Vxi11_client
 Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
ready...
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
ready...
Config module error:_get_fs_wave_data
ready...
Config module error:_get_fs_wave_data
ready...
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
bu_cfg module er[    7.413072] export_store: invalid GPIO 115
ror:mode-type:/usr/bin/siglent/firmdata0/options_mso_license.txt
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
Config module error:_get_fs_wave_data
sh: write error: Invalid argument
sh: can't create /sys/class/gpio/gpio115/direction: nonexistent directory
sh: can't create /sys/class/gpio/gpio115/value: nonexistent directory
ready...
drv_if_scrnsvr_t::set_switch++
[1B][34m[INFO]:[1B][0mset_current_iq_wave():line=146:open file /usr/bin/siglent/config/arb/2ASK.wav fail !!!!
lib_unit_deal_t::do_convert::amplify_index = 8
lib_unit_deal_t::do_convert::size = 6
acq_thread module error:lib_unit_deal_t::do_convert unit error.

                                                       $Task start:: UI
[    9.345073] UBIFS: background thread "ubifs_bgt1_0" started, PID 845
rm: can't remove '/usr/bin/siglent/wifi/wpa_supplicant': No such file or directory
[    9.372663] UBIFS: background thread "ubifs_bgt1_0" stops
ifconfig: SIOCGIFFLAGS: No such device
[    9.436328] UBIFS: background thread "ubifs_bgt1_0" started, PID 862
rm: can't remove '/usr/bin/siglent/wifi/wpa_supplicant': No such file or directory
[    9.478112] UBIFS: background thread "ubifs_bgt1_0" stops
ifconfig: SIOCGIFFLAGS: No such device
 lib_unit_deal_t::do_convert::amplify_index = 8
lib_unit_deal_t::do_convert::size = 6
acq_thread module error:lib_unit_deal_t::do_convert unit error.
lib_unit_deal_t::do_convert::amplify_index = 8
lib_unit_deal_t::do_convert::size = 6
acq_thread module error:lib_unit_deal_t::do_convert unit error.

                                                       $Task start:: awg_thread
 BUG:pui_cursors_parameter_t::get_cursors_manual_source() no curr manual source!
bu_cfg_digital_t::set_setup
adc_skew start
calc_phase_diff skew = 30160
calc_phase_diff skew = 30140
calc_phase_diff skew = 30100
adc_skew end

                                                       $Task start:: awg_interrupt_thread
[   13.530200] UBIFS: background thread "ubifs_bgt1_0" started, PID 884
rm: can't remove '/usr/bin/siglent/wifi/wpa_supplicant': No such file or directory
[   13.548290] UBIFS: background thread "ubifs_bgt1_0" stops
ifconfig: SIOCGIFFLAGS: No such device
 usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0xee38 iManufacturer=Siglent iProduct=SDS1104X-E iSerialNum=SDSMMDBD1R0050
insmod: can't read '/usr/bin/siglent/drivers/udc-xilinx.ko': No such file or directory
[   23.729376] ######################### usb_gadget_probe_driver 3f03346c ##################
[   23.737581] usbtmc_bind+++
[   23.742697] SIGLENT_DEV: SIGLENT_DEV, version: 2007 OCT 06
[   23.749321] usbtmc_open()++
[   23.752078] dev->usbtmc_cdev_open ret = 0
[   23.756040] ret = 0
[   23.758112] usbtmc_open--
[   23.761087] show_send_buffer_size = 61440

                                                       $Task start:: USBTMC


SHUTDOWN:
 save_trig_setup_as_xml
save_zoom_setup_as_xml
save_utility_setup_as_xml
save_auto_setup_as_xml
save_decode_setup_as_xml
save_search_setup_as_xml
save_digital_setup_as_xml
save_curr_menu_id_as_xml
[  213.010901] UBIFS: un-mount UBI device 2, volume 0
power_off+++[00]

Start menu vdma ...
« Last Edit: November 26, 2017, 04:44:43 PM by EEVblog »
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 13000
  • Country: nl
    • NCT Developments
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #1 on: November 26, 2017, 08:32:25 AM »
I have seen that power supply before. Don't know if that heatsink on top of that chip/MOSFet is doing anything because the die will be on the tab soldered to the PCB anyway.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline dr.diesel

  • Super Contributor
  • ***
  • Posts: 2005
  • Country: us
  • Cramming the magic smoke back in...
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #2 on: November 26, 2017, 08:34:11 AM »
that heatsink

Makes me wonder just how hot it's running.

Offline iromero

  • Supporter
  • ****
  • Posts: 26
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #3 on: November 26, 2017, 08:47:51 AM »
That $69 wifi dongle looks suspiciously like the ones Microcenter sells for $5, I wonder if they would work?....
 

Online tox3

  • Contributor
  • Posts: 5
  • Country: lv
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #4 on: November 26, 2017, 09:00:41 AM »
Looks like a great feature set for the price. But will have to wait for the review to see what the user experience gonna be like.  :-//
 

Offline ArdWar

  • Newbie
  • Posts: 3
  • Country: id
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #5 on: November 26, 2017, 09:02:01 AM »
That $69 wifi dongle looks suspiciously like the ones Microcenter sells for $5, I wonder if they would work?....

Would be shitty design if it's an user-accessible USB port (with USB logo no less) but won't accept standard-compliant USB stuff.
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 9981
  • Country: nz
    • Taupaki Technologies Ltd.
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #6 on: November 26, 2017, 09:08:02 AM »
That $69 wifi dongle looks suspiciously like the ones Microcenter sells for $5, I wonder if they would work?....
It's not.

In our option listings the WiFi dongle is listed as TL-WN725N.
http://www.tp-link.com/us/products/details/cat-5520_TL-WN725N.html#overview

I've been told the gold version is the one to get, why I haven't sussed out yet.  :-//

Would be shitty design if it's an user-accessible USB port (with USB logo no less) but won't accept standard-compliant USB stuff.
Yep, we need to fiddle a bit with the WiFi dongle and see what else will work.

BUT you need buy the WIFI software option for it to work anyway unless a hack for it is found.
« Last Edit: November 26, 2017, 09:12:43 AM by tautech »
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Offline G0MJW

  • Contributor
  • Posts: 25
  • Country: gb
  • Mike
    • G0MJW
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #7 on: November 26, 2017, 09:08:23 AM »
It's quite remarkable what you can get for $499 and even more remarkable that you can get something quite similar for $350 from Rigol. I remember scopes being expensive and not something you would have at home. Nowadays its what you buy after a multi-meter and bench PSU and just before the spectrum analyser and signal generator. What's with the 4 channels? I usually find 2 enough.

I look forward to the proper testing video. One thing I expect I may like is the better choice of trace colours than we get on the DS1054.

Mike
Mike
 

Offline T3sl4co1l

  • Super Contributor
  • ***
  • Posts: 9332
  • Country: us
  • Expert, Analog Electronics, PCB Layout, EMC
    • Seven Transistor Labs
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #8 on: November 26, 2017, 09:20:37 AM »
That multiple trace NORM mode is weird.  (For both KS and Siglent. I dare say both are buggy -- multiple exposures don't make any sense in that mode, period.)

Appears it "ARM"s itself every 15 seconds, and that refreshes the screen.  Bizarre.

Tim
Seven Transistor Labs, LLC
Electronic Design, from Concept to Layout.
Need engineering assistance? Drop me a message!
 

Online mtdoc

  • Super Contributor
  • ***
  • Posts: 2811
  • Country: us
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #9 on: November 26, 2017, 10:28:20 AM »
That multiple trace NORM mode is weird.  (For both KS and Siglent. I dare say both are buggy -- multiple exposures don't make any sense in that mode, period.)

I agree. Single trigger event should equal single sweep.  Waveform update rate should be irrelevant, shouldn't it?
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 9981
  • Country: nz
    • Taupaki Technologies Ltd.
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #10 on: November 26, 2017, 10:42:19 AM »
That multiple trace NORM mode is weird.  (For both KS and Siglent. I dare say both are buggy -- multiple exposures don't make any sense in that mode, period.)

I agree. Single trigger event should equal single sweep.  Waveform update rate should be irrelevant, shouldn't it?
See this explanation for better understanding:
http://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1359013/#msg1359013
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Online mtdoc

  • Super Contributor
  • ***
  • Posts: 2811
  • Country: us
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #11 on: November 26, 2017, 10:56:39 AM »
That multiple trace NORM mode is weird.  (For both KS and Siglent. I dare say both are buggy -- multiple exposures don't make any sense in that mode, period.)

I agree. Single trigger event should equal single sweep.  Waveform update rate should be irrelevant, shouldn't it?
See this explanation for better understanding:
http://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1359013/#msg1359013

That still doesn't explain why a single trigger event should produce more than one acquisition. Or is Dave's tap creating more than one trigger event? Would the same thing occur if in single shot mode?
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 9981
  • Country: nz
    • Taupaki Technologies Ltd.
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #12 on: November 26, 2017, 11:50:57 AM »
That multiple trace NORM mode is weird.  (For both KS and Siglent. I dare say both are buggy -- multiple exposures don't make any sense in that mode, period.)

I agree. Single trigger event should equal single sweep.  Waveform update rate should be irrelevant, shouldn't it?
See this explanation for better understanding:
http://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1359013/#msg1359013

That still doesn't explain why a single trigger event should produce more than one acquisition. Or is Dave's tap creating more than one trigger event? Would the same thing occur if in single shot mode?
Let's see:



Probably Dave's one is all back together now but the Siglent's aren't usually that sensitive to impacts to the BNC inputs. I haven't had the beta unit I have here apart so I'm wondering if Siglent have used their usual through-chassis design for the inputs with nuts on the BNC's or they've departed to something else.  :-//
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 13000
  • Country: nl
    • NCT Developments
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #13 on: November 26, 2017, 11:57:59 AM »
I have the same question: are the input BNCs bolted to the chassis or not? IMHO it is important to have the input BNC connectors bolted to the chassis due to the amount of abuse/mechanical stress they endure.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 9981
  • Country: nz
    • Taupaki Technologies Ltd.
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #14 on: November 26, 2017, 12:02:29 PM »
I have the same question: are the BNCs bolted to the chassis or not? IMHO it is important to have BNC connectors bolted to the chassis due to the amount of abuse/mechanical stress they endure.
They certainly are for SDS1202X-E but the mainboard layout for the 4 ch versions is vertical and we'd have to remove it to see for sure.....but I'll have a look through the front panel cut outs with a magnifying glass......back with an edit soon. Undetermined. Teardown required to be sure.
« Last Edit: November 26, 2017, 12:08:29 PM by tautech »
Avid Rabid Hobbyist & NZ Siglent Distributor
 

Online nidlaX

  • Frequent Contributor
  • **
  • Posts: 550
  • Country: us
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #15 on: November 26, 2017, 02:04:40 PM »
Dave: Are we going to see individual reviews of the new bottom tier 4 channel scopes, or will you go straight to a shootout with the latest models? I would argue that a shootout would be more informative than any individual reviews, so might as well save the effort and get straight to it.
 

Offline maxwell3e10

  • Regular Contributor
  • *
  • Posts: 100
  • Country: us
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #16 on: November 26, 2017, 03:14:33 PM »
I saw that Owon is coming out with a 4-channel version of XDS scopes with 14 bit resolution, XDS3064AE and XDS3104AE. Dave, I wonder if you can get a hold of one of them for a review. If its not too buggy, it would be a great contender to replace generic low frequency scopes.
 

Offline EEVblog

  • Administrator
  • *****
  • Posts: 24761
  • Country: au
    • EEVblog
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #17 on: November 26, 2017, 04:21:32 PM »
Dave: Are we going to see individual reviews of the new bottom tier 4 channel scopes, or will you go straight to a shootout with the latest models? I would argue that a shootout would be more informative than any individual reviews, so might as well save the effort and get straight to it.

I think that's likely.
Shootouts are big jobs, but separate videos and shootout is even more work.
 

Offline Factotum

  • Newbie
  • Posts: 1
  • Country: au
Re: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #18 on: November 26, 2017, 05:47:15 PM »
Sounds great  :-+ Can't wait (and I need a new 4 channel 'scope too)...
 

Offline rf-loop

  • Super Contributor
  • ***
  • Posts: 2485
  • Country: fi
  • Starting with DLL21
Re: EEVblog #1044 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #19 on: November 26, 2017, 08:52:42 PM »
That multiple trace NORM mode is weird.  (For both KS and Siglent. I dare say both are buggy -- multiple exposures don't make any sense in that mode, period.)

I agree. Single trigger event should equal single sweep.  Waveform update rate should be irrelevant, shouldn't it?
See this explanation for better understanding:
http://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1359013/#msg1359013

That still doesn't explain why a single trigger event should produce more than one acquisition. Or is Dave's tap creating more than one trigger event? Would the same thing occur if in single shot mode?

Yes, of course.
How you think this what Dave did is "single trigger event". 
Just open History view after it have stopped and display these multiple waveforms and there can see  separate captured waveforms what are triggered. Also trigger hysteresis is not very big and trigger level was set near zero. Due to small random short peak/noise induced to open input BNC may generate "ghost" trigger. Now if this multiple waveform stay on the screen and then if there exist any next single trigger event it looks like display is cleaned. If there is no other triggers inside this one display refresh cycle what happen perhaps around every 40ms roughly. But what we see in video, time position 18:57 it is mysterious when it suddenly clean display and leave last one visible after long time (many seconds) when Dave is just only talking. SDS1202X-E do not this itself.

If there exist around 40ms burst what have many trigger events it may draw up to over 3000 wfm (depending other settings what affect wfm/s speed) to one display frame overlayed.
If there is timer what cleans all but last acquisition - I can ask, why. As long as user understand how to use oscilloscope after he have this display. Or if he do not want, he can easy set scope so that this do not happen.
If he do not want at all this, he can turn ti Single mode. But then he have visible only first trigger event independent of if there is after then other trigger events.
If he want stay in Normal mode, there is also other setting what can use. There is acquisition mode selection: Slow and Fast. Slow do not capture multiple trigger events to one display frame.

If there is bug in this case, then there is but what I see in Daves video is not bug but wondering it and claiming it is bug without any more thinking and analyzing, bug (lack of experience and knowledge) is in user side.


« Last Edit: November 26, 2017, 10:34:57 PM by rf-loop »
If practice and theory is not equal it tells that used application of theory  is wrong or the theory itself is wrong.
It is much easier to think an apple fall to the ground than to think that the earth and the apple will begin to move toward each other and collide.
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 13000
  • Country: nl
    • NCT Developments
Re: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #20 on: November 26, 2017, 11:12:55 PM »
As if Dave never used or seen any other oscilloscope  :palm: FFS he is even taking the trouble of pulling out 3 other scopes and show their behaviour in the same situation!
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline madires

  • Super Contributor
  • ***
  • Posts: 3661
  • Country: de
  • A qualified hobbyist ;)
Re: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #21 on: November 27, 2017, 12:08:05 AM »
I like the idea to put the MSO option into an external box connected via USB. If Siglent is clever they would provide a PC software to use the MSO box also directly by the PC. Same for the signal generator box.
FidoNet 2:240/1661
 

Online nctnico

  • Super Contributor
  • ***
  • Posts: 13000
  • Country: nl
    • NCT Developments
Re: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #22 on: November 27, 2017, 12:13:27 AM »
I like the idea to put the MSO option into an external box connected via USB. If Siglent is clever they would provide a PC software to use the MSO box also directly by the PC. Same for the signal generator box.
Well that does complicate combining things like triggering. Lecroy already went this route for one of their earlier MSO offerings and it didn't work out very well.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline rf-loop

  • Super Contributor
  • ***
  • Posts: 2485
  • Country: fi
  • Starting with DLL21
Re: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #23 on: November 27, 2017, 12:22:16 AM »
I like the idea to put the MSO option into an external box connected via USB. If Siglent is clever they would provide a PC software to use the MSO box also directly by the PC. Same for the signal generator box.

Time correlation between analog channels and LA via USB is perhaps "small" problem.  How many nanosecond variation you accept between analog channels and digital channels.  MSO need  tight time correlation without random exeptions between analog and digital channels. How this USB can syncronize with analog channels ADC clock.

I think Sbus (near USB connector) is there with reasons?
If practice and theory is not equal it tells that used application of theory  is wrong or the theory itself is wrong.
It is much easier to think an apple fall to the ground than to think that the earth and the apple will begin to move toward each other and collide.
 

Offline ChrisLX200

  • Supporter
  • ****
  • Posts: 242
  • Country: gb
Re: EEVblog #1042 - Siglent's $499 SDS1104X-E 4CH Oscilloscope Teardown
« Reply #24 on: November 27, 2017, 12:22:34 AM »
I was wondering... what is the difference between hacking a piece of hardware like this and hacking software? It seems both have legal issues yet one seems to be more 'acceptable' than the other. Consider that the Rigol hack is distributed so everyone is able to upgrade their scope, meaning we're not talking about something just done for your own use. What's the convention here, or is it unmentionable?
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf