Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
DIOT Zynq Ultrascale-based System Board
DIOT Zynq Ultrascale-based System Board
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 24
    • Issues 24
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Projects
  • DIOT Zynq Ultrascale-based System BoardDIOT Zynq Ultrascale-based System Board
  • Wiki
  • Software

Software

Last edited by Adam Wujek Oct 25, 2021
Page history
This is an old version of this page. You can view the most recent version or browse the history.

Software for DI/OT Zynq Ultrascale-based System Board

U-boot

Booting form network

By default DI/OT board will try to obtain from the DHCP server the IP address of the tftp server and the filename of an image. U-boot will try to retrieve the pointed image via TFTP. After the successful transfer the u-boot will try to run the retreived image as a script. If it fails, it will run as regular image.

Create script to be used by network booting

Create text file with valid uboot commands to be executed. E.g.:

echo "echo hello!" > boot_script.txt

Make a uboot image out of that file:

mkimage -A arm -O linux -C none -T script -n 'boot script' -d boot_script.txt boot_script.img

Linux

Sensors for diagnostics

I2C address Chip Channel Measurement Nominal V / Max I Description
0x48 LM75 (IC36) 1 Temp - Temp DDR
0x49 LM75 (IC36) 1 Temp - Temp FMC
0x4A LM75 (IC36) 1 Temp - Temp Power Management
0x2C MAX6639 (IC28) 1 Temp - Temp FPGA
0x2C MAX6639 (IC28) 2 Temp - Not used
0x2C MAX6639 (IC28) 1 Fan - Not used
0x2C MAX6639 (IC28) 2 Fan - Not used
0x14 IRPS5401 (IC30) IN V/I/P 12V IRPS1 Input <Voltage / Current / Power>
0x14 IRPS5401 (IC30) 1 V/I/P/T 0.85V, 20A IRPS1 P0V85 <Voltage / Current / Power / Temp>
0x14 IRPS5401 (IC30) 2 V/I/P/T 1.8V, 2A IRPS1 P1V8_AUX <Voltage / Current / Power / Temp>
0x14 IRPS5401 (IC30) 3 V/I/P/T 1.2V, 4A IRPS1 P1V2 <Voltage / Current / Power / Temp>
0x14 IRPS5401 (IC30) 4 V/I/P/T 1.8V, 4A IRPS1 P1V8 <Voltage / Current / Power / Temp>
0x14 IRPS5401 (IC30) 5 V/I/P/T 1.2V, 0.5A IRPS1 P1V2_PSPLL LDO <Voltage / Current / Power / Temp>
0x15 IRPS5401 (IC30) IN V/I/P 12V IRPS2 Input <Voltage / Current / Power>
0x15 IRPS5401 (IC30) 1 V/I/P/T 3.3V, 20A IRPS2 P3V3 <Voltage / Current / Power / Temp>
0x15 IRPS5401 (IC30) 2 V/I/P/T 1.8V, 2A IRPS2 MGT_1V8 <Voltage / Current / Power / Temp>
0x15 IRPS5401 (IC30) 3 V/I/P/T 0.9V, 4A IRPS2 MGT_0V9 <Voltage / Current / Power / Temp>
0x15 IRPS5401 (IC30) 4 V/I/P/T 1.2V, 4A IRPS2 MGT_1V2 <Voltage / Current / Power / Temp>
0x15 IRPS5401 (IC30) 5 V/I/P/T - (not used, do not report)
Clone repository
  • Backplane gth ibert analysis
  • Board specification
  • Software
  • Files
  • Home
  • Prototypes evaluation
  • PTS
    • Simple pts files
  • Software
    • Build system
    • Linux
    • Pts
    • Booting
    • Sensors for diagnostics
More Pages

New Wiki Page

Tip: You can specify the full path for the new file. We will automatically create any missing directories.