JTAG debugging the x-loader

Hello,

I'm quite new to the beagleboard, and especially to the JTAG world, so
I apologize in advance if I'm asking questions which are too trivial,
or just plain wrong.

I want to be able to single-step the x-loader code on my beagleboard
using JTAG.

Unfortunately, I couldn't find any tutorial on how to do so.
My Setup contains:
* A beagleboard
* A Blackhawk LAN560 JTAG emulator
* A Blackhawk XDS560T tracer (I know it's an overkill, I'm just using
it for the JTAG capabilities)
* A 20-to-14 pin adapter
* Code Composer Studio v4.1.2

From what I understood, in order to debug the x-loader using JTAG, I
need to halt the target, load the x-loader using the JTAG into the RAM
memory, change the program counter register to the beginning of the x-
loader, and let it run.

This setup has worked for a colleague of mine, who debugged the DSP
using CCS.

From what I saw, "it just works" for everyone.
I could find instructions only for JTAG debugging from the U-boot
stage (after stopping the countdown, using CCS), and even from that
stage, I had a problem loading my 'hello world' program, but I was
able to look at the memory using the JTAG.

I don't have any sentiments for CCS. If there's another software I can
use for the task, I'll use it.

Any reply would be highly appreciated,

Dan.

Hi,

Apologies if this is the wrong forum but I've recently been building
gstreamer-ti, bc-cat and the omap3-sgx-modules for some image
processing work on the Beagleboard (using the org.openembedded.dev
branch of OE)

All has gone well but I find it fiddly to install the ipkg's by hand on the
Beagleboard and so have come to add the recipes into the x11-image.

gstreamer-ti seems to be ok but the bc-cat recipe errors with the following

Configuring gstreamer-ti.
Collected errors:
* resolve_conffiles: Existing conffile

/home/ajlennon/OE/build/tmp-angstrom_2008_1/rootfs/x11-image/etc/device_table is different from the conffile in the new package. The new conffile will be placed at /home/ajlennon/OE/build/tmp-angstrom_2008_1/rootfs/x11-image/etc/device_table-opkg.

* opkg_install_cmd: Cannot install package bc-cube.
ERROR: Function do_rootfs failed

NOTE: package x11-image-1.0-r0: task do_rootfs: Failed
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/ajlennon/OE/sources/openembedded/recipes/images/x11-image.bb do_rootfs failed
ERROR: Task 11 (/home/ajlennon/OE/sources/openembedded/recipes/images/x11-image.bb, do_rootfs) failed with 256
ERROR: '/home/ajlennon/OE/sources/openembedded/recipes/images/x11-image.bb' failed
ERROR: '/home/ajlennon/OE/sources/openembedded/recipes/images/x11-image.bb' failed

Could somebody give me an idea where I need to look to fix this?

Also - I think I understand that the gstreamer-ti plugins are using the DSP core to
accelerate image/video encode and decode, but are the GL plugins for gstreamer also
able to make use of the OGLES/PowerVR core on the OMAP3530?

Thanks!

Alex

Hi,

Apologies if this is the wrong forum but I've recently been building
gstreamer-ti, bc-cat and the omap3-sgx-modules for some image
processing work on the Beagleboard (using the org.openembedded.dev
branch of OE)

All has gone well but I find it fiddly to install the ipkg's by hand on the
Beagleboard and so have come to add the recipes into the x11-image.

gstreamer-ti seems to be ok but the bc-cat recipe errors with the following

> Configuring gstreamer-ti.
> Collected errors:
> * resolve_conffiles: Existing conffile /home/ajlennon/OE/build/tmp-angstrom_2008_1/rootfs/x11-image/etc/device_table is different from the conffile in the new package. The new conffile will be placed at /home/ajlennon/OE/build/tmp-angstrom_2008_1/rootfs/x11-image/etc/device_table-opkg.
> * opkg_install_cmd: Cannot install package bc-cube.

You need to provide packagenames (e.g. bc-cube-x11) instead of recipe names.

Could somebody give me an idea where I need to look to fix this?

Also - I think I understand that the gstreamer-ti plugins are using the DSP core to
accelerate image/video encode and decode, but are the GL plugins for gstreamer also
able to make use of the OGLES/PowerVR core on the OMAP3530?

If you build gst-plugins-gles, you get gl plugins that can leverage the SGX. They currently don't do much beyond colourconv and spinning a cube, though.

regards,

Koen

Hi Koen,

You need to provide packagenames (e.g. bc-cube-x11) instead of recipe names.

Thanks for coming back to me - that does the trick!

If you build gst-plugins-gles, you get gl plugins that can leverage the SGX. They currently don't do much beyond colourconv and spinning a cube, though.

I've been experimenting with the OSSBuild Win32 build of GStreamer, specifically
the glfiltersobel element for edge detection which I need to perform on input images.

Apologies if I'm misunderstanding but do we know if the GStreamer GL plugins
leverage the OpenGLES core on the Beagleboard?

If not is that something that should be straightforward for me to support,
OpenGLES being a subset of OpenGL, or are there issues I'm missing here?

Also do we know if GStreamer-TI makes use of the TI bc-cat kernel module IOCTLs to
accelerate texture uploads as I've encountered this as a performance bottle-neck on Win32
Direct3D systems in the past?

(Sorry if these questions are better directed to a TI list somewhere?)

Thanks!

Alex