Author Topic: The Siglent SDG2042X Thread  (Read 564469 times)

0 Members and 7 Guests are viewing this topic.

Online Bad_Driver

  • Frequent Contributor
  • **
  • Posts: 364
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1525 on: August 27, 2022, 09:44:56 am »
Some UI house keeping would be nice. I’m now a owner of 5 (edit: 6!!) Siglent devices and there is not much in common in their user interfaces. And as shown in another thread every device software looks different on the PC and behaves different as well.
Come on Siglent, that can be done much better!

If someone can provide this last RB3 firmware I‘ll be very grateful  :clap: !
« Last Edit: August 31, 2022, 10:16:01 am by Bad_Driver »
 

Offline Johnny B Good

  • Frequent Contributor
  • **
  • Posts: 811
  • Country: gb
Re: The Siglent SDG2042X Thread
« Reply #1526 on: August 27, 2022, 11:43:44 am »
Some UI house keeping would be nice. I’m now a owner of 5 Siglent devices and there is not much in common in their user interfaces. And as shown in another thread every device software looks different on the PC and behaves different as well.
Come on Siglent, that can be done much better!

If someone can provide this last RB3 firmware I‘ll be very grateful  :clap: !

 Here's my copy, downloaded October last year.

Just remove the .txt off the end of the file name.

 Drat! I forgot about the 4000KB limit. >:(

 Try this link instead:

https://www.siglenteu.com/download/8700/
John
 

Offline Blue

  • Regular Contributor
  • *
  • Posts: 120
  • Country: nl
  • Fighting for peace is like fucking for virginity
Re: The Siglent SDG2042X Thread
« Reply #1527 on: August 27, 2022, 01:52:38 pm »
For those who want the B3 firmware get it now. Ik think the wetransfer link expires in 7 days.
If that happens, email me directly.

https://we.tl/t-Y5yZ7vQgFO

Nick
 
The following users thanked this post: Johnny B Good, Bad_Driver, nike75

Offline Blue

  • Regular Contributor
  • *
  • Posts: 120
  • Country: nl
  • Fighting for peace is like fucking for virginity
Re: The Siglent SDG2042X Thread
« Reply #1528 on: August 27, 2022, 01:56:29 pm »
I got that B3 firmware after emails with Tautech. He contacted Siglent after my bug report and they fixed it with this B3 firmware.
 

Online ebastler

  • Super Contributor
  • ***
  • Posts: 6491
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1529 on: August 27, 2022, 03:50:58 pm »
Try this link instead:
https://www.siglenteu.com/download/8700/

That's the B2 firmware, right? Your PDF history file also describes up to revision B2 only.  B3 had not been officially released by Siglent, I believe.

I got that B3 firmware after emails with Tautech. He contacted Siglent after my bug report and they fixed it with this B3 firmware.

I am lost in the long thread. Could you please remind me which bug B3 fixes? Thanks!
 

Offline Blue

  • Regular Contributor
  • *
  • Posts: 120
  • Country: nl
  • Fighting for peace is like fucking for virginity
Re: The Siglent SDG2042X Thread
« Reply #1530 on: August 27, 2022, 03:59:32 pm »
Look at fig 1 in the bug report pdf: Labview error using Siglents own example. That error has been solved with the B3 firmware.
Additional error still exist in the Siglents own example and has been solved by changing something in the labview schematic - see fig 2.
 
The following users thanked this post: ebastler, Bad_Driver

Offline Johnny B Good

  • Frequent Contributor
  • **
  • Posts: 811
  • Country: gb
Re: The Siglent SDG2042X Thread
« Reply #1531 on: August 27, 2022, 10:39:23 pm »
Try this link instead:
https://www.siglenteu.com/download/8700/

That's the B2 firmware, right? Your PDF history file also describes up to revision B2 only.  B3 had not been officially released by Siglent, I believe.


 Sorry! My bad. :-[ I'm afraid I got the 3B mixed up with the B2 part of the version number.:palm:
« Last Edit: September 12, 2022, 12:09:43 am by Johnny B Good »
John
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 28379
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: The Siglent SDG2042X Thread
« Reply #1532 on: September 18, 2022, 12:36:58 am »
FYI
Ad Hoc Curve tracer project using SDS2000X Plus in XY mode and both channels from the SDG2042X AWG.
https://www.eevblog.com/forum/testgear/fooln-around-with-dso-awg/
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 
The following users thanked this post: Johnny B Good, nike75

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1533 on: September 30, 2022, 09:15:02 am »
I measured the phase noise of the SDG2042X with the internal and an external reference. The plot with the external reference  (2. picture) looks like the plot with the internal reference at high frequencies, like the external OCXO below 2Hz and has strange spurs at multiples of 2.5Hz.

As the internal reference is 2.5Hz off the external reference, this looks like mixing products from the internal and external reference. Has my SDG2042X a problem, or is the insufficient offnes of the internal reference a "feature"?

 

Offline Blue

  • Regular Contributor
  • *
  • Posts: 120
  • Country: nl
  • Fighting for peace is like fucking for virginity
Re: The Siglent SDG2042X Thread
« Reply #1534 on: September 30, 2022, 10:23:00 am »
Dear bnz,

Can you elaborate on how you measured the phase noise.

Thanks
 

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1535 on: September 30, 2022, 10:37:27 am »
Dear bnz,

Can you elaborate on how you measured the phase noise.

Thanks

With Andrew Holmes direct digital phase noise measurement setup, see
http://www.aholme.co.uk/PhaseNoise/Main.htm

 
The following users thanked this post: Mortymore

Offline hpw

  • Frequent Contributor
  • **
  • Posts: 365
  • Country: 00
Re: The Siglent SDG2042X Thread
« Reply #1536 on: September 30, 2022, 11:29:20 am »
Interesting,

how long does a single PN measurement in min/hours required.

While did some minutes ago some Jitter measurements using a LeCroy SDA.
 

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1537 on: September 30, 2022, 12:18:17 pm »
Interesting,

how long does a single PN measurement in min/hours required.

While did some minutes ago some Jitter measurements using a LeCroy SDA.

It depends  ;)
1.) on the FFT size, which is responsible for the resolution.
2.) on how low frequencies in the PN graph you need.
3.) how good your reference oscillators are compared to the DUT (i.e. how much averaging/crosscorrelation is needed to get your curve above the noice floor).

The above graphs were made  with FFT size 4k and took about half an hour measurent time to get sub Hz readings.
« Last Edit: September 30, 2022, 12:21:04 pm by bnz »
 

Offline hpw

  • Frequent Contributor
  • **
  • Posts: 365
  • Country: 00
Re: The Siglent SDG2042X Thread
« Reply #1538 on: September 30, 2022, 01:44:42 pm »
Interesting,

how long does a single PN measurement in min/hours required.

While did some minutes ago some Jitter measurements using a LeCroy SDA.

It depends  ;)
1.) on the FFT size, which is responsible for the resolution.
2.) on how low frequencies in the PN graph you need.
3.) how good your reference oscillators are compared to the DUT (i.e. how much averaging/crosscorrelation is needed to get your curve above the noice floor).

The above graphs were made  with FFT size 4k and took about half an hour measurent time to get sub Hz readings.

Anyway, the figures are IMHO too low...

Please tell, used feq. on SDG as sine or square and levels (asymmetric symmetric). Also used OXCO brand & figures sine or square/levels.

Measure also the Square output of the siglent as this should have Jitter (plenty off) and also the used OXCO against the PN OXCO.

In addition, you do not know how the siglent uses the OXCO signal: Direct or by PLL. May also use the FM / sine modulation with a freq. of 500Hz or 1kHz and with 1Hz deviation.
 

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1539 on: September 30, 2022, 02:13:56 pm »
Interesting,

how long does a single PN measurement in min/hours required.

While did some minutes ago some Jitter measurements using a LeCroy SDA.

It depends  ;)
1.) on the FFT size, which is responsible for the resolution.
2.) on how low frequencies in the PN graph you need.
3.) how good your reference oscillators are compared to the DUT (i.e. how much averaging/crosscorrelation is needed to get your curve above the noice floor).

The above graphs were made  with FFT size 4k and took about half an hour measurent time to get sub Hz readings.

Anyway, the figures are IMHO too low...

Please tell, used feq. on SDG as sine or square and levels (asymmetric symmetric). Also used OXCO brand & figures sine or square/levels.

Measure also the Square output of the siglent as this should have Jitter (plenty off) and also the used OXCO against the PN OXCO.

In addition, you do not know how the siglent uses the OXCO signal: Direct or by PLL. May also use the FM / sine modulation with a freq. of 500Hz or 1kHz and with 1Hz deviation.

The Holme-phase-noise system seems to be accurate. See the cross checks with professional equipment on his web site. Also I was able to reproduce the specs of some of my OCXOs. Moreover If I turn PM-modulaion on I get a spike of expected magnitude in the plot.

The Siglent was set on 10MHz Sine 4Vpp (HiZ). I also did a test with 11.1MHz, it looked alike (for the external-reference measurement). The OCXOs were C-MAC CFPO-2, measurement below.

No I have no idea how Siglent uses the OXCO signal, but heavy oscillation with multiples of OCXO to internal ref frequency difference does look wrong.

P.S. the dark blue trace is the measurement of the DUT. The light blue the estimated noise floor.
« Last Edit: September 30, 2022, 02:18:40 pm by bnz »
 

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1540 on: October 01, 2022, 08:22:05 am »
I measured the reference in/output of the SDG2042X with a scope in the external-reference setting. There are indeed remains of the internal clock:  10MHz spikes of about 10mVpp (in 50 Ohm).

So is my SDG2042X defect or is that a feature, i.e. can somebody reproduce this measurement?
 

Offline luciof

  • Contributor
  • Posts: 24
  • Country: it
Re: The Siglent SDG2042X Thread
« Reply #1541 on: October 01, 2022, 10:43:22 am »
Connected the SDG2042X's 10 MHz In/Out BNC to the scope via a 50 ohm pass-thru terminator.
The first shot is in Internal Clock mode, and the second picture is in External Clock mode (like in your test); in this case it is an input, so I think it's quite normal to see some noise from the generator's circuitry.

« Last Edit: October 01, 2022, 10:45:48 am by luciof »
 

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1542 on: October 01, 2022, 11:46:32 am »
Thanks for testing it  :)

Well it may be "normal", but it prevents to make use of the better phase noise performance of the external clock, to some extend. It's annoying as it is unnecessary that the internal clock is powered up at all, the latest as soon the external is connected.
 

Offline hpw

  • Frequent Contributor
  • **
  • Posts: 365
  • Country: 00
Re: The Siglent SDG2042X Thread
« Reply #1543 on: October 01, 2022, 12:08:33 pm »
Well,

using some 20Gs scope... as 50E input

A) signal as internal looks equal, not nice square wave

B) signal as externsl looks like a 1GHz sine at 10mV

So turtles stuff at HF limited..

Cheers

hp
 

Offline bnz

  • Contributor
  • Posts: 43
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1544 on: October 01, 2022, 02:10:07 pm »
OK, I fired up the big scope ... for my SDG it looks alike my picture with its little brother.
« Last Edit: October 01, 2022, 02:12:28 pm by bnz »
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 28379
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: The Siglent SDG2042X Thread
« Reply #1545 on: December 10, 2022, 06:13:15 am »
New firmware for SDG2000X models, as reported by NoisyBoy in this thread:
https://www.eevblog.com/forum/testgear/siglent-sdg2000x-firmware-hardware-software-versions/

Version: V2.01.01.37R3
39MB
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG2000X_V2.01.01.37R3_EN.zip

Release notes
Compatible with Rev.F hardware; if the hardware version is “05-xx-xx-xx-xx”, it will not support to roll back previous firmware version
Supported trig dual channel separated when use manual trigger.
Supported using another channel as the modulation source
Supported setting the output frequency after the completion of sweep
Counter add fast measurement mode
Changed the square waveform data used in square FM modulation
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 
The following users thanked this post: luciof

Offline SimpleXP

  • Newbie
  • Posts: 2
  • Country: de
Re: The Siglent SDG2042X Thread
« Reply #1546 on: December 10, 2022, 08:38:14 pm »
Hi everybody,

I got a problem similar to the one here: https://www.eevblog.com/forum/repair/help-fixing-siglent-sdg805/, but with an SDG2042X. At some day, it just stopped booting up further the logo screen.

I already saved the boot log ouput via UART but I don't really know what the error at the end is telling me exactly...

Code: [Select]
U-Boot SPL 2013.01.01-svn72327 (Nov 06 2019 - 11:19:35)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=522292, height=272, width=480
Logo from nandflash: base=0x81000000; end=0x8107f81f; end-base=0x7f81f; rwsize=0x7f820; r=0x0
Lcd_Init()--


U-Boot 2013.01.01-svn72327 (Nov 06 2019 - 11:19:35)

I2C:   ready
DRAM:  128 MiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

set_default_env::8123
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
(Re)start USB...
USB0:   lowlevel init failed
USB error: all controllers failed lowlevel init
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 **
Booting from nand ...

NAND read: device 0 offset 0x3080000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-3.2.0-svn223263
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2812168 Bytes = 2.7 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 3.2.0-svn223263 (david@david-virtual-machine) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #42 Wed Nov 6 11:19:32 CST 2019
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: am335xevm
[    0.000000] Ignoring tag cmdline (using the default kernel command line)
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] AM335X ES1.0 (neon )
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=ubi0:rootfs ro ubi.mtd=7,2048 rootfstype=ubifs rootwait=1t ip=none
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 123756k/123756k available, 7316k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0529364   (5253 kB)
[    0.000000]       .init : 0xc052a000 - 0xc056c000   ( 264 kB)
[    0.000000]       .data : 0xc056c000 - 0xc05bd350   ( 325 kB)
[    0.000000]        .bss : 0xc05bd374 - 0xc060103c   ( 272 kB)
[    0.000000] NR_IRQS:396
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] Total of 128 interrupts on 1 active controller
[    0.000000] OMAP clockevent source: GPTIMER2 at 25000000 Hz
[    0.000000] omap_dm_timer_switch_src: Switching to HW default clocksource(sys_clkin_ck) for timer1, this may impact timekeeping in low power state
[    0.000000] OMAP clocksource: GPTIMER1 at 25000000 Hz
[    0.000000] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798ms
[    0.000000] Console: colour dummy device 80x30
[    0.000212] Calibrating delay loop... 718.02 BogoMIPS (lpj=3590144)
[    0.057101] pid_max: default: 32768 minimum: 301
[    0.057280] Mount-cache hash table entries: 512
[    0.057669] CPU: Testing write buffer coherency: ok
[    0.057746] ftrace: allocating 14556 entries in 43 pages
[    0.109567] omap_hwmod: gfx: failed to hardreset
[    0.125622] omap_hwmod: pruss: failed to hardreset
[    0.126786] print_constraints: dummy:
[    0.127072] NET: Registered protocol family 16
[    0.129315] OMAP GPIO hardware version 0.1
[    0.131577] am335x_evm_init()++
[    0.131803] omap_mux_init: Add partition: #1: core, flags: 0
[    0.134029] am335x_evm_i2c_init()++
[    0.134267]  omap_i2c.1: alias fck already exists
[    0.134471] am335x_evm_i2c_init()--
[    0.134599] da8xx_panel_power_ctrl()++
[    0.134638] back light switch = 1
[    0.134660] da8xx_panel_power_ctrl()--
[    0.134975] am335x_evm_init()--
[    0.135278]  omap2_mcspi.1: alias fck already exists
[    0.135496]  omap2_mcspi.2: alias fck already exists
[    0.135765]  edma.0: alias fck already exists
[    0.135787]  edma.0: alias fck already exists
[    0.135806]  edma.0: alias fck already exists
[    0.152705] bio: create slab <bio-0> at 0
[    0.154858] SCSI subsystem initialized
[    0.156661] usbcore: registered new interface driver usbfs
[    0.156986] usbcore: registered new interface driver hub
[    0.157240] usbcore: registered new device driver usb
[    0.157858] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
[    0.159660] tps65910 1-002d: JTAGREVNUM 0x0
[    0.162048] print_constraints: VRTC:
[    0.163492] print_constraints: VIO: at 1500 mV
[    0.165793] print_constraints: VDD1: 600 <--> 1500 mV at 1262 mV normal
[    0.168094] print_constraints: VDD2: 600 <--> 1500 mV at 1137 mV normal
[    0.169117] print_constraints: VDD3: 5000 mV
[    0.170517] print_constraints: VDIG1: at 1800 mV
[    0.171932] print_constraints: VDIG2: at 1800 mV
[    0.173346] print_constraints: VPLL: at 1800 mV
[    0.174760] print_constraints: VDAC: at 1800 mV
[    0.176191] print_constraints: VAUX1: at 1800 mV
[    0.177598] print_constraints: VAUX2: at 3300 mV
[    0.179024] print_constraints: VAUX33: at 3300 mV
[    0.180441] print_constraints: VMMC: at 3300 mV
[    0.180937] tps65910 1-002d: No interrupt support, no core IRQ
[    0.182569] cfg80211: Calling CRDA to update world regulatory domain
[    0.183214] Switching to clocksource gp timer
[    0.204195] NET: Registered protocol family 2
[    0.204406] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.204705] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.204795] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.204851] TCP: Hash tables configured (established 4096 bind 4096)
[    0.204864] TCP reno registered
[    0.204877] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.204901] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.205077] NET: Registered protocol family 1
[    0.205362] RPC: Registered named UNIX socket transport module.
[    0.205376] RPC: Registered udp transport module.
[    0.205386] RPC: Registered tcp transport module.
[    0.205396] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.206136] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
[    0.213469] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.213809] msgmni has been set to 241
[    0.214473] io scheduler noop registered
[    0.214488] io scheduler deadline registered
[    0.214570] io scheduler cfq registered (default)
[    0.215716] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
[    0.767017] console [ttyO0] enabled
[    0.771158] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
[    0.778949] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
[    0.786706] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
[    0.794442] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[    0.802129] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
[    0.819361] brd: module loaded
[    0.827648] loop: module loaded
[    0.831012] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.893256] No daughter card found
[    0.896847] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.904115] am335x_evm_setup()++
[    0.963256] AM335X: EVM Config read fail: -110
[    0.967884] No board detected, using GPBoard 1.1A as default
[    0.973931] The board is general purpose EVM in profile 0
[    0.979555] Found invalid GP EVM revision, falling back to Rev1.1A
[    0.986008] -------siglent_fpga_init++
[    0.990013] -------siglent_fpga_init--
[    0.994721]  da8xx_lcdc.0: alias fck already exists
[    1.000246] evm_nand_init()++
[    1.003981] omap-gpmc omap-gpmc: GPMC revision 6.0
[    1.008984] Registering NAND on CS0
[    1.013219] evm_nand_init()--
[    1.017759] haptics_init()++
[    1.021729] haptics_init()--
[    1.024777] out_triger_gpio_init()++
[    1.028540] out_triger_gpio_init()--
[    1.032735] am335x_evm_setup()--
[    1.037646] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.044787] omap2-nand driver initializing
[    1.049377] ONFI flash detected
[    1.052781] ONFI param page 0 valid
[    1.056454] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP)
[    1.065146] Creating 12 MTD partitions on "omap2-nand.0":
[    1.070789] 0x000000000000-0x000000020000 : "SPL"
[    1.077156] 0x000000020000-0x000000040000 : "SPL.backup1"
[    1.084097] 0x000000040000-0x000000060000 : "SPL.backup2"
[    1.091000] 0x000000060000-0x000000080000 : "SPL.backup3"
[    1.097951] 0x000000080000-0x000000260000 : "U-Boot"
[    1.105182] 0x000000260000-0x000000280000 : "U-Boot Env"
[    1.111985] 0x000000280000-0x000000580000 : "Manufacturedata"
[    1.120528] 0x000000580000-0x000003080000 : "rootfs"
[    1.144868] 0x000003080000-0x000003680000 : "kerneldata"
[    1.154113] 0x000003680000-0x000006880000 : "firmdata0"
[    1.181550] 0x000006880000-0x000009a80000 : "firmdata1"
[    1.208981] 0x000009a80000-0x000010000000 : "datafs"
[    1.257708] OneNAND driver initializing
[    1.262405] UBI: attaching mtd7 to ubi0
[    1.266461] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    1.272992] UBI: logical eraseblock size:    126976 bytes
[    1.278626] UBI: smallest flash I/O unit:    2048
[    1.283535] UBI: sub-page size:              512
[    1.288344] UBI: VID header offset:          2048 (aligned 2048)
[    1.294610] UBI: data offset:                4096
[    1.709969] UBI: max. sequence number:       577
[    1.728487] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 12
[    1.740175] UBI: attached mtd7 to ubi0
[    1.744120] UBI: MTD device name:            "rootfs"
[    1.749382] UBI: MTD device size:            43 MiB
[    1.754473] UBI: number of good PEBs:        344
[    1.759281] UBI: number of bad PEBs:         0
[    1.763917] UBI: number of corrupted PEBs:   0
[    1.768544] UBI: max. allowed volumes:       128
[    1.773360] UBI: wear-leveling threshold:    4096
[    1.778258] UBI: number of internal volumes: 1
[    1.782884] UBI: number of user volumes:     1
[    1.787519] UBI: available PEBs:             0
[    1.792146] UBI: total number of reserved PEBs: 344
[    1.797235] UBI: number of PEBs reserved for bad PEB handling: 9
[    1.803501] UBI: max/mean erase counter: 7/2
[    1.807947] UBI: image sequence number:  1632968070
[    1.813096] UBI: background thread "ubi_bgt0d" started, PID 485
[    1.863298] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
[    1.869748] davinci_mdio davinci_mdio.0: detected phy mask bfffffff
[    1.876541] bus->id = 0, addr= 30
[    1.880188] 11--
[    1.882314] davinci_mdio.0: probed
[    1.885899] davinci_mdio davinci_mdio.0: phy[30]: device 0:1e, driver unknown
[    1.893714] usbcore: registered new interface driver rt2800usb
[    1.899795] Initializing USB Mass Storage driver...
[    1.905092] usbcore: registered new interface driver usb-storage
[    1.911352] USB Mass Storage support registered.
[    1.916635] mousedev: PS/2 mouse device common for all mice
[    1.922444] i2c /dev entries driver
[    1.927234] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.934268] TCP cubic registered
[    1.937636] NET: Registered protocol family 17
[    1.942400] NET: Registered protocol family 33
[    1.947082] lib80211: common routines for IEEE802.11 drivers
[    1.953025] Registering the dns_resolver key type
[    1.958005] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    1.966010] ThumbEE CPU extension supported.
[    1.970519] mux: Failed to setup hwmod io irq -22
[    1.976038] Power Management for AM33XX family
[    1.980727] clock: disabling unused clocks to save power
[    1.987955] Detected MACID=68:9e:19:5c:3a:88
[    2.067101] UBIFS: recovery needed
[    2.270801] UBIFS: recovery deferred
[    2.274562] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.280819] UBIFS: mounted read-only
[    2.284555] UBIFS: file system size:   40632320 bytes (39680 KiB, 38 MiB, 320 LEBs)
[    2.292537] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
[    2.300163] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    2.306248] UBIFS: default compressor: lzo
[    2.310514] UBIFS: reserved for root:  0 bytes (0 KiB)
[    2.318288] VFS: Mounted root (ubifs filesystem) readonly on device 0:12.
[    2.325784] Freeing init memory: 264K

init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)

starting pid 520, tty '': '/etc/init.d/rcS'
rS in
/etc/init.d/rcS: line 14: setterm: not found
Current direction is :"/usr/bin/siglent"

starting pid 534, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/ # [1B][34m[INFO]:[1B][0mcalibrate_t():line=81:calibrate_t::calibrate_t()
check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
[    5.069235] UBI: attaching mtd11 to ubi1
[    5.073406] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    5.079936] UBI: logical eraseblock size:    126976 bytes
[    5.085571] UBI: smallest flash I/O unit:    2048
[    5.090470] UBI: sub-page size:              512
[    5.095289] UBI: VID header offset:          2048 (aligned 2048)
[    5.101545] UBI: data offset:                4096
[    6.074508] UBI: max. sequence number:       31102
[    6.103391] UBI: attached mtd11 to ubi1
[    6.107407] UBI: MTD device name:            "datafs"
[    6.112669] UBI: MTD device size:            101 MiB
[    6.117858] UBI: number of good PEBs:        812
[    6.122666] UBI: number of bad PEBs:         0
[    6.127303] UBI: number of corrupted PEBs:   0
[    6.131930] UBI: max. allowed volumes:       128
[    6.136747] UBI: wear-leveling threshold:    4096
[    6.141645] UBI: number of internal volumes: 1
[    6.146281] UBI: number of user volumes:     1
[    6.150907] UBI: available PEBs:             0
[    6.155544] UBI: total number of reserved PEBs: 812
[    6.160623] UBI: number of PEBs reserved for bad PEB handling: 32
[    6.166980] UBI: max/mean erase counter: 58/38
[    6.171608] UBI: image sequence number:  79843063
[    6.176537] UBI: background thread "ubi_bgt1d" started, PID 554
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
[    6.289626] UBIFS: recovery needed
[    6.445662] UBIFS: recovery completed
[    6.449504] UBIFS: mounted UBI device 1, volume 0, name "rootfs"
[    6.455785] UBIFS: file system size:   97136640 bytes (94860 KiB, 92 MiB, 765 LEBs)
[    6.463778] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
[    6.471395] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    6.477480] UBIFS: default compressor: lzo
[    6.481746] UBIFS: reserved for root:  0 bytes (0 KiB)
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
[    6.551622] UBI: attaching mtd9 to ubi2
[    6.555718] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    6.562249] UBI: logical eraseblock size:    126976 bytes
[    6.567885] UBI: smallest flash I/O unit:    2048
[    6.572784] UBI: sub-page size:              512
[    6.577603] UBI: VID header offset:          2048 (aligned 2048)
[    6.583869] UBI: data offset:                4096
[    7.065982] UBI: max. sequence number:       34
[    7.093376] UBI: attached mtd9 to ubi2
[    7.097301] UBI: MTD device name:            "firmdata0"
[    7.102834] UBI: MTD device size:            50 MiB
[    7.107936] UBI: number of good PEBs:        400
[    7.112743] UBI: number of bad PEBs:         0
[    7.117392] UBI: number of corrupted PEBs:   0
[    7.122019] UBI: max. allowed volumes:       128
[    7.126837] UBI: wear-leveling threshold:    4096
[    7.131735] UBI: number of internal volumes: 1
[    7.136371] UBI: number of user volumes:     1
[    7.140997] UBI: available PEBs:             0
[    7.145633] UBI: total number of reserved PEBs: 400
[    7.150713] UBI: number of PEBs reserved for bad PEB handling: 16
[    7.157069] UBI: max/mean erase counter: 2/1
[    7.161515] UBI: image sequence number:  1976655378
[    7.166626] UBI: background thread "ubi_bgt2d" started, PID 579
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
[    7.359768] UBIFS: mounted UBI device 2, volume 0, name "firmdata0"
[    7.366338] UBIFS: mounted read-only
[    7.370065] UBIFS: file system size:   46854144 bytes (45756 KiB, 44 MiB, 369 LEBs)
[    7.378059] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
[    7.385687] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    7.391763] UBIFS: default compressor: lzo
[    7.396038] UBIFS: reserved for root:  0 bytes (0 KiB)
--mount_check_copy_appdata: ending

                                                       $Task start:: SCPI
 example_thread++
[    7.683648]
[    7.683659] CPSW phy found : id is : 0x20005c90
[    7.690666] PHY 0:01 not found
[    7.762294] gpib_usb_init
 $Task start:: Devce
 vxi11_main = 7890.12
$Task start:: Udisk&Lan
 drv_instance_manage_t: produce_id: 10600
(DRV_PRODUCT_SDG2000)
_drv_product=0
[    8.963270] sched: RT throttling activated
[    9.023988] usbcore: registered new interface driver usb-gpib
init_spi:: name = /dev/spidev1.0
init_spi:: handle = 17
_init_load_fpga_file_to_fpga()::str_path = /usr/bin/siglent/config/fpga/fpga.bin
[1B][34m[INFO]:[1B][0mload_cali_data():line=1544:sdg2000 load from usr cali data OK
Config module error:lib_xml_t::set_content = iq:max_amp:
Config module error:lib_xml_t::set_content = iq:min_amp:
Config module error:lib_xml_t::set_content = iq:max_sample_rate:
Config module error:lib_xml_t::set_content = iq:min_symbol_rate:
Config module error:lib_xml_t::set_content = iq:max_center_frq:
Config module error:lib_xml_t::set_content = iq:min_center_frq:
Config module error:lib_xml_t::set_content = iq:max_gain_balance:
Config module error:lib_xml_t::set_content = iq:min_gain_balance:
Config module error:lib_xml_t::set_content = iq:max_Q_Angle:
Config module error:lib_xml_t::set_content = iq:min_Q_Angle:
Config module error:lib_xml_t::set_content = iq:max_offset:
Config module error:lib_xml_t::set_content = iq:min_offset:
I/O error : Read-only file system
I/O error : Read-only file system
Config module error:lib_xml_t::set_content = device:Support_IQ_Flag:
I/O error : Read-only file system
I/O error : Read-only file system
mod_if_exit_handler:signal=11
Clean Up Ready!
Clean Up - Example
Clean Up - SCPI
Clean Up - dev_thread
Clean Up - dev_interpreter_main
Clean Up - USBTMC
Clean Up - ui_task
Clean Up - touch_task
Clean Up - key
Clean Up - Config
Clean Up - Config assistant
Clean Up - Config_assistant_voltage_overload
Clean Up - VXI_11
Clean Up - telnet_scpi
Clean Up - socket
Clean Up - GPIB
Clean Up - Timer
Clean Up Over!


I measured all hardware voltages, they are all as expected and the FPGA and Linux Heartbeat LEDs are blinking like they should.

I tried starting the sdg2000.app manually per nonsole but this ends in the same error, some configuration seems to be bricked.

I would like to try reflashing the firmware but I don't know how to do this via UART.

I would be really happy if I can restore this unit!
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 28379
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: The Siglent SDG2042X Thread
« Reply #1547 on: December 10, 2022, 08:44:39 pm »
Hi everybody,

I got a problem similar to the one here: https://www.eevblog.com/forum/repair/help-fixing-siglent-sdg805/, but with an SDG2042X. At some day, it just stopped booting up further the logo screen.


I would be really happy if I can restore this unit!
Welcome to the forum.

We have recovery files to fix these.
Send us a PM with your email and we'll get this sorted for you.

In the meanwhile find a USB stick of 8GB max formatted in FAT32 with 4k clusters.

..........
And he got it fixed. :)
« Last Edit: December 10, 2022, 11:06:34 pm by tautech »
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 

Online markone

  • Frequent Contributor
  • **
  • Posts: 698
  • Country: it
Re: The Siglent SDG2042X Thread
« Reply #1548 on: December 10, 2022, 10:56:53 pm »
New firmware for SDG2000X models, as reported by NoisyBoy in this thread:
https://www.eevblog.com/forum/testgear/siglent-sdg2000x-firmware-hardware-software-versions/

Version: V2.01.01.37R3
39MB
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG2000X_V2.01.01.37R3_EN.zip

Release notes
Compatible with Rev.F hardware; if the hardware version is “05-xx-xx-xx-xx”, it will not support to roll back previous firmware version

My SDG2042x shows HW version "02-07-00-40-00", where should be the letter 'F' ?

I guess it's not compatible.
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 28379
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: The Siglent SDG2042X Thread
« Reply #1549 on: December 10, 2022, 11:00:46 pm »
New firmware for SDG2000X models, as reported by NoisyBoy in this thread:
https://www.eevblog.com/forum/testgear/siglent-sdg2000x-firmware-hardware-software-versions/

Version: V2.01.01.37R3
39MB
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG2000X_V2.01.01.37R3_EN.zip

Release notes
Compatible with Rev.F hardware; if the hardware version is “05-xx-xx-xx-xx”, it will not support to roll back previous firmware version

My SDG2042x shows HW version "02-07-00-40-00", where should be the letter 'F' ?

I guess it's not compatible.
I'm guessing it's in the SN# coding.
Should have more idea after a reply from Tech support and after getting more stock of these in a week or so.
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf