![]() |
115200 8-N-1
:
|
|||||||||||
USB Serial Port
should appear in Device Manager. The COMxx
number will be used to configure the terminal emulator. dmesg
command. The /dev/ttyUSBx
number will be used to configure the terminal emulator.
[605576.562740] usb 1-1.1.2: new full-speed USB device number 17 using ehci-pci
[605576.660920] usb 1-1.1.2: New USB device found, idVendor=0403, idProduct=6001
[605576.660933] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[605576.660939] usb 1-1.1.2: Product: TTL232R-3V3
[605576.660944] usb 1-1.1.2: Manufacturer: FTDI
[605576.660958] usb 1-1.1.2: SerialNumber: FTGNVZ04
[605576.663092] ftdi_sio 1-1.1.2:1.0: FTDI USB Serial Device converter detected
[605576.663120] usb 1-1.1.2: Detected FT232RL
[605576.663122] usb 1-1.1.2: Number of endpoints 2
[605576.663124] usb 1-1.1.2: Endpoint 1 MaxPacketSize 64
[605576.663126] usb 1-1.1.2: Endpoint 2 MaxPacketSize 64
[605576.663128] usb 1-1.1.2: Setting MaxPacketSize 64
[605576.663483] usb 1-1.1.2: FTDI USB Serial Device converter now attached to ttyUSB0
A /dev/ttyUSB0 node has been created.
|
|||||||||||||||||||||||||||||||||||||
Etcher
:
Flash!
button
NAND BOOT
jumper is kept closed
nRST
reset button to boot from on-chip Boot ROM AT91 USB to Serial Converter
should appear in Device Manager. If it shows a unknown device you need to download and install the driver: AT91SAM USB CDC driverdmesg
command:
[172677.700868] usb 2-1.4.4: new full-speed USB device number 31 using ehci-pci
[172677.792677] usb 2-1.4.4: not running at top speed; connect to a high speed hub
[172677.793418] usb 2-1.4.4: New USB device found, idVendor=03eb, idProduct=6124
[172677.793424] usb 2-1.4.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[172677.793897] cdc_acm 2-1.4.4:1.0: This device cannot do calls on its own. It is not a modem.
[172677.793924] cdc_acm 2-1.4.4:1.0: ttyACM0: USB ACM device
idVendor=03eb, idProduct=6124: from this message you can see it's Microchip board USB connection.
sam-ba
application is in your Operating System path so that you can reach it from your demo package directory
demo_linux_nandflash.bat
file
demo_linux_nandflash.sh
file
QML
sam-ba script (demo_linux_nandflash_usb.qml
) with proper parameters
-I- === Done. ===
wget -c https://developer.arm.com/-/media/Files/downloads/gnu/13.2.rel1/binrel/arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz
tar -xf arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz export CROSS_COMPILE=`pwd`/arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-or
tar -xf arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz export CROSS_COMPILE=arm-none-linux-gnueabihf- export PATH=$PATH:/YOUR/PATH/TO/arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-linux-gnueabihf/bin/
export PATH=${PATH/':/YOUR/PATH/TO/arm-gnu-toolchain-VERSION-x86_64-arm-none-linux-gnueabihf/bin/'/}
$ git clone https://github.com/linux4sam/at91bootstrap.git Cloning into 'at91bootstrap'... remote: Enumerating objects: 17621, done. remote: Counting objects: 100% (3324/3324), done. remote: Compressing objects: 100% (1029/1029), done. remote: Total 17621 (delta 2465), reused 3102 (delta 2285), pack-reused 14297 Receiving objects: 100% (17621/17621), 5.65 MiB | 4.65 MiB/s, done. Resolving deltas: 100% (13459/13459), done. $ cd at91bootstrap/
configs
folder which contains several default configuration files: sam9x60_curiositynf_uboot_defconfig sam9x60_curiositysd_uboot_defconfig
qspi
means to read quad-SPI serial flash, sd
means to read mmc card, nf
means to read nand flash$ make mrproper $ make sam9x60_curiositysd_uboot_defconfigIf the configuring process is successful, the .config file can be found at AT91Bootstrap root directory.
$ make menuconfigNow, in the menuconfig dialog, you can easily add or remove some features to/from AT91Bootstrap as the same way as kernel configuration.
<Exit>
with arrows and press this button hitting the Enter
key to exit from this screen.
$ makeIf the building process is successful, the final .bin image is build/binaries/at91bootstrap.bin.
$ git clone https://github.com/linux4microchip/u-boot-mchp.git Cloning into 'u-boot-mchp'... remote: Enumerating objects: 951876, done. remote: Counting objects: 100% (17718/17718), done. remote: Compressing objects: 100% (5735/5735), done. remote: Total 951876 (delta 12391), reused 15314 (delta 11846), pack-reused 934158 Receiving objects: 100% (951876/951876), 164.77 MiB | 401.00 KiB/s, done. Resolving deltas: 100% (790362/790362), done. $ cd u-boot-mchp/
$ git branch -r origin/HEAD -> origin/master origin/dev/tony/sama7g5ek_optee origin/master origin/sam9x60_curiosity_early origin/sam9x60_early origin/sam9x60_iar origin/sam9x7_early origin/sama5d27wlsom1ek_ear origin/sama7g5_early origin/u-boot-2012.10-at91 origin/u-boot-2013.07-at91 origin/u-boot-2014.07-at91 origin/u-boot-2015.01-at91 origin/u-boot-2016.01-at91 origin/u-boot-2016.03-at91 origin/u-boot-2017.03-at91 origin/u-boot-2018.07-at91 origin/u-boot-2019.04-at91 origin/u-boot-2020.01-at91 origin/u-boot-2021.04-at91 origin/u-boot-2022.01-at91 origin/u-boot-2023.07-mchp origin/uboot_5series_1.x $ git checkout origin/u-boot-2023.07-mchp -b u-boot-2023.07-mchp Branch 'u-boot-2023.07-mchp' set up to track remote branch 'u-boot-2023.07-mchp' from 'origin'. Switched to a new branch 'u-boot-2023.07-mchp'
configs/
to find the exact target when invoking make.
The U-Boot environment variables can be stored in different media, above config files can specify where to store the U-Boot environment.
# To put environment variables in nand flash: sam9x60_curiosity_nandflash_defconfig # To put environment variables in SD/MMC card: sam9x60_curiosity_mmc_defconfigHere are the building steps for the SAM9X60-Curiosity board:
# You can change the config according to your needs. make sam9x60_curiosity_mmc_defconfig makeThe result of these operations is a fresh U-Boot binary called
u-boot.bin
corresponding to the binary ELF file u-boot
. u-boot.bin
is the file you should store on the board
u-boot
is the ELF format binary file you may use to debug U-Boot through a JTag link for instance.
$ git clone https://github.com/linux4microchip/linux.git Cloning into 'linux'... remote: Enumerating objects: 8587836, done. remote: Total 8587836 (delta 0), reused 0 (delta 0), pack-reused 8587836 Receiving objects: 100% (8587836/8587836), 3.49 GiB | 13.44 MiB/s, done. Resolving deltas: 100% (7117887/7117887), done. Updating files: 100% (70687/70687), done. $ cd linuxThe source code has been taken from the master branch which is pointing on the latest branch we use.
$ git remote add linux4microchip https://github.com/linux4microchip/linux.git $ git remote update linux4microchip Fetching linux4microchip From https://github.com/linux4microchip/linux * [new branch] linux-6.1-mchp -> linux4microchip/linux-6.1-mchp * [new branch] linux-6.6-mchp -> linux4microchip/linux-6.6-mchp * [new branch] master -> linux4microchip/masterIf you want to use another branch, you can list them and use one of them by doing this:
$ git branch -r linux4microchip/linux-5.10-mchp linux4microchip/linux-5.15-mchp linux4microchip/linux-5.15-mchp+fpga linux4microchip/linux-6.1-mchp linux4microchip/linux-6.1-mchp+fpga linux4microchip/linux-6.6-mchp linux4microchip/linux-6.6-mchp+fpga linux4microchip/master $ git checkout -b linux-6.6-mchp --track remotes/linux4microchip/linux-6.6-mchp Branch linux-6.6-mchp set up to track remote branch linux-6.6-mchp from linux4microchip. Switched to a new branch 'linux-6.6-mchp'
wget -c https://developer.arm.com/-/media/Files/downloads/gnu/13.2.rel1/binrel/arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz
tar -xf arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz export CROSS_COMPILE=`pwd`/arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-or
tar -xf arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz export CROSS_COMPILE=arm-none-linux-gnueabihf- export PATH=$PATH:/YOUR/PATH/TO/arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-linux-gnueabihf/bin/
export PATH=${PATH/':/YOUR/PATH/TO/arm-gnu-toolchain-VERSION-x86_64-arm-none-linux-gnueabihf/bin/'/}
arch/arm/configs
arch/arm/configs/at91_dt_defconfig arch/arm/configs/sama5_defconfig arch/arm/configs/sama7_defconfig
at91_dt_defconfig
: for SAM9 (ARM926) series chips
sama5_defconfig
: for SAMA5 series chips
sama7_defconfig
: for SAMA7 series chips
menuconfig
$ make ARCH=arm menuconfigNow, in the menuconfig dialog, you can easily add or remove some features. Once done, Move to
<Exit>
with arrows and press this button hitting the Enter
key to exit from this screen.
Build the Linux kernel image, before you build you need set up the cross compile toolchain, check this section.
$ make ARCH=arm [..] Kernel: arch/arm/boot/Image is ready Kernel: arch/arm/boot/zImage is readyNow you have an usable compressed kernel image
zImage
.
If you need an uImage you can run this additional step:
make ARCH=arm uImage LOADADDR=0x20008000 [..] Kernel: arch/arm/boot/zImage is ready UIMAGE arch/arm/boot/uImage Image Name: Linux-6.6.23-linux4microchip-202 Created: Thu May 16 14:36:06 2024 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5221704 Bytes = 5099.32 KiB = 4.98 MiB Load Address: 20008000 Entry Point: 20008000 Kernel: arch/arm/boot/uImage is ready
make ARCH=arm dtbs [..] DTC arch/arm/boot/dts/microchip/at91-sam9x60_curiosity.dtb DTC arch/arm/boot/dts/microchip/at91-sam9x60ek.dtb DTC arch/arm/boot/dts/microchip/at91-sam9x75_curiosity.dtb DTC arch/arm/boot/dts/microchip/at91-sam9x75eb.dtb DTC arch/arm/boot/dts/microchip/at91-sama5d27_som1_ek.dtb DTC arch/arm/boot/dts/microchip/at91-sama5d27_wlsom1_ek.dtb DTC arch/arm/boot/dts/microchip/at91-sama5d29_curiosity.dtb DTC arch/arm/boot/dts/microchip/at91-sama5d2_icp.dtb DTC arch/arm/boot/dts/microchip/at91-sama5d2_ptc_ek.dtb DTC arch/arm/boot/dts/microchip/at91-sama5d2_xplained.dtb DTC arch/arm/boot/dts/microchip/at91-sama7g5ek.dtb [..]If the building process is successful, the final images can be found under arch/arm/boot/ directory.
meta-atmel
. The source for this layer are hosted on Linux4SAM GitHub accountgit-lfs
to the package requirement list from whichever Linux distribution you use.
For instance, on Ubuntu or debian, these packages need to be installed on your development host:
sudo apt-get install gawk wget git-core git-lfs diffstat unzip texinfo gcc-multilib \ build-essential chrpath socat cpio python3 python3-pip python3-pexpect \ xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \ pylint3 xterm
meta-atmel
layer. This file in the meta-atmel layer repository must be considered as the reference and the following copy can be out-of-sync.
Linux4SAM 2021.04
release, the meta-atmel
layer supports Yocto templates, so make sure you create a new build environment using oe-init-build-env
This layer provides support for Microchip microprocessors (aka AT91) ==================================================================== For more information about the Microchip MPU product line see: http://www.microchip.com/design-centers/32-bit-mpus Linux & Open Source on Microchip microprocessors: http://www.linux4sam.org Supported SoCs / MACHINE names ============================== Note that most of the machine names below, have a SD Card variant that can be built by adding an "-sd" suffix to the machine name. - SAMA5D2 product family / sama5d2-xplained, sama5d2-xplained-emmc, sama5d27-som1-ek-sd, sama5d27-som1-ek-optee-sd, sama5d2-ptc-ek, sama5d2-icp, sama5d27-wlsom1-ek-sd, sama5d29-curiosity-sd - SAMA5D4 product family / sama5d4ek, sama5d4-xplained - SAMA5D3 product family / sama5d3xek, sama5d3-xplained - AT91SAM9x5 product family (AT91SAM9G15, AT91SAM9G25, AT91SAM9X25, AT91SAM9G35 and AT91SAM9X35) / at91sam9x5ek - AT91SAM9RL / at91sam9rlek - AT91SAM9G45 / at91sam9m10g45ek - SAM9X60 / sam9x60ek, sam9x60-curiosity - SAMA7G5 / sama7g5ek-sd, sama7g5ek-emmc, sama7g5ek-ospi - SAM9X75 / sam9x75eb, sam9x75-curiosity Sources ======= - meta-atmel URI: https://github.com/linux4sam/meta-atmel.git Branch: kirkstone Tag:linux4microchip-2024.04 Dependencies ============ This Layer depends on : - poky URI: https://git.yoctoproject.org/poky Branch: kirkstone Tag:yocto-4.0.17 - meta-openembedded URI: https://git.openembedded.org/meta-openembedded Branch: kirkstone Tag/commit:8bb16533532b6abc2eded7d9961ab2a108fd7a5b - meta-arm (for optee components) URI: https://git.yoctoproject.org/meta-arm Branch: kirkstone Tag:yocto-4.0.2 Build procedure =============== 0/ Create a directory mkdir my_dir cd my_dir 1/ Clone yocto/poky git repository with the proper branch ready git clone https://git.yoctoproject.org/poky && cd poky && \ git checkout -b kirkstone yocto-4.0.17 && cd - 2/ Clone meta-openembedded git repository with the proper branch ready git clone git://git.openembedded.org/meta-openembedded && \ cd meta-openembedded && git checkout -b kirkstone 8bb165 && cd - 3/ Clone meta-atmel layer with the proper branch ready git clone https://github.com/linux4sam/meta-atmel.git git checkout -b kirkstone linux4microchip-2024.04 && cd - 4/ Clone meta-arm layer with the proper branch ready git clone https://git.yoctoproject.org/meta-arm && cd meta-arm && \ git checkout -b kirkstone yocto-4.0.2 && cd - 5/ Enter the poky directory to configure the build system and start the build process cd poky If not created yet, add a new "build-microchip" directory: mkdir build-microchip Else, if it's the first time you use Yocto Project templates, and if the build-microchip directory remains from a previous use, we advise you to start from a fresh directory. Keep your build-microchip/conf/local.conf file for reference. 6/ Inside the .templateconf file, you will need to modify the TEMPLATECONF variable to match the path to the meta-atmel layer "conf" directory: export TEMPLATECONF=${TEMPLATECONF:-../meta-atmel/conf} 7/ Initialize build directory source oe-init-build-env build-microchip 8/ To build a small image provided by Yocto Project: [MACHINE=] bitbake core-image-minimal Example for sama5d2-xplained-sd SD card image: MACHINE=sama5d2-xplained-sd bitbake core-image-minimal 9/ To build the microchip image with no graphics support: [MACHINE= ] bitbake microchip-headless-image Example for sama5d2-xplained-sd SD card image: MACHINE=sama5d2-xplained-sd bitbake microchip-headless-image 10/ To build the microchip image with graphics support (EGT): [MACHINE= ] bitbake microchip-graphics-image Example for sama5d2-xplained-sd SD card image: MACHINE=sama5d2-xplained-sd bitbake microchip-graphics-image Typical bitbake output ====================== Build Configuration: BB_VERSION = "2.0.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "sam9x75-curiosity-sd" DISTRO = "poky-atmel" DISTRO_VERSION = "4.0.17" TUNE_FEATURES = "arm armv5 thumb dsp" TARGET_FPU = "soft" meta meta-poky meta-yocto-bsp = "heads/kirkstone-4.0.17:6d1a878bbf24c66f7186b270f823fcdf82e35383" meta-oe meta-networking meta-webserver meta-python meta-initramfs = "8bb16533532b6abc2eded7d9961ab2a108fd7a5b:8bb16533532b6abc2eded7d9961ab2a108fd7a5b" meta-atmel = "heads/linux4microchip-2024.04-rc2:fd6500c866002b78e8ec752e11e34cff0acbc044" meta-multimedia = "8bb16533532b6abc2eded7d9961ab2a108fd7a5b:8bb16533532b6abc2eded7d9961ab2a108fd7a5b" meta-arm meta-arm-toolchain = "heads/yocto-4.0.2:96aad3b29aa7a5ee4df5cf617a6336e5218fa9bd" Contributing ============ To contribute to this layer you should submit the patches for review to: the github pull-request facility directly or the forum. Anyway, don't forget to Cc the maintainers. Microchip Forum: https://www.microchip.com/forums/f542.aspx for some useful guidelines to be followed when submitting patches: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Maintainers: Hari Prasath G E Nicolas Ferre When creating patches insert the [meta-atmel] tag in the subject, for example use something like: git format-patch -s --subject-prefix='meta-atmel][PATCH'
QML
language for scripting used for flashing the demos, most common SAM-BA action can be done using SAM-BA command line.
For browsing information on the SAM-BA command line usage, please see the Command Line Documentation that is available in the SAM-BA installation directory: doc/index.html
or doc/cmdline.html
.
SAM-BA includes command line interface that provides support for the most common actions:
The command line interface is designed to be self-documenting.
The main commands can be listed using the "sam-ba --help" command:
SAM-BA Command Line Tool v3.8 Copyright 2024 Microchip Technology Usage: ./sam-ba [options] SAM-BA Command Line Tool Options: -v, --version Displays version information. -h, --help Displays this help. -t, --tracelevel <trace_level> Set trace level to <trace_level>. -L, --applet-buffer-limit <SIZE> Set applet buffer limit to <SIZE>
bytes (default 131072). -x, --execute <script.qml> Execute script <script.qml>. -p, --port <port[:options:...]> Communicate with device using <port>. -d, --device <device[:options:...]> Connected device is <device>. -b, --board <board[:options:...]> Connected board is <board>. -m, --monitor <command[:options:...]> Run monitor command <command>. -a, --applet <applet[:options:...]> Load and initialize applet <applet>. -c, --command <command[:args:...]> Run command <command>. -w, --working-directory <DIR> Set working directory to <DIR>.
Additional help can be obtained for most commands by supplying a "help" parameter that will display their usage.
For example "sam-ba --port help" will display:
Known ports: j-link, serial, secure
Command that take an argument with options (port, monitor, applet) will display even more documentation when called with "help" as option value.
For example "sam-ba --port serial:help" will display:
Syntax: serial:[<port>]:[<baudrate>] Examples: serial serial port (will use first AT91 USB if found otherwise first serial port) serial:COM80 serial port on COM80 serial:ttyUSB0:57600 serial port on /dev/ttyUSB0, baudrate 57600
-b
parameter of SAM-BA, the default PMECC configuration for the NAND populated on the board is valid. You can verify its value by running the command that reads one byte in a dummy file (named test.bin
in the following command):
# sam-ba -p serial -b sam9x60-curiosity -a nandflash -c read:test.bin:0:1
Opening serial port 'ttyACM0'
Connection opened.
Detected memory size is 536870912 bytes.
Page size is 4096 bytes.
Buffer is 12288 bytes (3 pages) at address 0x003085a0.
NAND header value is 0xc2605007.
Supported erase block sizes: 256KB
Executing command 'read:test.bin:0:1'
Read 1 bytes at address 0x00000000 (100.00%)
Connection closed.
You can figure out that the default PMECC parameter for this sam9x60-curiosity
board is 0xc2605007.
Applet 'NAND Flash' from SAM-BA Applets Framework 3.8 (v3.8). Initializing NAND ioSet1 Bus Width 8 PMECC configuration: 0xc2605007 Sector size: 512 Sectors per page: 8 Spare size: 256 ECC bits: 8 ECC offset: 152 ECC size: 104 PMECC enabled Buffer Address: 0x003085a0 Buffer Size: 12288 bytes NAND applet initialized successfully.If you want to change the default PMECC parameters you can simply specify another value on the SAM-BA command line with the
-a nandflash
argument as shown below:
# sam-ba -p serial -b sam9x60-curiosity -a nandflash:help
Syntax: nandflash:[<ioset>]:[<bus_width>]:[<header>]
Parameters:
ioset I/O set
bus_width NAND bus width (8/16)
header NAND header value
Examples:
nandflash use default board settings
nandflash:2:8:0xc0098da5 use fully custom settings (IOSET2, 8-bit bus, header is 0xc0098da5)
nandflash:::0xc0098da5 use default board settings but force header to 0xc0098da5
For information on NAND header values, please refer to SAMA5D4 datasheet section "12.4.4 Detailed Memory Boot Procedures".
By reading this in-line documentation we can specify the NAND PMECC parameter with this command:
# sam-ba -p serial -b sam9x60-curiosity -a nandflash:::0xc2605007 Opening serial port 'ttyACM0' Connection opened. Detected memory size is 536870912 bytes. Page size is 4096 bytes. Buffer is 20480 bytes (5 pages) at address 0x0020a240. NAND header value is 0xc2605007. Supported erase block sizes: 256KB Connection closed.
serial
) and erase the beginning of the NAND flash and then write AT91Bootstrap binary:
# sam-ba -p serial -b sam9x60-curiosity -a nandflash -c erase::0x40000 -c writeboot:at91bootstrap-sam9x60_curiosity.bin Opening serial port 'ttyACM0' Connection opened. Detected memory size is 536870912 bytes. Page size is 4096 bytes. Buffer is 20480 bytes (5 pages) at address 0x0020a240. NAND header value is 0xc2605007. Supported erase block sizes: 256KB Executing command 'erase::0x40000' Erased 262144 bytes at address 0x00000000 (100.00%) Executing command 'writeboot:at91bootstrap-sam9x60_curiosity.bin' Prepended NAND header prefix (0xc1e04e07) Appending 4008 bytes of padding to fill the last written page Wrote 20480 bytes at address 0x00000000 (83.33%) Wrote 4096 bytes at address 0x00005000 (100.00%) Connection closed.
serial
) and erase the U-Boot section in the NAND flash memory map and then write U-Boot binary:
# sam-ba -p serial -b sam9x60-curiosity -a nandflash -c erase:0x40000:0x80000 -c write:u-boot-sam9x60-curiosity.bin:0x40000 Opening serial port 'ttyACM0' Connection opened. Detected memory size is 536870912 bytes. Page size is 4096 bytes. Buffer is 20480 bytes (5 pages) at address 0x0020a240. NAND header value is 0xc2605007. Supported erase block sizes: 256KB Executing command 'erase:0x40000:0x80000' Erased 262144 bytes at address 0x00040000 (50.00%) Erased 262144 bytes at address 0x00080000 (100.00%) Executing command 'write:u-boot-sam9x60-curiosity.bin:0x40000' Appending 3137 bytes of padding to fill the last written page Wrote 20480 bytes at address 0x00040000 (4.59%) Wrote 20480 bytes at address 0x00045000 (9.17%) Wrote 20480 bytes at address 0x0004a000 (13.76%) [..] Wrote 20480 bytes at address 0x00094000 (81.65%) Wrote 20480 bytes at address 0x00099000 (86.24%) Wrote 20480 bytes at address 0x0009e000 (90.83%) Wrote 20480 bytes at address 0x000a3000 (95.41%) Wrote 20480 bytes at address 0x000a8000 (100.00%) Connection closed.
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microchip and others, are registered trademarks or trademarks of Microchip Technology Inc. and its subsidiaries.
Arm® and others are registered trademarks or trademarks of Arm Limited (or its affiliates). Other terms and product names may be trademarks of others.
Ideas, requests, contributions ? Connect to LinksToCommunities page.