Skip to content

Commit ff9963c

Browse files
deploy: a5e6c73 #210 (synchronize)
1 parent 250b77d commit ff9963c

File tree

3 files changed

+29
-141
lines changed

3 files changed

+29
-141
lines changed

pull/210/_sources/hardware-configuration.rst.txt

Lines changed: 15 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -456,8 +456,8 @@ FAT32 partition:
456456
2. `<target>/socfpga_arria10_socdk_sdmmc.dtb` - Device tree
457457
3. `<target>/u-boot.img` - U-Boot proper
458458
4. `socfpga_arria10_common/zImage` - Kernel image
459-
5. Create an `extlinux` folder and copy
460-
`socfpga_arria10_common/extlinux.conf` into it
459+
5. Create an `extlinux` folder and copy `socfpga_arria10_common/extlinux.conf`
460+
into it
461461

462462
Then write the preloader:
463463

@@ -497,10 +497,19 @@ partition. To identify it:
497497
# Find your SD card device
498498
lsblk
499499
500-
# Look for a device like /dev/mmcblkX with multiple partitions
501-
# The third partition (mmcblkXp3) is typically the 4MB bootloader partition
500+
Example output on PC:
502501

503-
Example output:
502+
.. code-block:: text
503+
504+
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
505+
sdb 8:16 1 29.7G 0 disk
506+
├─sdb1 8:17 1 256M 0 part /media/user/BOOT
507+
├─sdb2 8:18 1 29.2G 0 part /media/user/rootfs
508+
└─sdb3 8:19 1 4M 0 part
509+
510+
In this case, `/dev/sdb3` is the 4MB bootloader partition.
511+
512+
Example output on target board:
504513

505514
.. code-block:: text
506515
@@ -510,74 +519,7 @@ Example output:
510519
├─mmcblk0p2 179:2 0 29.2G 0 part
511520
└─mmcblk0p3 179:3 0 4M 0 part
512521
513-
In this case, `/dev/mmcblk0p3` is the bootloader partition.
514-
515-
File Location Reference
516-
~~~~~~~~~~~~~~~~~~~~~~~
517-
518-
When manually configuring, you'll find the required files in your `/boot`
519-
directory organized like this:
520-
521-
.. code-block:: text
522-
523-
/boot/
524-
├── zynq-common/ # Shared Zynq files
525-
│ ├── uImage
526-
│ └── uEnv.txt
527-
├── zynqmp-common/ # Shared ZynqMP files
528-
│ ├── Image
529-
│ └── uEnv.txt
530-
├── versal-common/ # Shared Versal files
531-
│ └── Image
532-
├── socfpga_arria10_common/ # Shared Arria10 files
533-
│ ├── zImage
534-
│ └── extlinux.conf
535-
├── <project_name>/ # Project-specific files
536-
│ ├── BOOT.BIN
537-
│ ├── devicetree.dtb or system.dtb
538-
│ └── other project files
539-
└── *.json # Configuration metadata
540-
541-
Verification and Testing
542-
~~~~~~~~~~~~~~~~~~~~~~~~
543-
544-
After manual configuration, verify your setup:
545-
546-
**1. Check Boot Messages**
547-
548-
Connect to the serial console (115200 baud) and watch for successful boot
549-
messages. You should see:
550-
551-
- U-Boot loading and executing
552-
- Kernel starting
553-
- Root filesystem mounting
554-
- Kuiper Linux login prompt
555-
556-
**2. Verify Hardware Detection**
557-
558-
Once booted, check if your hardware is properly detected:
559-
560-
.. code-block:: bash
561-
562-
# List IIO devices (if your project includes IIO devices)
563-
iio_info
564-
565-
# Check kernel boot messages
566-
dmesg | grep -i "your_device_name"
567-
568-
# Verify device tree loading
569-
ls /sys/firmware/devicetree/base/
570-
571-
**3. Network and System Check**
572-
573-
.. code-block:: bash
574-
575-
# Verify system information
576-
cat /etc/os-release
577-
uname -a
578-
579-
# Check network (if configured)
580-
ip addr show
522+
In this case, `/dev/mmcblk0p3` is the 4MB bootloader partition.
581523

582524
----
583525

pull/210/hardware-configuration.html

Lines changed: 13 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -110,8 +110,6 @@
110110
<li><a class="reference internal" href="#finding-the-correct-partition-for-preloader">Finding the Correct Partition for Preloader</a></li>
111111
</ul>
112112
</li>
113-
<li><a class="reference internal" href="#file-location-reference">File Location Reference</a></li>
114-
<li><a class="reference internal" href="#verification-and-testing">Verification and Testing</a></li>
115113
</ul>
116114
</li>
117115
<li><a class="reference internal" href="#next-steps">Next Steps</a></li>
@@ -562,8 +560,8 @@ <h4>Intel/Altera Platforms<a class="headerlink" href="#intel-altera-platforms" t
562560
<li><p><cite>&lt;target&gt;/socfpga_arria10_socdk_sdmmc.dtb</cite> - Device tree</p></li>
563561
<li><p><cite>&lt;target&gt;/u-boot.img</cite> - U-Boot proper</p></li>
564562
<li><p><cite>socfpga_arria10_common/zImage</cite> - Kernel image</p></li>
565-
<li><p>Create an <cite>extlinux</cite> folder and copy
566-
<cite>socfpga_arria10_common/extlinux.conf</cite> into it</p></li>
563+
<li><p>Create an <cite>extlinux</cite> folder and copy <cite>socfpga_arria10_common/extlinux.conf</cite>
564+
into it</p></li>
567565
</ol>
568566
<p>Then write the preloader:</p>
569567
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Write preloader to the bootloader partition (replace mmcblkXp3 with your actual device)</span>
@@ -595,79 +593,27 @@ <h4>Finding the Correct Partition for Preloader<a class="headerlink" href="#find
595593
partition. To identify it:</p>
596594
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Find your SD card device</span>
597595
lsblk
598-
599-
<span class="c1"># Look for a device like /dev/mmcblkX with multiple partitions</span>
600-
<span class="c1"># The third partition (mmcblkXp3) is typically the 4MB bootloader partition</span>
601596
</pre></div>
602597
</div>
603-
<p>Example output:</p>
598+
<p>Example output on PC:</p>
599+
<div class="highlight-text notranslate"><div class="highlight"><pre><span></span>NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
600+
sdb 8:16 1 29.7G 0 disk
601+
├─sdb1 8:17 1 256M 0 part /media/user/BOOT
602+
├─sdb2 8:18 1 29.2G 0 part /media/user/rootfs
603+
└─sdb3 8:19 1 4M 0 part
604+
</pre></div>
605+
</div>
606+
<p>In this case, <cite>/dev/sdb3</cite> is the 4MB bootloader partition.</p>
607+
<p>Example output on target board:</p>
604608
<div class="highlight-text notranslate"><div class="highlight"><pre><span></span>NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
605609
mmcblk0 179:0 0 29.7G 0 disk
606610
├─mmcblk0p1 179:1 0 256M 0 part /mnt/BOOT
607611
├─mmcblk0p2 179:2 0 29.2G 0 part
608612
└─mmcblk0p3 179:3 0 4M 0 part
609613
</pre></div>
610614
</div>
611-
<p>In this case, <cite>/dev/mmcblk0p3</cite> is the bootloader partition.</p>
612-
</section>
615+
<p>In this case, <cite>/dev/mmcblk0p3</cite> is the 4MB bootloader partition.</p>
613616
</section>
614-
<section id="file-location-reference">
615-
<h3>File Location Reference<a class="headerlink" href="#file-location-reference" title="Link to this heading"></a></h3>
616-
<p>When manually configuring, you’ll find the required files in your <cite>/boot</cite>
617-
directory organized like this:</p>
618-
<div class="highlight-text notranslate"><div class="highlight"><pre><span></span>/boot/
619-
├── zynq-common/ # Shared Zynq files
620-
│ ├── uImage
621-
│ └── uEnv.txt
622-
├── zynqmp-common/ # Shared ZynqMP files
623-
│ ├── Image
624-
│ └── uEnv.txt
625-
├── versal-common/ # Shared Versal files
626-
│ └── Image
627-
├── socfpga_arria10_common/ # Shared Arria10 files
628-
│ ├── zImage
629-
│ └── extlinux.conf
630-
├── &lt;project_name&gt;/ # Project-specific files
631-
│ ├── BOOT.BIN
632-
│ ├── devicetree.dtb or system.dtb
633-
│ └── other project files
634-
└── *.json # Configuration metadata
635-
</pre></div>
636-
</div>
637-
</section>
638-
<section id="verification-and-testing">
639-
<h3>Verification and Testing<a class="headerlink" href="#verification-and-testing" title="Link to this heading"></a></h3>
640-
<p>After manual configuration, verify your setup:</p>
641-
<p><strong>1. Check Boot Messages</strong></p>
642-
<p>Connect to the serial console (115200 baud) and watch for successful boot
643-
messages. You should see:</p>
644-
<ul class="simple">
645-
<li><p>U-Boot loading and executing</p></li>
646-
<li><p>Kernel starting</p></li>
647-
<li><p>Root filesystem mounting</p></li>
648-
<li><p>Kuiper Linux login prompt</p></li>
649-
</ul>
650-
<p><strong>2. Verify Hardware Detection</strong></p>
651-
<p>Once booted, check if your hardware is properly detected:</p>
652-
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># List IIO devices (if your project includes IIO devices)</span>
653-
iio_info
654-
655-
<span class="c1"># Check kernel boot messages</span>
656-
dmesg<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span>-i<span class="w"> </span><span class="s2">&quot;your_device_name&quot;</span>
657-
658-
<span class="c1"># Verify device tree loading</span>
659-
ls<span class="w"> </span>/sys/firmware/devicetree/base/
660-
</pre></div>
661-
</div>
662-
<p><strong>3. Network and System Check</strong></p>
663-
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Verify system information</span>
664-
cat<span class="w"> </span>/etc/os-release
665-
uname<span class="w"> </span>-a
666-
667-
<span class="c1"># Check network (if configured)</span>
668-
ip<span class="w"> </span>addr<span class="w"> </span>show
669-
</pre></div>
670-
</div>
671617
</section>
672618
</section>
673619
<hr class="docutils" />

0 commit comments

Comments
 (0)