L27.INC1.9.0 OMAP4 Froyo ES2 Release Notes

= Introduction = This software release has been developed and verified in the following software and hardware environment.

Please note Toolchain is upgraded since L27.7.0 release

OS Kernel: Linux® 2.6.35 Android:  Froyo public project Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux Reference hardware platform: TI OMAP4 ES2.1 EMU Blaze Build Host OS: Ubuntu

=Tools & Dependency packages=

Pre-requisite packages for build Android Filesystem (Note this is with reference to uBuntu 8.04)

If you are behind firewall, you will have to set-up firewall using the instructions in Support Tools

For higher versions of U-buntu please refer to Host PC COnfiguration

The following commands will install the correct packages to your server:

sudo apt-get install git-core flex bison gperf libesd0-dev libwxgtk2.6-dev zlib1g-dev build-essential libstdc++5 tofrodos sudo apt-get install x-dev sudo apt-get install libx11-dev sudo apt-get install libncurses5-dev sudo apt-get install sun-java5-jdk

If you do not have sudo rights to your machine, contact your System Administrator for assistance. Google has issued that “sun-java6-jdk” has become unsupported: “because of incompatibilities with @Override” To uninstall “sun-java6-jdk” please type:

sudo apt-get remove sun-java6-jdk

“Intrepid (8.10) users may need a newer version of libreadline:

sudo apt-get install lib32readline5-dev”

Tool Chain for building Kernel and Drivers

The Kernel and Driver sources are built using Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux version.

This tool chain can be obtained from

=Downloading Release Software= Android Filesystem Sources

you can get the Android source for this release by doing: git clone git://git.omapzoom.org/platform/omapmanifest.git cd omapmanifest git reset --hard RLS27.9.0_Froyo_RC0 export MANIFEST=`pwd` cd export YOUR_PATH=`pwd` mkdir -p 27.9.0/mydroid; cd 27.9.0/mydroid export MYDROID=`pwd` repo init –u $MANIFEST repo sync

Kernel & Driver Sources

To clone kernel source from scratch do: cd ; export YOUR_PATH=`pwd` mkdir kernel git clone git://git.omapzoom.org/kernel/omap.git kernel/android-2.6.35 cd kernel/android-2.6.35 git checkout ff1a51568a988c03005f262cc026b2abdb2de044 If you already have kernel source cloned then just update it: cd $YOUR_PATH/kernel/android-2.6.35 git fetch origin git checkout ff1a51568a988c03005f262cc026b2abdb2de044

U-Boot Sources cd ; export YOUR_PATH=`pwd` git clone git://git.omapzoom.org/repo/u-boot.git u-boot cd u-boot git checkout 025fefdbfb6234fe986ac59e7cde5e838981d00a

X-loader Sources cd ; export YOUR_PATH=`pwd` git clone git://git.omapzoom.org/repo/x-loader.git x-loader cd x-loader git checkout c07208b045182c61c204ce445f936799b57bd174

=Release Content=

This release has the below content - Kernel and Drivers tested with OMAP4 ES2.1 EMU Blaze platform and verified with Froyo UI - A9 source code for accelerating Video

The release has been verified with OMAP4 SGX hardware Graphics Accelerator libraries and accelerated Video codecs Please contact TI customer representative to gain access TI proprietary packages

=Build Instructions=

Setting up build environment
From your work directory (where your 27.9.0 folder resides): export YOUR_PATH=`pwd` export PATH=$PATH:/arm-2010q1/bin export MYDROID=${YOUR_PATH}/27.9.0/mydroid mkdir $MYDROID/logs export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun export CROSS_COMPILE=arm-none-linux-gnueabi- export PATH=${YOUR_PATH}/u-boot/tools:${PATH}

Building U-BOOT
cd $YOUR_PATH/u-boot make distclean make ARCH=arm omap4430sdp_config make 2>&1 |tee $MYDROID/logs/u-boot_make.out

Building X-LOADER
cd $YOUR_PATH/x-loader make distclean make ARCH=arm omap4430sdp_config make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out

For previous board revisions with OMAP4 ES1 600MHz, the configuration should be changed as described below: cd $YOUR_PATH/x-loader make distclean make ARCH=arm omap4430sdp_MPU_600MHz_config make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out

Signing X-LOADER for EMU devices

The tool for signing x-loader is provided on TI's package. Please contact TI customer representative to get access to this tool. cd $YOUR_PATH/27.9.0/mshield-dk cp -f $YOUR_PATH/x-loader/x-load.bin. ./generate_MLO x-load.bin

Building Kernel
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable: cd $YOUR_PATH/kernel/android-2.6.35 make ARCH=arm distclean make ARCH=arm android_4430_defconfig make ARCH=arm uImage 2>&1 |tee $MYDROID/logs/kernel_make.out

Building Kernel modules
cd $YOUR_PATH/kernel/android-2.6.35 make ARCH=arm modules 2>&1 |tee $MYDROID/logs/kernel_modules.out

Building WLAN driver
export HOST_PLATFORM=sdc4430 export KERNEL_DIR=$YOUR_PATH/kernel/android-2.6.35 cd $MYDROID/hardware/ti/wlan/wl1283/platforms/os/linux make ARCH=arm

Building Android Filesystem (AFS) with TI Codecs enabled
on step below use the number of cores you have available; i.e. -j4 or -j12: cd $MYDROID cp -Rfp device/ti/blaze/buildspec.mk.default buildspec.mk make clean (required for rebuild only) make -j4 2>&1 |tee $MYDROID/logs/android_make.out

Building AFS with Android Codecs
This release was not verified with Android codecs. Camera based applications need TI proprietary drivers. Please contact TI customer representative to get access to proprietary sources

Preparing Android binaries
The following binaries are required by the Blaze® board. This step will prepare a directory, called myfs, containing all necessary Android files that you must include within your SD card. cd $YOUR_PATH mkdir myfs cd myfs cp -Rfp $YOUR_PATH/kernel/android-2.6.35/drivers/staging/ti-st/*.ko $MYDROID/out/target/product/blaze/root cp -Rfp $MYDROID/out/target/product/blaze/root/*. cp -Rfp $MYDROID/out/target/product/blaze/system/. cp -Rfp $MYDROID/out/target/product/blaze/data/. cp -Rfp $MYDROID/device/ti/blaze/init.omap4sdp.rc init.rc

Changing default display resolution on Android

Default LCD density is now set to 240 (was 160 previously by default). If you want to come back to the previous setting to make Android UI look smaller (smaller icons, etc...), comment the following line in system/build.prop
 * 1) ro.sf.lcd_density=240

Preparing eMMC images
If you wish to boot entirely from eMMC, you will need to modify init.rc file to mount eMMC partitions on your system and create the eMMC partition images:

cd $MYDROID cp $YOUR_PATH/myfs/init.rc out/target/product/blaze/root sed -i -e '/system ro remount/a\ mount ext3 /dev/block/mmcblk0p1 /system\ mount ext3 /dev/block/mmcblk0p1 /system ro remount' \ -e '/data nosuid nodev/a\ mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev' \ -e '/cache nosuid nodev/a\ mount ext3 /dev/block/mmcblk0p3 /cache nosuid nodev' out/target/product/blaze/root/init.rc

Now you need to rebuild your Android filesystem; but before you need to erase ramdisk.img file from your 'out' directory:

cd $MYDROID rm -f out/target/product/blaze/ramdisk.img make -j4

This build should not take too much time and will re-generate a new ramdisk.img file with the modified init.rc file in it.

After build is done you need to copy the new ramdisk.img file to a new directory where you will store all eMMC-related files for easy location:

cd $YOUR_PATH mkdir omap4_emmc_files cp -f $MYDROID/out/target/product/blaze/ramdisk.img omap4_emmc_files cp -f $MYDROID/out/host/linux-x86/bin/fastboot omap4_emmc_files cp -f $MYDROID/device/ti/blaze/mbr.bin omap4_emmc_files cp -f u-boot/tools/mkimage omap4_emmc_files cp -f u-boot/u-boot.bin omap4_emmc_files cp -f x-loader/MLO omap4_emmc_files cp -f kernel/android-2.6.35/arch/arm/boot/zImage omap4_emmc_files

Now from this new directory we will create the eMMC images which will be flashed using fastboot protocol (described later). First create uMulti-2 image using kernel image we copied previously:

cd $YOUR_PATH/omap4_emmc_files ./mkimage -A arm -O linux -T multi -C none -a 0x80008000 -e 0x80008000 -n 'Linux-2.6.35' -d ./zImage:./ramdisk.img uMulti-2

Then create system image:

cd $YOUR_PATH/omap4_emmc_files dd if=/dev/zero of=./system.img bs=1048510 count=200 mkfs.ext3 -F system.img -L system mkdir tmp sudo mount -o loop system.img tmp cp -prf $YOUR_PATH/myfs/system/* tmp sudo umount tmp

In a similar fashion create userdata and cache partitions:

cd $YOUR_PATH/omap4_emmc_files dd if=/dev/zero of=./data.img bs=1048510 count=150 mkfs.ext3 -F data.img -L data sudo mount -o loop data.img tmp cp -prf $YOUR_PATH/myfs/data/* tmp sudo umount tmp dd if=/dev/zero of=./cache.img bs=1048510 count=50 mkfs.ext3 -F cache.img -L cache

And finally the environment file with the bootargs and bootcmd information:

cd $YOUR_PATH/omap4_emmc_files echo "bootdelay=5 bootargs=console=ttyO2,115200n8 rootdelay=2 mem=458M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M" bootcmd=mmcinit 1;mmc 1 read 0x1000 0x81000000 0x500000;bootm 81000000 loadaddr=81000000" > env.txt

= Booting Kernel and Android File System from SD card = Formatting SD Card

You will need to format your SD for the Linux file system. Connect your SD memory card reader with memory card inserted to a USB port on your Linux Ubuntu PC. You must login as Super User.

$ su $ fdisk -l

Match the device to the size of your memory card. Look for the /dev/*** device which matches the memory card in the card reader. Use the matching device’s letter prefix in the next command. For example if the device for memory card reader card example was: /dev/sdb1, then use only /dev/sdb in the fdisk command.

Take note of the size in bytes of your SD Card. You will need this to calculate the number of cylinders in a future step.

$ fdisk /dev/sdb (replace sdb with the letter prefix for your device)

(Delete all partitions on the card if they exist) Command (m for help): d Partition number (1-4): 1 Command (m for help): d Selected partition 2

Command (m for help): x

(Change the number of heads, sectors and cylinders on the device) Expert command (m for help): h Number of heads (1-256, default 255): 255 Expert command (m for help): s Number of sectors (1-63, default 63): 63 Expert command (m for help): c Number of cylinders (1-1048576, default 248): 

(Now return to the main menu) Expert command (m for help): r

(Create the first partition) Command (m for help): n Command action e  extended p  primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-248, default 1): 1 Last cylinder or +size or +sizeM or +sizeK (1-248, default 248): +64M

If you plan to use this SD card partition for storing media your can use +1024M assuming a 2+ GB SD card.

(Create the second partition) Command (m for help): n Command action e  extended p  primary partition (1-4) p Partition number (1-4): 2 First cylinder (10-248, default 10): 10 Last cylinder or +size or +sizeM or +sizeK (124-248, default 248): 

(Change the first partition to at FAT32 partition) Command (m for help): t Partition number (1-4): 1 Hex code (type L to list codes): c Changed system type of partition 1 to c (W95 FAT32 (LBA))

(Toggle the bootable flag for partition 1) Command (m for help): a Partition number (1-4): 1

(Print the partition table to confirm your settings) Command (m for help): p

(Sample Output – your output may differ depending on your SD card’s size and brand) Disk /dev/sdb: 2041 MB, 2041577472 bytes 255 heads, 63 sectors/track, 248 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000

Device Boot     Start         End      Blocks   Id  System /dev/sdb1  *           1         9        72261     c  W95 FAT32 (LBA) /dev/sdb2             10       248     1919767+    83  Linux

(Write your changes to the SD Card) Command (m for help): w

(You will see the following output) The partition table has been altered!

Calling ioctl to re-read partition table.

WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information. Syncing disks.

Format your partitions typing the following commands (logged as root@ubuntu-box): $ mkfs.vfat -F 32 -n boot /dev/ $ mkfs.ext3 -L android_fs /dev/

There is a shell script that all calculations above automatically; to get it do: $ wget http://cgit.openembedded.org/cgit.cgi/openembedded/plain/contrib/angstrom/omap3-mkcard.sh

Add execution permission: $ chmod +x omap3-mkcard.sh

And you are ready to use it by just typing: $sudo ./omap3-mkcard.sh 

Copying Binaries onto SD Card

Now type the following to mount your SD Card on your Linux box (logged as root@ubuntu-box): $ mkdir /tmp/mmc1 $ mkdir /tmp/mmc2 $ mount /dev/ /tmp/mmc1 $ mount /dev/ /tmp/mmc2

Load the appropriate software to the SD Card (logged as root@ubuntu-box): $ cp $YOUR_PATH/x-loader/MLO /tmp/mmc1  (if you are using EMU or HS device, plese copy signed MLO instead) $ cp $YOUR_PATH/u-boot/u-boot.bin /tmp/mmc1 $ cp $YOUR_PATH/kernel/android-2.6.35/arch/arm/boot/uImage /tmp/mmc1 $ cp -Rfp $YOUR_PATH/27.9.0/myfs/* /tmp/mmc2 $ chmod –R 777 /tmp/mmc2/* $ umount /tmp/mmc1 $ umount /tmp/mmc2

Booting

Insert your SD card (with u-boot, x-loader and uImage loaded in FAT partition and ) into Blaze SD/MMC card slot, then plug the Blaze mini USB port to your PC and open a serial terminal (baudrate:115200, no parity, 8 bits). Power your board up and in your terminal window you should be able to see the ‘New’ u-boot prompt:

“OMAP44XX SDP #”

In your serial terminal define the following: setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk1p2 rw rootdelay=2 mem=458M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M"'

now type this: mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000

Right after this your Blaze should start booting using the kernel image and loading the Android filesystem from your SD

= Booting Kernel and Android File System from eMMC = Formatting eMMC

Starting on L27.7.2 release onwards the eMMC partition table changed and the flashing procedure now uses fastboot protocol. Please read carefully the following instructions

If your are going to use eMMC for the first time, you need to create the appropriate partition table and create a filesystem (format) for each partition. For this you need to load u-boot from your SD card; for this you need to change your SYS_BOOT configuration (S2-[1:3] OFF, ON, OFF). Use the u-boot.bin and the x-loader you built for this release; copy them to your "boot" partition of your SD card, turn your Blaze on and press any key on your serial terminal to stop the auto-boot process.

Now type from you serial terminal (on the u-boot prompt) 'fastboot' and board should be waiting for any fastboot command. You should see something like this: [Please note this is an older snapshot (so rev numbers you see might be different as compared to below)]

OMAP 4 PPA tactical release 0.8.1

Texas Instruments X-Loader 1.41 (Oct 20 2010 - 12:03:47) Starting OS Bootloader from MMC/SD1 ...

U-Boot 1.1.4-g0e685295-dirty (Oct 14 2010 - 17:09:14)

Load address: 0x80e80000 DRAM: 1024 MB Flash:  0 kB In:    serial Out:  serial Err:  serial Net:  KS8851SNL Hit any key to stop autoboot: 0 OMAP44XX SDP # fastboot Disconnect USB cable to finish fastboot..

Now connect the Blaze micro USB port to your Linux box and go to where the eMMC files are. The first fastboot command will create the Master Boot Record that has the partition table along with other boot information on eMMC and the others will flash the files onto the corresponding eMMC partition:

cd $YOUR_PATH/omap4_emmc_files ./fastboot flash mbr mbr.bin ./fastboot flash xloader ./MLO ./fastboot flash bootloader ./u-boot.bin ./fastboot flash environment ./env.txt ./fastboot flash kernel ./uMulti-2 ./fastboot flash system ./system.img ./fastboot flash userdata ./data.img ./fastboot flash cache ./cache.img

Once MBR is created you no longer need to flash mbr anymore ; only when partition table changes is when we would need to flash mbr again but don't expect changes in the partition table so soon. You can now switch to boot from eMMC.

IMPORTANT: DO NOT ERASE mbr, system, userdata OR cache PARTITIONS. If you want to update these partitions with a new set of eMMC images just use fastboot "flash" commands as described above. For the other partitions you can safely use fastboot "erase" command before updating them:

./fastboot erase xloader ./fastboot erase bootloader ./fastboot erase environment ./fastboot erase kernel

Booting

Insert your SD card into Blaze SD/MMC card slot (now only required to store MM files), then plug the Blaze mini USB port to your PC and open a serial terminal (baudrate:115200, no parity, 8 bits). Disconnect the micro USB cable if connected to Blaze, change your SYS_BOOT configuration to boot from eMMC (S2-[1:3] ON, ON, ON) and power your board up and in your terminal window you should be able to see the auto-boot process start in 5 seconds: * This SYS_BOOT configuration must be kept even when you want to update eMMC binaries set, just keep in mind you must NOT flash mbr.bin file again.

OMAP 4 PPA tactical release 0.8.3

Texas Instruments X-Loader 1.41 (Oct 20 2010 - 12:03:47) Starting OS Bootloader from EMMC ...

U-Boot 1.1.4-g8024422c-dirty (Oct 20 2010 - 12:03:36)

Load address: 0x80e80000 DRAM: 1024 MB Flash:  0 kB In:    serial Out:  serial Err:  serial Net:  KS8851SNL Hit any key to stop autoboot: 5

If you want to verify that your bootargs and bootcmd were flashed correctly as described in env.txt file, then press any key to stop the auto-boot process and type 'print': OMAP44XX SDP # print bootdelay=5 bootargs=console=ttyO2,115200n8 rootdelay=2 mem=458M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M" bootcmd=mmcinit 1;mmc 1 read 0x1000 0x81000000 0x500000;bootm 81000000 loadaddr=81000000 stdin=serial stdout=serial stderr=serial ethact=KS8851SNL

Environment size: 223/131068 bytes

To continue booting just type 'boot' and the boot process will start.

=Bootargs= Note that parameter mem=458M@0x80000000 mem=512M@0xA0000000 should be used in the bootargs

L27.9.0 Bootargs for SD card boot

setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk1p2 rw rootdelay=2 mem=458M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M"' setenv bootcmd 'mmcinit 0;fatload mmc 0 0x80000000 uImage; bootm 0x80000000' saveenv boot

eMMC bootargs given in env.txt

bootdelay=5 bootargs=console=ttyO2,115200n8 rootdelay=2 mem=458M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M bootcmd=mmcinit 1;mmc 1 read 0x1000 0x81000000 0x500000;bootm 81000000 loadaddr=81000000

Right after this your Blaze should start booting kernel image and loading the Android filesystem both from Blaze eMMC

= BIOS SysLink =

The following steps will help you to set up the BIOS SysLink tools and compilers as well as how to build a BIOS SysLink sample in a Linux Ubuntu Host.

BIOS SysLink sources
Get the latest code: git clone git://git.omapzoom.org/platform/hardware/ti/bios-syslink.git

The above command will clone the BIOS SysLink source code in a directory called bios-syslink/. cd bios-syslink git checkout c93297fe556b6b443eb28804d1ca5813fcca06ad

Accordingly with the Ducati Release 1.20

BIOS SysLink tools
The following tool versions are taken from he Ducati Release 1.20 as mentioned above.

Download and install the following tools:

Public BIOS version 6.31.00.18 for Linux

bios

Public XDC version 3.20.05.76 for Linux

xdc

Public CGT C6000 version 7.1.0B2 for Linux

cgtc6x

CGT TMS470 version 4.6.1 for Linux

armcgt

Setting up Build environment
The following environment variables are set assuming the tools installation directory is dsp-tc/ and that you will use the git clone directory as working directory (bios-syslink/).

export PATH=$PATH:/dsp-tc/xdctools_3_20_05_76 export TMS470CGTOOLPATH=/dsp-tc/cgtarm-4.6.1 export C6000CGTOOLPATH=/dsp-tc/cgt6x-7.1.0B2/ export XDCPATH="~/bios-syslink/packages;/dsp-tc/bios_6_31_00_18/packages"

Build BIOS SysLink Notify Sample
Type on the host machine: cd bios-syslink/packages ./build.sh

The build.sh script is invoking the xdc compiler. As many of the makefiles, the operrations this build.sh script perform are based on rules; the script released along with the BIOS SysLink sources has three rules:

Clean. Build the libraries. Build the samples.

Let’s take a look to the third rule:

xdc -PR ./ti/omap/samples/notify

The above command means that only the Notify Sample will be built.

In case you are working in a multicore environment the xdc allows the usage of multiple cores for parallel building: xdc --jobs=2 -PR ./ti/omap/samples/notify

Where --jobs=2 indicates the xdc that you are in dual core environment.

Copying the BIOS SysLink binaries to the Android Filesystem
The output files of the build process are located at the following directories. Yo have to copy the .xem3 files as well as the .xe64T file to your Android Filesystem: bios-syslink\packages\ti\omap\samples\notify\ti_omap_platform_core0\whole_program_debug Notify_MPUSYS_reroute_Test_Core0.xem3 Notify_MPUSYS_Test_Core0.xem3

bios-syslink\packages\ti\omap\samples\notify\ti_omap_platform_core1\whole_program_debug Notify_MPUAPP_reroute_Test_Core1.xem3

bios-syslink\packages\ti\omap\samples\notify\ti_omap_platform_dsp\whole_program_debug Notify_Test_Dsp.xe64T

The BIOS SysLink Notify images are also located in the Android Filesystem by default at: cd /data /data # ls Notify_MPUAPP_reroute_Test_Core1.xem3 Notify_MPUSYS_Test_Core0.xem3 Notify_MPUSYS_reroute_Test_Core0.xem3

Running the Notify Sample
When the Android filesystem boots a Multimedia baseimage is loaded, in order to run the Notify sample this baseimage must be unloaded.

For unload this baseimage the syslink daemon must be killed, on your serial console:

. . . 1448 0 /system/bin/syslink_daemon.out /data/Notify_MPUSYS_rerout . . . omap_hwmod: ipu: failed to reset in 10000 usec omap-iommu omap-iommu.0: ducati: version 2.1 Wakeup SYSM3 Wakeup APPM3 messageq_detach : status [0x0] nameserver_remotenotify_detach : status [0x0] ipu_pm_detach : status [0x0] notify_detach : status [0x0] messageq_detach : status [0x0] nameserver_remotenotify_detach : status [0x0] ipu_pm_detach : status [0x0] notify_detach : status [0x0] . ..
 * ps
 * 1) kill 1448
 * 2) omap mailbox rev 0.0

Finally Run the sample:

/data # notifyping.out 1
 * 1) cd /data

NotifyPing Sample
Enteredomap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla , count 1 NotifyPing_staromap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, n ame ducati-proc0, count 1 omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1 , count 1 . . . omap_hwmod: ipu: failed to reset in 10000 usec omap-iommu omap-iommu.0: ducati: version 2.1 proc4430_attach num_mem_entries = 6 proc_mgr_attach:proc_mgr_handle->num_mem_entries = 6 Ipc_setup successful!ProcMgr_attach status: [0x97d2000] After attach: ProcMgr_getState state [0x1] Testing SysM3 only! Image = ./Notify_MPUSYS_Test_Core0.xem3

Programming proc 2 MMU using linear address Programming SysM3 memory regions

=
============================ VA = [0xa0000000] of size [0x100000] at PA = [0x9cf00000] VA = [0x0] of size [0x1000000] at PA = [0x9d000000] VA = [0x80000000] of size [0x1000000] at PA = [0x9e000000] VA = [0x81000000] of size [0x1000000] at PA = [0x9f000000] Programming SysM3 L4 peripherals

=
============================ PA [0x60000000] VA [0x60000000] size [0x10000000] PA [0x70000000] VA [0x70000000] size [0x8000000] PA [0x78000000] VA [0x78000000] size [0x8000000] PA [0x4a000000] VA [0xaa000000] size [0x1000000] PA [0x48000000] VA [0xa8000000] size [0x1000000] PA [0x5a000000] VA [0xba000000] size [0x1000000] PA [0x5b000000] VA [0xbb000000] size [0x1000000] PA [0x54000000] VA [0xb4000000] size [0x1000000] ProcMgr_load (Sy_platform_read_slave_memory successful! status = 0x0, proc_id = 2, addr = 0xc480, m_addr = 0xf3a0c480, size = 0x20sM3) successful! _platform_read_slave_memory successful! status = 0x0, proc_id = 2, addr = 0xc4a0 , m_addr = 0xf3a0c4a0, size = 0x30

_platform_write_slave_memory successful! status = 0x0, proc_id = 2, addr = 0xc48 0, m_addr = 0xf3a0c480, size = 0x20ProcMgrDrvUsr_io omap-remoteproc omap-remoteproc.1: omap_rproc_ioctl . ..

You can also do:

/data # notifyping.out 0
 * 1) cd /data

=Resources= Insert non-formatted text here  Insert non-formatted text here