Keysight U3810 Series Getting Started Guide
94
loading /boot/initrd.img-4.14.49-ti-r54 ...
4034122 bytes read in 271 ms (14.2 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet] ...
debug: [bootz 0x82000000 0x88080000:3d8e4a 88000000] ...
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fc27000, end 8ffffe4a ... OK
reserving fdt memory region: addr=88000000 size=70000
Loading Device Tree to 8fbb4000, end 8fc26fff ... OK
Starting kernel ...
[ 0.000814] timer_probe: no matching timers found
[ 0.546264] dmi: Firmware registration failed.
[ 1.035757] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc
handle
[ 1.334985] omap_voltage_late_init: Voltage driver support not added
Debian GNU/Linux 9 beaglebone ttyS0
BeagleBoard.org Debian Image 2018-06-17
U3810A Version 2.50
Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
default username:password is [debian:temppwd]
beaglebone login:
Debugging I
2
C Devices
1
i
2cdetect -r -y 1
Debugging SPI and ADC
1
Measure and verify VSENSOR and +5SYS supplies.
Debugging GPIO
1
mraa-gpio list
2
look in
/sys/class/gpio
3
Mention 1 second turnaround for status change.
Debugging PWM
1
/sys/class/pwm. See if there is pwmchip0 and pwmchip2.
2
$ echo ‘0’ > /sys/class/pwm/pwmchip0
should result in seeing the
/sys/class/pwm/pwm-0:0 directory
.
3
In that directory echoing various values will affect PWM output on GP5.
Summary of Contents for U3810A
Page 1: ...Keysight U3810A Advanced IoT Teaching Solution Getting Started Guide ...
Page 78: ...Keysight U3810 Series Getting Started Guide 78 IMU Characteristics from the LSM9DS1 datasheet ...
Page 131: ...Keysight U3810 Series Getting Started Guide 131 ...
Page 132: ...Keysight U3810 Series Getting Started Guide 132 Disassembly ...