Looks like I got an idea what's going wrong here. The sigrok software writes another USB control request as CTRL SAMPLING. The struct sample_config_t has a uint32_t member "u2" that should not be 32 bit aligned in the USB message. This __packed__ attribute is not honored in the MXE compiler. Fill bytes are inserted.
Should I send the details here in the list or should I open an issue in the tracker? Best regards, Helge -----Original Message----- From: Florian Schmidt [mailto:schmidt_flor...@gmx.de] Sent: Tuesday, October 27, 2020 7:30 PM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016 (just my guess on reported run_state's) my assumption is that run_state 0x85e_2_ is meaning "waiting for trigger condition". from your other log output i see that there is no edge/level-trigger requested, device should just start sampling 200M samples no matter what signals are applied... and my device immediately signals this by reporting a run_state of 0x85e_e_ "triggered". next run_state 0x85e_d_ is signaled as soon as acquisition buffer of 200M samples is full, which will trigger download. your device does successfully transition from 0x85e_9_ to 0x85e_2_. i am curious what your log looks like if you request fewer samples (e.g. via --samples 256). (also make sure to leave the programm running long enough (~20s ?) such that enough log messages are generated.) flo. _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
