adi-linux-docs Mailing List for ADI Linux Kernel
Linux kernel port for the ADI's Blackfin and future processors
Brought to you by:
aaronwu1,
davidgibsonadi
Menu
▾
▴
adi-linux-docs — ADI Linux open source document
You can subscribe to this list here.
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(10) |
Oct
(29) |
Nov
(11) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2014 |
Jan
|
Feb
|
Mar
(8) |
Apr
(2) |
May
(6) |
Jun
(5) |
Jul
(16) |
Aug
(6) |
Sep
(8) |
Oct
(6) |
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: aaronwu1 <no...@do...> - 2016-09-21 08:37:39
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:tcpip_performance Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:tcpip_performance&rev=1318916671 Edit Summary: [Iperf TCP test] @@ -4,8 +4,9 @@ The kernel source is the latest pre 2011R1 based on kernel 2.6.30. The hardware is BF527 EZKIT v2.2 and bf527 v0.2 connect to a host PC via on chip 100M EMAC. The kernel configuration is the default BF527-EZKIT-V2 with oprofile enabled. ==== Iperf TCP test ==== ===oprofile result when blackfin runs as TCP client=== + Note we need to run "ipers -s" first on server before running as client on another side. <code> root:/> iperf -c 10.100.4.174 -t 30 ------------------------------------------------------------ Client connecting to 10.100.4.174, TCP port 5001 |
|
From: daveg <no...@bl...> - 2016-07-06 08:20:15
|
New Revision: https://blackfin.uclinux.org/doku.php?id=main Old Revision: https://blackfin.uclinux.org/doku.php?id=main&rev=1410338846 Edit Summary: Page title is now Blackfin specific, added reference to Linux for ADSPSC5xx @@ -1,6 +1,12 @@ - ====== Analog Devices Open Source Projects ====== + ====== Analog Devices Open Source Projects For Blackfin Processors ====== This site is the central location for open source and free software and hardware projects targeted for use with certain members of the Analog Devices Blackfin processor family, and Analog Devices peripherals (and their associated Linux drivers). In addition to a wide range of applications, this site also focuses on supporting Open Source hardware and software tools, including the GNU GCC toolchain, u-boot boot loader and the buildroot distribution. It is sponsored and supported by a small team from Analog Devices. + + **Analog Devices Linux for ADSP-SC5xx Processors** + + Analog Devices has introduced a new Open Source product for it's ADSP-SC5xx family of processors. + The Linux Add-In for CrossCore Embedded Studio provides users with full Linux for the ADSP-SC5xx ARM core, along with open source development tools. Analog Devices World Class IDE is also available. + For more information [[http://www.analog.com/en/design-center/processors-and-dsp/evaluation-and-development-software/linuxaddin.html|analog.com]]. **The development of the Blackfin Linux Projects is moved to sourceforge.net since Jul. 20, 2013.** In order to provide a more reliable service for our customers, from Jul. 20, 2013, the Blackfin Linux projects, source repositories and released files are moved to [[http://sourceforge.net|sourceforge.net]]. The legacy forum threads and bugs after Jan. 1st, 2009 are moved to [[ez>|ADI EZ Engineer Zone]](under construction). Forum threads and bugs before 2009 can never be accessed. |
|
From: steven.miao <no...@do...> - 2016-07-01 03:51:57
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1467344484 Edit Summary: [Dispatch packet] @@ -1390,8 +1390,9 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== + {{:protocols:icc_layer1.png|}} **icc session layer manage the user space packet send/recv session** the sm_session data structure: @@ -1413,11 +1414,14 @@ wait_queue_head_t rx_wait; } __attribute__((__aligned__(4))); </code> + if the icc queue is full, packet send will be blocked on icc queue tx_wait wait queue until the tx queue is not full. - **message_queue_thread** + packet receive will blocked on session's rx_wait queue if there's no available message, until the ipi wait up the icc queue thread to hanle incoming message, receive the message to packet and wakeup the packet recv process sleeping on rx_wait queue. + **message_queue_thread** + kernel thread to handle incoming msg, the remote ipi will wakeup this thread. **On core running Linux** * To send a packet in application , the packet buffer should be allocated in user space first. Its pointer then is passed to the kernel system call. Kernel code also allocates a buffer in kernel space and copies the user data in. After that, the dsp bridge driver appends a packet ready message with packet address and length to the shared message queue in L2 memory and link the packet buffer to the sent list. |
|
From: steven.miao <no...@do...> - 2016-07-01 03:43:26
|
File : https://docs.blackfin.uclinux.org/lib/exe/fetch.php?media=protocols:icc_layer1.png Size : 23.8 KB MIME : image/png |
|
From: steven.miao <no...@do...> - 2016-07-01 03:42:03
|
File : https://docs.blackfin.uclinux.org/lib/exe/fetch.php?media=protocols:icc_layer.png Size : 23.8 KB MIME : image/png |
|
From: steven.miao <no...@do...> - 2016-07-01 03:41:31
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1467343769 Edit Summary: [Dispatch packet] @@ -1390,9 +1390,8 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== - {{:protocols:icc_layer.png|}} **icc session layer manage the user space packet send/recv session** the sm_session data structure: |
|
From: steven.miao <no...@do...> - 2016-07-01 03:38:59
|
File : https://docs.blackfin.uclinux.org/lib/exe/fetch.php?media=protocols:icc_layer.png Size : 23.8 KB MIME : image/png |
|
From: steven.miao <no...@do...> - 2016-07-01 03:34:52
|
File : https://docs.blackfin.uclinux.org/lib/exe/fetch.php?media=protocols:icc_layer.png Size : 31.3 KB MIME : image/png |
|
From: steven.miao <no...@do...> - 2016-07-01 03:32:26
|
File : https://docs.blackfin.uclinux.org/lib/exe/fetch.php?media=protocols:icc_layer.png Size : 52.9 KB MIME : image/png |
|
From: steven.miao <no...@do...> - 2016-07-01 03:29:55
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1386125529 Edit Summary: [Dispatch packet] @@ -1389,8 +1389,34 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== + + **icc session layer manage the user space packet send/recv session** + + the sm_session data structure: + + <code> + struct sm_session { + struct list_head rx_messages; /*rx queue sm message*/ + struct list_head tx_messages; + uint32_t n_avail; + uint32_t n_uncompleted; + uint32_t local_ep; + uint32_t remote_ep; /*remote ep*/ + uint32_t type; + pid_t pid; + uint32_t flags; + int (*handle)(struct sm_message *msg, struct sm_session *session); + struct sm_proto *proto_ops; + uint32_t queue_priority; + wait_queue_head_t rx_wait; + } __attribute__((__aligned__(4))); + </code> + + + **message_queue_thread** + **On core running Linux** * To send a packet in application , the packet buffer should be allocated in user space first. Its pointer then is passed to the kernel system call. Kernel code also allocates a buffer in kernel space and copies the user data in. After that, the dsp bridge driver appends a packet ready message with packet address and length to the shared message queue in L2 memory and link the packet buffer to the sent list. |
|
From: steven.miao <no...@do...> - 2016-07-01 03:29:35
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1467342757 Edit Summary: [Dispatch packet] @@ -1389,8 +1389,10 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== + + {{:protocols:icc_layer.png|}} **icc session layer manage the user space packet send/recv session** the sm_session data structure: |
|
From: steven.miao <no...@do...> - 2016-07-01 03:29:13
|
File : https://docs.blackfin.uclinux.org/lib/exe/fetch.php?media=protocols:icc_layer.png Size : 24.2 KB MIME : image/png |
|
From: aaronwu1 <no...@do...> - 2016-01-29 08:10:06
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=test_mcapi Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=test_mcapi&rev=1370598424 Edit Summary: [build CCES mcapi msg test project] @@ -144,8 +144,10 @@ {0x4000000, (ENUM_DCPLB_DATA_64MB | CPLB_DNOCACHE)}, </code> ** build project ** Project -> build project + + After building successfully we get the file BF609_MCAPI_msg_CORE1.dxe, we can load it onto core B to run in two ways, either by the ROM code or by the Linux, details below. ==== load CCES mcapi test application by bootrom ==== Blackfin bootrom allows to load 1 LDR image into memory and run on both cores after reset. You can pack core1 MCAPI dxe binary and core 0 uboot elf binary into one LDR image by bfin-elf-ldr utility and run MCAPI application on core1 at the very begining of uboot init. |
|
From: aaronwu1 <no...@do...> - 2016-01-29 08:10:06
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=test_mcapi Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=test_mcapi&rev=1454054160 Edit Summary: [build CCES mcapi msg test project] @@ -145,9 +145,9 @@ </code> ** build project ** Project -> build project - After building successfully we get the file BF609_MCAPI_msg_CORE1.dxe, we can load it onto core B to run in two ways, either by the ROM code or by the Linux, details below. + After building successfully we get the file BF609_MCAPI_msg_CORE1.dxe, we can load it onto core B to run in two ways, either by the bootrom code or by the Linux, details below. ==== load CCES mcapi test application by bootrom ==== Blackfin bootrom allows to load 1 LDR image into memory and run on both cores after reset. You can pack core1 MCAPI dxe binary and core 0 uboot elf binary into one LDR image by bfin-elf-ldr utility and run MCAPI application on core1 at the very begining of uboot init. |
|
From: grace <no...@do...> - 2015-07-23 07:11:50
|
New Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: pc_ubuntu_setup Old Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: pc_ubuntu_setup&rev=1423721060 Edit Summary: install cifs-utils @@ -6,9 +6,9 @@ *Set the root password as "blackfin":<xterm>**$ sudo passwd root**</ xterm> *Use apt-get install to install the following packages through DHCP allocated ipaddress. <xterm>**$ sudo apt-get install vim-nox openssh-serve r expect default-jdk minicom ckermit gawk \ git-core g++ bison flex gettext texinfo libncurses5-dev subversion m eld \ rsh-client mpg123 python-setuptools python-dev netperf tftpd-hpa \ - uuid-dev genromfs samba xz-utils intltool ethtool libtool wakeonlan **</ xterm>Package mpg123 is for audio test. Package uuid-dev is for host-e2fsp rogs. Package genromfs is for xip test. Package intltool is for linphone t est. Package wakeonlan is for ethernet wakeup test. Install vim-nox is for tool vimdiff. Install default-jdk is for openjdk-6-jdk + uuid-dev genromfs samba cifs-utils xz-utils intltool ethtool libtool wak eonlan **</xterm>Package mpg123 is for audio test. Package uuid-dev is for host-e2fsprogs. Package genromfs is for xip test. Package intltool is for linphone test. Package wakeonlan is for ethernet wakeup test. Install vim -nox is for tool vimdiff. Install default-jdk is for openjdk-6-jdk *Configure static network ipaddress using network interfaces instead of DHCP ( **Notice** : 10.99.29.xx is available only in lab, before movin g eth0 should remain the DHCP setting): *Don't use network-manager as it handles multiple network cards ba dly. Disable network-manager in file /etc/rc.local by adding following scr ipts:<code> service network-manager stop ifup eth0 eth1</code> |
|
From: sonicz <no...@bl...> - 2015-07-01 10:57:39
|
New Revision: https://blackfin.uclinux.org/doku.php?id=processes Old Revision: https://blackfin.uclinux.org/doku.php?id=processes&rev=1 435747055 Edit Summary: fix graph @@ -309,15 +309,15 @@ and the Blackfin/GNU Toolchain, which is managed in a similar way, excep t for the bits and pieces (like the eclipse plugins, and ldr utils, which we create, and maintain 100%): <graphviz dot> digraph { - "blackfin.uclinux.org git" -> "release" - "mainline uClibc" -> "blackfin.uclinux.org git" -> "mainline uClibc" ; - "FSF gcc" -> "blackfin.uclinux.org git" -> "FSF gcc" ; - "FSF binutils" -> "blackfin.uclinux.org git" -> "FSF binutils"; - "FSF gdb" -> "blackfin.uclinux.org git" -> "FSF gdb"; - "eclipse plugins" -> "blackfin.uclinux.org git"; - "ldr-utils" -> "blackfin.uclinux.org git"; + "blackfin.uclinux.org svn" -> "release" + "mainline uClibc" -> "blackfin.uclinux.org svn" -> "mainline uClibc" ; + "FSF gcc" -> "blackfin.uclinux.org svn" -> "FSF gcc" ; + "FSF binutils" -> "blackfin.uclinux.org svn" -> "FSF binutils"; + "FSF gdb" -> "blackfin.uclinux.org svn" -> "FSF gdb"; + "eclipse plugins" -> "blackfin.uclinux.org svn"; + "ldr-utils" -> "blackfin.uclinux.org svn"; } </graphviz> <note important>While the desire is that people should be able to take a mainline project and have it function, and work with it, this is not the most important thing when it comes to making releases, or doing developmen t. While we spend best efforts in working with the mainline projects, peop le who develop products with the Blackfin are recommended to get their sou rce code from this site, which has been tested and released for production development. @@ -378,23 +378,23 @@ } subgraph cluster_1 { node [style=filled]; - rc1 -> rc2 -> "2012R1 head"; - label = "branch 2012R1"; + rc1 -> rc2 -> "2008R1 head"; + label = "branch 2008R1"; color=blue } subgraph cluster_2 { node [style=filled]; rc_1 -> rc_2; - label = "branch 2013R1"; + label = "branch 2009R1"; color=blue } a1 -> rc1; a3 -> rc_1; "bug fix1" -> a2; "bug fix2" -> a3; - "bug fix2" -> "2012R1 head"; + "bug fix2" -> "2008R1 head"; "bug fix1" -> rc1; "new feature" -> a3; "update to mainline" -> a3; } |
|
From: sonicz <no...@bl...> - 2015-07-01 10:52:39
|
New Revision: https://blackfin.uclinux.org/doku.php?id=processes Old Revision: https://blackfin.uclinux.org/doku.php?id=processes&rev=1 435747339 Edit Summary: fix graph @@ -281,12 +281,12 @@ The Linux kernel is a integral part of this, but is handled in a more st ructured manner, due to it's development process. <graphviz dot> digraph { - "blackfin.uclinux.org git" -> "blackfin git tree" -> "Linus git tree" - > "official Linux release" - "blackfin.uclinux.org git" -> "driver maintainer git tree" -> "Linus gi t tree" -> "official Linux release" + "blackfin.uclinux.org svn" -> "blackfin git tree" -> "Linus git tree" - > "official Linux release" + "blackfin.uclinux.org svn" -> "driver maintainer git tree" -> "Linus gi t tree" -> "official Linux release" "Linus git tree" -> "blackfin git tree" - "official Linux release" -> "blackfin.uclinux.org git" + "official Linux release" -> "blackfin.uclinux.org svn" } </graphviz> For example; @@ -300,10 +300,10 @@ U-Boot is managed in a similar way, where we send patches to the mainlin e maintainers, and periodically update the local git to become synced with the mainline project. <graphviz dot> digraph { - "blackfin.uclinux.org git" -> "release" - "mainline U-Boot" -> "blackfin.uclinux.org git" -> "mainline U-Boot" ; + "blackfin.uclinux.org svn" -> "release" + "mainline U-Boot" -> "blackfin.uclinux.org svn" -> "mainline U-Boot" ; } </graphviz> and the Blackfin/GNU Toolchain, which is managed in a similar way, excep t for the bits and pieces (like the eclipse plugins, and ldr utils, which we create, and maintain 100%): |
|
From: sonicz <no...@bl...> - 2015-07-01 10:52:39
|
New Revision: https://blackfin.uclinux.org/doku.php?id=processes Old Revision: https://blackfin.uclinux.org/doku.php?id=processes&rev=1 435747426 Edit Summary: fix graph @@ -373,9 +373,9 @@ style=filled; color=lightgrey; node [style=filled,color=white]; a0 -> a1 -> a2 -> a3 -> a4 -> a5; - label = "master"; + label = "Trunk"; } subgraph cluster_1 { node [style=filled]; |
|
From: grace <no...@do...> - 2015-05-12 06:53:43
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=%E5%AE%9E%E4 %B9%A0%E5%B7%A5%E4%BD%9C%E8%AF%B4%E6%98%8E%E6%96%87%E6%A1%A3 Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=%E5%AE%9E%E4 %B9%A0%E5%B7%A5%E4%BD%9C%E8%AF%B4%E6%98%8E%E6%96%87%E6%A1%A3&rev=1431412 235 Edit Summary: update @@ -16,15 +16,8 @@ 建立workspace，输入命令 ：mkdir workspace 所需要到的code都可通过blackfin.uclinux.org这个主进入sourceforge.net网页进下载。\\ 通过git clone 命令。\\ - 下面列举两个例子 ：\\ - - 下载u-boot ：<code> - git clone git://nwd2cvs1.corp.analog.com/git/unreleased/u-boot.git u-boo t - - - 下载buildroot:<code> - git clone git://nwd2cvs1.corp.analog.com/git/unreleased/buildroot.git - 当使用git clone下来到工 程中带有submodule时，初 始的时候，submodule的内 容并不会自动下载 ，需要 在buildroot目录下执行下 面命令：<code> git submodule init git submodule update</code> |
|
From: grace <no...@do...> - 2015-05-12 06:42:40
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=%E5%AE%9E%E4 %B9%A0%E5%B7%A5%E4%BD%9C%E8%AF%B4%E6%98%8E%E6%96%87%E6%A1%A3 Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=%E5%AE%9E%E4 %B9%A0%E5%B7%A5%E4%BD%9C%E8%AF%B4%E6%98%8E%E6%96%87%E6%A1%A3&rev= Edit Summary: created ===== 第一步：安装Ubun tu ===== - 放入CD或插上U盘，下F12键，进入启动 页面，选择相应启 动方式。 - 进入安装界面，择install Ubuntu选项，进行一步。 - 进入设置页面，除原有系统，进新的磁盘分区。行磁盘分区时，意三个分区必须：1.swap ;2./(root目录);3./home(用户 主目录)。设置开机 密码，比如,可设机 器的开机密码为test采用英文版系统默认选择就可以 - 安装完成后，重电脑 ===== 第二步：对电进行相应配置 ==== = 参见网页：blackfin.uclinux.org.择The Linux kernel/testing，到网页 最低部，选择How to set up ubuntu 12.04 on regression PC，进入相应配置文档。\\ 配置过程中需要拷 贝到文件，可以到 其他机器上拷贝：ss h 10.99.29.* 拷贝之前先通过ifconfig询一下自己电脑IP，电脑之间到拷命令为scp，如果拷 贝的是目录，采用 scp -r 命令进行拷贝。 配置完成后，对系 统进行重启。 （注：配置过程一 定要按照文档一步 一步来，否则会出 现一些问题） ===== 第三步：建立work space以及相应Code的下载 ===== 建立workspace，输入命令 ：mkdir workspace 所需要到的code都可通过blackfin.uclinux.org这个主进入sourceforge.net网页进行 下载。或者从内部 资料库下载：10.99.29.20机 器上。\\ 通过git clone 命令。\\ 下面列举两个例子 ：\\ - 下载u-boot ：<code> git clone git://nwd2cvs1.corp.analog.com/git/unreleased/u-boot.git u-boot 或者从内部机器上 下载 git clone git://10.99.29.20/git/unreleased/u-boot.git u-boot</code> - 下载buildroot:<code> git clone git://nwd2cvs1.corp.analog.com/git/unreleased/buildroot.git 或者从内部机器上 下载 git clone git://10.99.29.20/git/unreleased/buildroot.git</code> 当使用git clone下来到工 程中带有submodule时，初 始的时候，submodule的内 容并不会自动下载 ，需要 在buildroot目录下执行下 面命令：<code> git submodule init git submodule update</code> 在完成相应的下载 之后，需要查看branch通过git branch来查看。\\ ===== 第四步：编译u-bo ot和uImage ===== 在编译u-boot和uImage之前要确定机器上面否有toolchain，<code> $ cd /opt/ $ ls</code> 如果没有，需要去10 .99.29.*上面进行拷贝。<co de> $ ssh 10.99.29.* $ scp toolchain.tar.gz test@10.99.24.*:/opt</code> 如果给出没有权限 ，需要在命令前面 添加sudo\\ 如果还是不能拷贝 ，进行如下操作<code> $ sudo scp toolchain.tar.gz test@10.99.24.*:/home/test $ exit $ sudo cp toolchain.tar.gz /opt/uClinux $ cd /opt/uClinux $ tar -xf toolchain.tar.gz</code> (1)u-boot编译示例：<code> $ cd u-boot $ make bf609-ezkit_config （要和所用子对应，可以通命令$ ls configs/bf 来找对的配置文件） $ pex (需要在本机主目下.bash_aliases文件中设置: alias pex='export PATH=/opt/uClinux/bfin-uclinux/bin:/opt/uClinux/bfin -elf/bin:/opt/uClinux/bfin-linux-uclibc/bin:$PATH') $ make $ cp u-boot.ldr /tftpboot</code> (2)uImage编译示例 编译uImage时，如果是同一个板子，测不同的项目，在新编译uImage时，需执行一下make clean命令，清除之前配置。 如果测试不同的板 子时，需要对板子 重新配置make *_defconfig，当为了防止之前的试影响到后面到 试，可以使用make distclean进行彻底清除。<code> $ cd buildroot $ make bf609-ezkit_defconfig（要和所用 板子对应，可以通 过命令$ ls configs/bf 来找对的配置文件） $ make clean $ pex (确认安装的toolchain能找到) $make menuconfig $make linux-menuconfig $ make $ cp output/images/uImage /tftpboot</code> 注意：检测branch是否致，并且符合板要求。 在buildroot目录下面，运 行<code> $ git branch $ cd linux/linux-kernel/ $ git branch</code> 如果branch 不一致，需将其切换到一致下面命令是以blackfin例。 $ git checkout master 编译uImage时，由于所试到项目不同，需要根据不同测脚本进行相应到置，配置过程在常使用 到两个命令分别是 ：make menuconfig,make linux-menuconfig。这两 个命令都是运行在ma ke *_defconfig之后。 ===== 第五步：烧写u-bo ot ===== === 1.通过JTAG烧写 === （1）先到10.99.24.51上拷jtag-gnice目录。里面有应板子到flash文件。 （2）进入jtag-gnice目录下 面，查看需要烧u-boot子型号对应到flash文 件，如：vi flash-bf537- stamp.jtag 。查看其要求到 u-boot类型：是u-boot.ldr还是u-bo ot.bin （3）拷贝相应到u-boot 型到 /tftpboot下面 （4）切换到/opt/uClinux/bfin-elf/bin录下，运行下面令：<code> sudo ./bfin-jtag ~/jtag-gnice/flash-*</code> （5）烧写完成后， 打开minicom，设置相应IP （前提是可以boot起），命令如下：<code> set ipaddr 10.100.4.50 set serverip 10.100.4.174 saveenv</code> === 2.通过UART烧写 === （1）拷贝相应u-boot.ldr.uart件到/tftpboot目录下面 （2）查看相应板子 到文档，根据文档 把板子对应到硬件 开关调到uart位置上 （3）运行下面命令 ：<code> bfin-uclinux-ldr -l /tftpboot/u-boot.ldr.uart /dev/ttyS0 && kermit -l /dev /ttyS0 -b 57600 -C connect</code> (前提是串口正常， 设置正确。如果采 用到是USB转串口，么/dev/ttyS0 应改为/dev/ttyUSB0。 （4）烧写完成后， 打开minicom，将硬件开调回到原来位置设置IP：<code> set ipaddr 10.100.4.50 set serverip 10.100.4.174 运行命令run update</code> === 3.通过GDB烧写 === 通过GDB烧写u-boot需要先 编译u-boot （1）通过git clone 命令拷 贝u-boot的code。可以进入b lackfin.uclinux.org网页进行相应 下载。第三步已 经交代过了下载方 法。 （2）进入下载到u-boot录下面，编译u-boot （3）找到相应板子 型号的配置文件:ls include /configs/bf （4）编译u-boot。<code> make bf609-ezkit_config make clean make</code> （5）进入GDB：运行gdb，需要运行./bfin-gdbproxy bfin在/opt/uClinux/bfin-uclinux/bin/下面<code> cd /opt/uClinux/bfin-uclinux/bin/ sudo ./bfin-gdbproxy bfin</code> （6）转换到u-boot目录，进入gdb<code> bfin-uclinux-gdb u-boot <gdb> targer remote :2000 <gdb>load arc/blackfin/cpu/init.elf <gdb> c <gdb>load <gdb>c</code> 打开minicom，看板子是boot起来，如果起来 ，然后运行run update === 6.脚本测试 === 打开minicom ，在板子正起来后，输入命：tftpboot uImage，把将要试的项目对于uImage下 载到 板子上，然后输入 命令boot，将板子boot起。 板子boot起来之后，看相应测试项目测试脚本，或者试log，进行相应的试工作。或者查网页 blackfin.uclinux.org |
|
From: grace <no...@do...> - 2015-05-12 06:37:39
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=%E5%AE%9E%E4 %B9%A0%E5%B7%A5%E4%BD%9C%E8%AF%B4%E6%98%8E%E6%96%87%E6%A1%A3 Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=%E5%AE%9E%E4 %B9%A0%E5%B7%A5%E4%BD%9C%E8%AF%B4%E6%98%8E%E6%96%87%E6%A1%A3&rev=1431411 872 Edit Summary: update @@ -3,6 +3,6 @@ - 进入安装界面，择install Ubuntu选项，进行 下一步。 - - 进入设置页面，除原有系统，进新的磁盘分区。行磁盘分区时，意三个分区必须：1.swap ;2./(root目录);3./home(用主目录)。设置开密码，比如,可设器的开机密码为test采用英文版系统默认选择就可以 + - 进入设置页面，除原有系统，进新的磁盘分区。行磁盘分区时，意三个分区必须：1.swap ;2./(root目录);3./home(用主目录)。采用英版系统，默认选就可以。 - 安装完成后，重电脑 ===== 第二步：对电 脑进行相应配置 === == 参见网页：blackfin.uclinux.org.择The Linux kernel/testing，到网页 最低部，选择How to set up ubuntu 12.04 on regression PC，进入相应配置文档。\\ @@ -14,19 +14,17 @@ ===== 第三步：建立wo rkspace以及相应Code的下载 ===== 建立workspace，输入命令 ：mkdir workspace - 所需要到的code都可通过blackfin.uclinux.org这个主进入sourceforge.net网页进下载。或者从内资料库下载：10.99.29.20器上。\\ + 所需要到的code都可通过blackfin.uclinux.org这个主进入sourceforge.net网页进下载。\\ 通过git clone 命令。\\ 下面列举两个例子 ：\\ - 下载u-boot ：<code> git clone git://nwd2cvs1.corp.analog.com/git/unreleased/u-boot.git u-boo t - 或者从内部机器上 下载 - git clone git://10.99.29.20/git/unreleased/u-boot.git u-boot</code> + - 下载buildroot:<code> git clone git://nwd2cvs1.corp.analog.com/git/unreleased/buildroot.git - 或者从内部机器上 下载 - git clone git://10.99.29.20/git/unreleased/buildroot.git</code> + 当使用git clone下来到工 程中带有submodule时，初 始的时候，submodule的内 容并不会自动下载 ，需要 在buildroot目录下执行下 面命令：<code> git submodule init git submodule update</code> |
|
From: grace <no...@do...> - 2015-04-01 03:17:46
|
New Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test Old Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test&rev=1427858129 Edit Summary: [Manual test] @@ -17,12 +17,13 @@ Before running the following specific cases from testsuites, please adj ust your param setting according to your machine environment. - common/kernel_config.exp: set src_root /your/kernel/source/code/directly + common/kernel_config.exp: <code> + set src_root /your/kernel/source/code/directly </code> - If your are running the case on regression machine, please remember do: - export BOARD_CONFIG=BOARD_CONFIG(for example BF537-STAMP-XXX) + If your are running the case on regression machine, please remember do: <code> + export BOARD_CONFIG=BOARD_CONFIG(for example BF537-STAMP-XXX) </code> **AD1836 audio driver** *The test will need to be done on the boards of BF533-STAMP,BF537-STA MP and BF609-EZKIT. *First refer to "Device driver test"---1.Audio driver test over SPORT (AD1836) in https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:t esting. |
|
From: grace <no...@do...> - 2015-04-01 03:15:36
|
New Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test Old Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test&rev=1427857875 Edit Summary: [Manual test] @@ -14,13 +14,14 @@ *The following commands are also useful:ssh -l test XX.XX.XX.XX;scp test@xx.xx.xx.xx:/files ~/;scp ~/files test@xx.xx.xx.xx:~/. If you want to reference the previous release logs,please download the files in 10.99 .22.20/home/test/release/. *You can also refer to the wiki of https://docs.blackfin.uclinux.org /doku.php?id=linux-kernel:testing. All the build uImage scripts and test scripes are in the file of "testsuites". ======Manual test====== - Before running the following specific cases from testsuites, please adju st your param setting according to your machine environment. + Before running the following specific cases from testsuites, please adj ust your param setting according to your machine environment. + common/kernel_config.exp: set src_root /your/kernel/source/code/directly - If your are running the case on regression machine, please remember do: + If your are running the case on regression machine, please remember do: export BOARD_CONFIG=BOARD_CONFIG(for example BF537-STAMP-XXX) **AD1836 audio driver** *The test will need to be done on the boards of BF533-STAMP,BF537-STA MP and BF609-EZKIT. |
|
From: grace <no...@do...> - 2015-04-01 03:12:39
|
New Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test Old Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test&rev=1402543434 Edit Summary: [How to build workspace] @@ -1,12 +1,13 @@ ======How to build workspace====== *Make the dir: eg:~/workspace/src/kernel *Get the files: <code> git clone git://10.99.22.20/git/buildroot kernel + git submodule init git config submodule.testsuites.url git://10.99.22.20/buildroot_tes t git config submodule.linux/linux-kernel.url git://10.99.22.20/linux -kernel git submodule update</code> - *Checkout the right branch:using "git tag -l"to show all branch,"git checkout -b XXX XXX"to change branch, "git branch"to check out the head, and "git pull" to updata the code.The commands of "checkout ." and "git st atus" is also useful. + *Checkout the right branch:using "git tag -l"to show all branch,"git checkout -b XXX XXX"to create branch, "git branch"to show the current br anch,and "git pull" to update the code.The commands of "git checkout ." an d "git status" is also useful. ======How to setup toolchain====== *To build the dir /opt/uClinux/,and chmod 777 uClinux *Borm 10.99.29.40 to get the right version to uClinux *Before make the uImage ,you should export PATH=/opt/uClinux/bfin- uclinux/bin:/opt/uClinux/bfin-elf/bin:/opt/uClinux/bfin-linux-uclibc/bin:$ PATH |
|
From: grace <no...@do...> - 2015-04-01 03:11:23
|
New Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test Old Revision: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel: manual_test&rev=1427857272 Edit Summary: [Manual test] @@ -13,8 +13,16 @@ *Before make the uImage ,you should export PATH=/opt/uClinux/bfin- uclinux/bin:/opt/uClinux/bfin-elf/bin:/opt/uClinux/bfin-linux-uclibc/bin:$ PATH *The following commands are also useful:ssh -l test XX.XX.XX.XX;scp test@xx.xx.xx.xx:/files ~/;scp ~/files test@xx.xx.xx.xx:~/. If you want to reference the previous release logs,please download the files in 10.99 .22.20/home/test/release/. *You can also refer to the wiki of https://docs.blackfin.uclinux.org /doku.php?id=linux-kernel:testing. All the build uImage scripts and test scripes are in the file of "testsuites". ======Manual test====== + + Before running the following specific cases from testsuites, please adju st your param setting according to your machine environment. + + common/kernel_config.exp: set src_root /your/kernel/source/code/directly + + If your are running the case on regression machine, please remember do: + export BOARD_CONFIG=BOARD_CONFIG(for example BF537-STAMP-XXX) + **AD1836 audio driver** *The test will need to be done on the boards of BF533-STAMP,BF537-STA MP and BF609-EZKIT. *First refer to "Device driver test"---1.Audio driver test over SPORT (AD1836) in https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:t esting. *Need a module of ad1836 http://docs.blackfin.uclinux.org/doku.php?i d=hw:cards:ad1836a.(BF609-EZKIT have a special extension board).The modu le should be connect to the SPORT0 on the board .Need two audio cables, co nnect the board's audio input to PC's audio output and the board's audio o utput to PC's audio input.Using PC to provide sounds to board by palying a file of audiotest.mp3.<code> |
38 messages has been excluded from this view by a project administrator.