No file under the path "QorIQ-SDK-V1.6-20140619-yocto\build_p2020rdb_release\tmp\work\ppce500v2-fsl-linux-gnuspe\libgcc\4.8.1 fsl-r0\build"

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No file under the path "QorIQ-SDK-V1.6-20140619-yocto\build_p2020rdb_release\tmp\work\ppce500v2-fsl-linux-gnuspe\libgcc\4.8.1 fsl-r0\build"

851 Views
kuoweihsu
Contributor III

Hi,

 

We've recently compiled "Das U-Boot" with gcc 4.8.1 for powerpc target and debug by CW using a elf file.

After reference "AN4876:CodeWarrior U-Boot Debugging.pdf" and "Targeting_PA_Processors.pdf", we can debug u-boot from setpicloadaddr 0xfff40000 (768K).

However, it shows that the file "start.S" can't be find under "QorIQ-SDK-V1.6-20140619-yocto\build_p2020rdb_release\tmp\work\ppce500v2-fsl-linux-gnuspe\libgcc\4.8.1 fsl-r0\build".

Truely, we don't have any files under that path.

 

Is any process we miss???

 

Thanks for your response.

Labels (1)
Tags (1)
0 Kudos
2 Replies

614 Views
lunminliang
NXP Employee
NXP Employee

There are start.S in the path:

QorIQ-SDK-V1.6-20140619-yocto/build_p2020rdb_release/tmp/work/p2020rdb-fsl-linux-gnuspe/u-boot/2014.01+fslgit-r0/git/arch/powerpc/cpu

pastedImage_1.png

614 Views
kuoweihsu
Contributor III

Hi, lunminliang,

We found that the path "QorIQ-SDK-V1.6-20140619-yocto\build_p2020rdb_release\tmp\work\ppce500v2-fsl-linux-gnuspe\libgcc\4.8.1 fsl-r0\build" is wrong by some reasons and talked about this issue in this link

U-boot debug failed because "Can't find a source file"

Best Regard,

kuowei

0 Kudos