Loading program from Code Composer 3.3 to Beagle Board

Sven · October 28, 2010, 7:31am

Hi,

I cannot load my .out file to the Beagle Board i am using.

I am using:
Code Composer 3.3
Beagle Board -xMA
Angstrom as OS on the Beagleboard
XDS510plus Emulator

I used the "Spectrum Digital USB510" configuration file from section
"DM3730 and DM3725" on website: http://processors.wiki.ti.com/index.php/OMAP_and_Sitara_CCS_support

I am able to connect to the Cortex processor and after that I can use
GELIVA2200 ->IVA22_startup to the release the DSP. Then I can connect
to the DSP. But when openening Code Composer and I want to load the
program to the DSP, the following message appears in the putput
cosole:

“Trouble Writing Memory Block at 0xfc00 on Page 0 of Length 0x200:
Error 0x00000002/-1190 Error during: Memory, The DTDMA memory request
is not serviced by the HW memory system. This could be caused by the
memory address specified does not exist in the specified memory/cache
level.“

A couple of things I still dont get:
Why are there distinct entries in the CCSTudio Parallel Debug manager
for ARM9 and CortexA, I thought there is only one Cortex-A9 processor?

And I am also not familiar with the usage of gel files.
The config file I am using automatically uses the gel files:
"omap3430_c64plus.gel" for the DSP and
"omap3430_arm9.gel" for the ARM processor

Is this right at all, because the BB is not a OMAP3430?

I hope anyone has an idea.

Thx and regards
Sven

Juha1 · October 28, 2010, 3:00pm

Did you configure the DSP MMU? It must be done from the ARM side.
Seems that the am-dm37x-cortexA.gel has menu IVA2200_MMU and menuitem ProgramMMU. I would try that.

You might want to look at the configuration so that DSP does not step on ARM’s toes, that is if you have something running there.
Look to me that the code maps 2MB at 0x80000000 to 0x80000000 on the DSP but I don’t have the datasheet on front of me so I cannot verify.

Juha

Mark_Lazarewicz · October 28, 2010, 4:21pm

BBPATH and BBFILES should point to what?

lazarman@kerndev:~/Amazon cloud build$ ./ec2build.sh build-image test
+ set -e
+ ANGSTROM_SCRIPT_ID=f593f1c023cd991535c748682ab21154c807385e
+ ANGSTROM_REPO_ID=24805033b1205acc35f8b4d75cc42f8b9c2a1b38
+ USE_EC2=yes
+ USE_PSTAGE=yes
+ HALT=no
+ AMI=ami-fd4aa494
+ ‘[’ -e /home/lazarman/ec2build-ami.sh ‘]’
++ date +%Y%m%d%H%M
+ DATE=201010271827
+ KEYPAIR=ec2build-keypair
+ KEYPAIR_FILE=/home/lazarman/secret/ec2build-keypair.txt
+ INSTANCES=/home/lazarman/ec2build-instances.txt
+ VOLUMES=/home/lazarman/ec2build-volumes.txt
+ MACH_TYPE=m1.xlarge
+ DOWNLOAD_EBS=vol-08374961
+ ANGSTROM_EBS=vol-24fa964d
+ DOWNLOAD_DIR=/home/lazarman/downloads
+ OEBB_DIR=/home/lazarman/angstrom-setup
+ SCRIPT_DIR=/home/lazarman/scripts
+ THIS_FILE=./ec2build.sh
+ INSTANCE=
+ MACH_NAME=
+ build-image test
+ IMAGE=test
+ setup-oe
+ ‘[’ ‘!’ -x /home/lazarman/angstrom-setup/oebb.sh ‘]’
+ pushd /home/lazarman/angstrom-setup
~/angstrom-setup ~/Amazon cloud build
+ git checkout f593f1c023cd991535c748682ab21154c807385e
M sources/bitbake
M sources/openembedded
HEAD is now at f593f1c… oebb.sh: fixed remote name
+ ‘[’ ‘!’ -d sources/openembedded/.git ‘]’
+ pushd sources/openembedded
~/angstrom-setup/sources/openembedded ~/angstrom-setup ~/Amazon cloud build
+ git remote add myrepo git://gitorious.org/~Jadon/angstrom/jadon-openembedded.git
remote myrepo already exists.
+ true
+ git remote update
Updating myrepo
Updating origin
remote: Counting objects: 212, done.
remote: Compressing objects: 100% (152/152), done.
remote: Total 158 (delta 108), reused 1 (delta 0)
Receiving objects: 100% (158/158), 20.89 KiB, done.
Resolving deltas: 100% (108/108), completed with 48 local objects.
From git://git.openembedded.org/openembedded
d79f536…ddffbe4 master → origin/master
d79f536…ddffbe4 org.openembedded.dev → origin/org.openembedded.dev
+ true
+ git checkout 24805033b1205acc35f8b4d75cc42f8b9c2a1b38
HEAD is now at 2480503… beagleboard-demo-image: don’t waste time building
+ popd
~/angstrom-setup ~/Amazon cloud build
+ popd
~/Amazon cloud build
+ oebb bitbake -k beagleboard-test-image
+ cd /home/lazarman/angstrom-setup
+ ./oebb.sh bitbake -k beagleboard-test-image
Using ~/.oe/environment to setup needed variables. It is recommended to do ‘. ~/.oe/environment’ and run ‘bitbake something’ without using ./oebb.sh as wrapper
Executing: bitbake -k beagleboard-test-image
ERROR: no recipe files to build, check your BBPATH and BBFILES?
NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it to increase performance.
ERROR: no recipe files to build, check your BBPATH and BBFILES?

|

Sven · November 1, 2010, 12:11pm

I tried to use the option ProgramMMU, but nothing happens then, not
even an output to the console. If I try to laod the outfile fterwards,
the same "Trouble Writing Memory Block.." problem occurs.

@Mark: I dont get what you are trying to explain to me, what exactly
is the printout you have written?

Mark_Lazarewicz · November 1, 2010, 7:54pm

What

— On Mon, 11/1/10, Sven Hartlieb sven.hartlieb@googlemail.com wrote:

> From: Sven Hartlieb sven.hartlieb@googlemail.com
> Subject: [beagleboard] Re: Angstrom ERROR: no recipe files to build, check your BBPATH and BBFILES?
> To: “Beagle Board” beagleboard@googlegroups.com
> Date: Monday, November 1, 2010, 7:11 AM
>
> I tried to use the option ProgramMMU, but nothing happens then, not
> even an output to the console. If I try to laod the outfile fterwards,
> the same “Trouble Writing Memory Block…” problem occurs.
>
> @Mark: I dont get what you are trying to explain to me, what exactly
> is the printout you have written?
>
> On 28 Okt., 17:21, Mark Lazarewicz <lazar…@yahoo.com> wrote:
> > BBPATH and BBFILES should point to what?
> >
> > lazarman@kerndev:~/Amazon cloud build$ ./ec2build.sh build-image test
> > + set -e
> > + ANGSTROM_SCRIPT_ID=f593f1c023cd991535c748682ab21154c807385e
> > + ANGSTROM_REPO_ID=24805033b1205acc35f8b4d75cc42f8b9c2a1b38
> > + USE_EC2=yes
> > + USE_PSTAGE=yes
> > + HALT=no
> > + AMI=ami-fd4aa494
> > + ‘[’ -e /home/lazarman/ec2build-ami.sh ‘]’
> > ++ date +%Y%m%d%H%M
> > + DATE=201010271827
> > + KEYPAIR=ec2build-keypair
> > + KEYPAIR_FILE=/home/lazarman/secret/ec2build-keypair.txt
> > + INSTANCES=/home/lazarman/ec2build-instances.txt
> > + VOLUMES=/home/lazarman/ec2build-volumes.txt
> > + MACH_TYPE=m1.xlarge
> > + DOWNLOAD_EBS=vol-08374961
> > + ANGSTROM_EBS=vol-24fa964d
> > + DOWNLOAD_DIR=/home/lazarman/downloads
> > + OEBB_DIR=/home/lazarman/angstrom-setup
> > + SCRIPT_DIR=/home/lazarman/scripts
> > + THIS_FILE=./ec2build.sh
> > + INSTANCE=
> > + MACH_NAME=
> > + build-image test
> > + IMAGE=test
> > + setup-oe
> > + ‘[’ ‘!’ -x /home/lazarman/angstrom-setup/oebb.sh ‘]’
> > + pushd /home/lazarman/angstrom-setup
> > ~/angstrom-setup ~/Amazon cloud build
> > + git checkout f593f1c023cd991535c748682ab21154c807385e
> > M sources/bitbake
> > M sources/openembedded
> > HEAD is now at f593f1c… oebb.sh: fixed remote name
> > + ‘[’ ‘!’ -d sources/openembedded/.git ‘]’
> > + pushd sources/openembedded
> > ~/angstrom-setup/sources/openembedded ~/angstrom-setup ~/Amazon cloud build
> > + git remote add myrepo git://gitorious.org/~Jadon/angstrom/jadon-openembedded.git
> > remote myrepo already exists.
> > + true
> > + git remote update
> > Updating myrepo
> > Updating origin
> > remote: Counting objects: 212, done.
> > remote: Compressing objects: 100% (152/152), done.
> > remote: Total 158 (delta 108), reused 1 (delta 0)
> > Receiving objects: 100% (158/158), 20.89 KiB, done.
> > Resolving deltas: 100% (108/108), completed with 48 local objects.
> > From git://git.openembedded.org/openembedded
> > d79f536…ddffbe4 master → origin/master
> > d79f536…ddffbe4 org.openembedded.dev → origin/org.openembedded.dev
> > + true
> > + git checkout 24805033b1205acc35f8b4d75cc42f8b9c2a1b38
> > HEAD is now at 2480503… beagleboard-demo-image: don’t waste time building
> > + popd
> > ~/angstrom-setup ~/Amazon cloud build
> > + popd
> > ~/Amazon cloud build
> > + oebb bitbake -k beagleboard-test-image
> > + cd /home/lazarman/angstrom-setup
> > + ./oebb.sh bitbake -k beagleboard-test-image
> > Using ~/.oe/environment to setup needed variables. It is recommended to do ‘. ~/.oe/environment’ and run ‘bitbake something’ without using ./oebb.sh as wrapper
> > Executing: bitbake -k beagleboard-test-image
> > ERROR: no recipe files to build, check your BBPATH and BBFILES?
> > NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it to increase performance.
> > ERROR: no recipe files to build, check your BBPATH and BBFILES?
>
> –
> You received this message because you are subscribed to the Google Groups “Beagle Board” group.
> To post to this group, send email to beagleboard@googlegroups.com.
> To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

|

Mark_Lazarewicz · November 1, 2010, 9:01pm

1. wget http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/ec2build.sh
1. ./ec2build.sh setup-oe
1. Download TI C6000 CGT tools to /mnt/angstrom-setup-scripts/sources/downloads.
1. Download the Graphics SDK to /mnt/angstrom-setup-scripts/sources/downloads.
1. ./ec2build.sh build-image test

I am at step 5 above the script that is failing is oebb.sh

— On Mon, 11/1/10, Sven Hartlieb sven.hartlieb@googlemail.com wrote:

> From: Sven Hartlieb sven.hartlieb@googlemail.com
> Subject: [beagleboard] Re: Angstrom ERROR: no recipe files to build, check your BBPATH and BBFILES?
> To: “Beagle Board” beagleboard@googlegroups.com
> Date: Monday, November 1, 2010, 7:11 AM
>
> I tried to use the option ProgramMMU, but nothing happens then, not
> even an output to the console. If I try to laod the outfile fterwards,
> the same “Trouble Writing Memory Block…” problem occurs.
>
> @Mark: I dont get what you are trying to explain to me, what exactly
> is the printout you have written?
>
> On 28 Okt., 17:21, Mark Lazarewicz <lazar…@yahoo.com> wrote:
> > BBPATH and BBFILES should point to what?
> >
> > lazarman@kerndev:~/Amazon cloud build$ ./ec2build.sh build-image test
> > + set -e
> > + ANGSTROM_SCRIPT_ID=f593f1c023cd991535c748682ab21154c807385e
> > + ANGSTROM_REPO_ID=24805033b1205acc35f8b4d75cc42f8b9c2a1b38
> > + USE_EC2=yes
> > + USE_PSTAGE=yes
> > + HALT=no
> > + AMI=ami-fd4aa494
> > + ‘[’ -e /home/lazarman/ec2build-ami.sh ‘]’
> > ++ date +%Y%m%d%H%M
> > + DATE=201010271827
> > + KEYPAIR=ec2build-keypair
> > + KEYPAIR_FILE=/home/lazarman/secret/ec2build-keypair.txt
> > + INSTANCES=/home/lazarman/ec2build-instances.txt
> > + VOLUMES=/home/lazarman/ec2build-volumes.txt
> > + MACH_TYPE=m1.xlarge
> > + DOWNLOAD_EBS=vol-08374961
> > + ANGSTROM_EBS=vol-24fa964d
> > + DOWNLOAD_DIR=/home/lazarman/downloads
> > + OEBB_DIR=/home/lazarman/angstrom-setup
> > + SCRIPT_DIR=/home/lazarman/scripts
> > + THIS_FILE=./ec2build.sh
> > + INSTANCE=
> > + MACH_NAME=
> > + build-image test
> > + IMAGE=test
> > + setup-oe
> > + ‘[’ ‘!’ -x /home/lazarman/angstrom-setup/oebb.sh ‘]’
> > + pushd /home/lazarman/angstrom-setup
> > ~/angstrom-setup ~/Amazon cloud build
> > + git checkout f593f1c023cd991535c748682ab21154c807385e
> > M sources/bitbake
> > M sources/openembedded
> > HEAD is now at f593f1c… oebb.sh: fixed remote name
> > + ‘[’ ‘!’ -d sources/openembedded/.git ‘]’
> > + pushd sources/openembedded
> > ~/angstrom-setup/sources/openembedded ~/angstrom-setup ~/Amazon cloud build
> > + git remote add myrepo git://gitorious.org/~Jadon/angstrom/jadon-openembedded.git
> > remote myrepo already exists.
> > + true
> > + git remote update
> > Updating myrepo
> > Updating origin
> > remote: Counting objects: 212, done.
> > remote: Compressing objects: 100% (152/152), done.
> > remote: Total 158 (delta 108), reused 1 (delta 0)
> > Receiving objects: 100% (158/158), 20.89 KiB, done.
> > Resolving deltas: 100% (108/108), completed with 48 local objects.
> > From git://git.openembedded.org/openembedded
> > d79f536…ddffbe4 master → origin/master
> > d79f536…ddffbe4 org.openembedded.dev → origin/org.openembedded.dev
> > + true
> > + git checkout 24805033b1205acc35f8b4d75cc42f8b9c2a1b38
> > HEAD is now at 2480503… beagleboard-demo-image: don’t waste time building
> > + popd
> > ~/angstrom-setup ~/Amazon cloud build
> > + popd
> > ~/Amazon cloud build
> > + oebb bitbake -k beagleboard-test-image
> > + cd /home/lazarman/angstrom-setup
> > + ./oebb.sh bitbake -k beagleboard-test-image
> > Using ~/.oe/environment to setup needed variables. It is recommended to do ‘. ~/.oe/environment’ and run ‘bitbake something’ without using ./oebb.sh as wrapper
> > Executing: bitbake -k beagleboard-test-image
> > ERROR: no recipe files to build, check your BBPATH and BBFILES?
> > NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it to increase performance.
> > ERROR: no recipe files to build, check your BBPATH and BBFILES?
>
> –
> You received this message because you are subscribed to the Google Groups “Beagle Board” group.
> To post to this group, send email to beagleboard@googlegroups.com.
> To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

|

Maksym_Parkachov · November 1, 2010, 10:05pm

Hi Mark,

I’m not sure what you are trying to do, but it seems like you wanted to build angstrom/oe on the ec2 instance. Sometimes ago I did the same and documented the process in the wiki.

http://wiki.openembedded.org/index.php/EC2CloudBuild

Hope this helps,
Maksym Parkachov.

Sven · November 3, 2010, 7:20am

@Mark: I dont get why you changed the name of my thread and we are
discussing the building of angstrom instead of my problem of loading
an outfile. Maybe you have mistaklen the thread?