Post Go back to editing

Unexpected behavior from channel-A and channel-B

Category: Software
Product Number: ADALM1000
Software Version: Built: 2020/09/15 Version: 1.0.5-g943a506, Serial Number: 203220505444AD39203830323730303, Firmware Version: 2.17

Hello sir,

I'm experiencing unexpected behavior with my ADALM1000 kit

Background: During a test, I generated 1Hz square wave for the counter IC using python programing and generated 1Hz clock signal however, after this , the kit seems to be generating a square wave on both the Channel-A and B. Even when I select different signals in Pixel pulse/Alice, the output doesn't change. It seems the reference signal has been permanently configured as a square wave. 

I also have calibration issue, voltage in Pixlepulse/Alice  is showing 1000v 

Kindly guide how to fix this issue. 



x
[edited by: AnandaMaity at 4:48 AM (GMT -4) on 2 Apr 2025]
  • Assuming the device does not come back to proper operation after power cycling it, and given the 1000V readings I would guess that the calibration / firmware has been corrupted. Assuming you have libsmu installed (a must to have ALICE work) go the command line and type:

    >smu


    smu: utility for managing M1K devices

    -h, --help print this help message and exit
    --version show libsmu version
    -l, --list-devices list supported devices currently attached to the system
    -p, --hotplug-devices simple session device hotplug testing
    -s, --stream-samples stream samples to stdout from a single attached device
    -d, --display-calibration display calibration data from all attached devices
    -r, --reset-calibration reset calibration data to the defaults on all attached devices
    -w, --write-calibration <cal file> write calibration data to a single attached device
    -f, --flash <firmware image> flash firmware image to a single attached device

    The smu command line utility will show the above list of options.

    the -r option will reset the calibration data to the factory defaults on all attached devices. Give that a try. If that does nor help then it may require the firmware to be re-flashed. firmware image file available  here:

    github.com/.../m1000-2.17.bin

    If that does not return the board to proper operation then there is not much that can be done short of replacing the board.