Quantcast
Channel: Processors
Viewing all articles
Browse latest Browse all 124018

Forum Post: RE: Unable to communicate between OMAP 3530 and C6678

$
0
0

Hi Vivek

From the log you provided in your previous post, it looks like there are some arguments missing in the bootargs. When you did a printenv, it does not show the following two arguments highlighted in yellow below:

bootargs console=ttyS0,115200n8 rw mem=99M@0x80000000 mpurate=720 mem=100M@0x89300000 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M omapfb.mode=dvi:1280x720@60 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait ip=off

Could you please correct the bootargs as above and try again? 

If the problem is not solved with the above, please go to your NFS directory to the path etc/init.d/rcS and comment out the line that calls 'ultrasound -qws.' Then boot the board. Once it reaches the linux command prompt, try to 'ping' the IP address of the 6678, and let us know if the ping works or not.

Also please provide the complete log. Right from the beginning to the end, including bootargs, the kernel decompressing, the ultrasound demo being launched, everything. 

Thanks.


Viewing all articles
Browse latest Browse all 124018

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>