Problems booting from an NFS server with U-boot in a AM1705 custom board

October 25, 2016, 4:13 pm

≪ Previous: Sys/BIOS or StarterWare one ARM

Hello,

First of all, my board has the following hardware:

SPI Flash : K0XMFI011 (Spansion) - 4MBytes - Connected to SPI0
Nand Flash: S34ML01G200TFI000 (Spansion) - 128MBytes - Connected to EMIFA
SDR SDRAM : AS4C16M16SA (Alliance Memory) - 32MBytes - Connected to EMIFB - Only one RAM chip
Ethernet : LAN8720a
Audio : TLV320AIC3106
Power : TPS65023

Important : I'm using UART1 for the console. This is for U-boot and Linux as well.

I have modified and recompiled U-boot and the Kernel to be able to use UART1 instead of UART0.

So far U-boot runs well with UART1 as console. Linux also runs OK when using the ramdisk http://arago-project.org/files/releases/2009.11/images/arago/arago-base-image-arago.ext2.gz

However the problems begin, when I try to boot from an NFS server.

I mounted a NFS server and tested it from another computer to be sure that it is ok. I have tried 4 different file systems where the only one that shows "more output" (lines in gray shwon below) in the terminal is from this link:

http://arago-project.org/files/releases/2009.11/images/arago/arago-base-image-arago.tar.gz

The last lines shown before the terminal shows no more information are the following:

udevd (489): /proc/489/oom_adj is deprecated, please use /proc/489/oom_score_adj instead.
udev: starting version 141
udevd[489]: inotify_add_watch(3, (null), 10) failed: Bad address

modprobe: FATAL: Could not load /lib/modules/3.3.0/modules.dep: No such file or directory

STAYS HERE FOREVER

When pinging the board from another computer, I can see that it is alive so the kernel must be still running.

Another interesting test is the one when disconnecting the ethernet cable, it shows the following activity: (so the kernel is definitely running)

nfs: server 192.168.0.27 not responding, still trying
nfs: server 192.168.0.27 not responding, still trying
nfs: server 192.168.0.27 OK
nfs: server 192.168.0.27 OK

Could this be a console configuration problem since I'm using UART1 instead of the default one UART0? I know that Linux is correctly builded to use UART1 (because it worked with the ramdisk).

Maybe when the filesystem gets loaded, some configuration file could be overwriting the configurations. But why then when using the ramdisk there is no problem? (assuming that both links shown above are the same file system only in different format) What do you think?

If you think that some file should be modified in the filesystem, where should I look?

My inittab, terminal log and U-boot environment vars are attached.

Thank you very much for your help

Best regards,

Patricio

(Please visit the site to view this file)

↧

Where is 'vmlinux' file

October 27, 2016, 1:57 am

≫ Next: StarterWare 1.20.04.01 McASP Example without EDMA

≪ Previous: Problems booting from an NFS server with U-boot in a AM1705 custom board

Hello,

I'd like to debug OMAP-L138 LCDK board with embedded linux.

I installed CCSv6.1.2, arago-2011.09-armv5te-linux-gnueabi-sdk, mcsdk_1_01_00_02, and sys/bios 6.35.04.

To debug project in CCSv6, I have followed your guide 'processors.wiki.ti.com/.../Linux_Debug_in_CCSv5' and'www.youtube.com/watch (about 23:00~25:00).

However, I can't find vmlinux file anywhere.

Is it not provided or am I just missing?

Should I make the vmlinux file, please let me know how the make it.

Thank you.

↧

StarterWare 1.20.04.01 McASP Example without EDMA

October 27, 2016, 8:38 pm

≫ Next: StarterWare 1_10_04_01 hw_pllc_OMAPL138.h #define PLLC_PLLM_PLLM (0x0000001Fu)

≪ Previous: Where is 'vmlinux' file

Hi, i'm trying McASP on c6748 LCDK with XDS100v2.

The loopback example of McASP from StarterWare can work.

In the example, the EDMA with ping-pong operation transfers/receives the buffers.

But I want to apply adaptive echo cancellation, data by data, for the real-time processing.

I'm trying two ways now

1. Reduce the sizes of buffers

I've tried to make NUM_SAMPLES_PER_AUDIO_BUF as 2 (one data for two channel)

And play the 1kHz sine wave which is produced by the code below:

short y1[3] = {0, -11585 , -16384};
const short A1 = 23170;

y1[0] = (short)(((int)y1[1]*A1 + ROUND )>> 14) - y1[2];
y1[2] = y1[1];
y1[1] = y1[0];

But I don't know why the txbuffer is always 0.

2. Delete the API of EDMA and configure the McASP without EDMA

Did anyone have this kinds of experences?

It has bothered me two weeks. Please help me.

↧

StarterWare 1_10_04_01 hw_pllc_OMAPL138.h #define PLLC_PLLM_PLLM (0x0000001Fu)

October 31, 2016, 5:38 am

≫ Next: Unable to implement EDMA with SYSBIOS on OMAPL138 LCDK.

≪ Previous: StarterWare 1.20.04.01 McASP Example without EDMA

AISgen told that PLLM can be from 1 to 64.

For that #define PLLC_PLLM_PLLM must be (0x0000003Fu)

spruh77c.pdf told (8.3.9 PLL Multiplier Control Register (PLLM))

PLLM 0-1F

Where is the truth ?

Alexander

↧

Unable to implement EDMA with SYSBIOS on OMAPL138 LCDK.

October 28, 2016, 7:09 am

≫ Next: SATA Cable Connection with OMAP-L138 LCDK

≪ Previous: StarterWare 1_10_04_01 hw_pllc_OMAPL138.h #define PLLC_PLLM_PLLM (0x0000001Fu)

Hi there,

I have converted the NAND example from the StarterWare to work with SYSBIOS.

I have enabled the interrupts for completion and error using the cfg.

Moved the NAND open and Nand read/ write api to a Task with pending Semaphore and added a clock to post Semaphore every 10 seconds.

I can see the design working fine when the NAND example is implemented with the NAND_XFER_MODE_CPU but when I change the NAND_DATA_XFER_MODE to NAND_XFER_MODE_DMA the nand write operation seems to fail.

- I am not sure, if there is a different way to initiate EDMA in SYSBIOS using cfg.

Would be great to get an insight on this asap. Ta.

Regards,

Mitesh

↧

SATA Cable Connection with OMAP-L138 LCDK

October 31, 2016, 11:06 pm

≫ Next: Linux spi-davinci driver: SPI Tx sends all zeros instead of actual data, possible DMA issue

≪ Previous: Unable to implement EDMA with SYSBIOS on OMAPL138 LCDK.

Hello,

I'd like to communicate SSD through SATA. Usual SSD has 22-pin SATA connector.Image may be NSFW.
Clik here to view.

However, there is only 7-pin SATA Conncetor in an OMAP-L138 LCDK.

Image may be NSFW.
Clik here to view.

If I connect SSD and LCDK board with 7pin to 22pin SATA Cable, do I share a power from provided 5V 3A adapter or use external adapter? If not, am I have to use a SMPS to share the power both SSD and LCDK?

As shown in first image, there are three different power, 3.3 V, 5 V, and 12 V. If I use properly, am I have to connect all?

Finally, I found 7 pin to 22 pin SATA cable below.

Image may be NSFW.
Clik here to view.

Is it OK to Communicate?

Thank you. :)

↧

Linux spi-davinci driver: SPI Tx sends all zeros instead of actual data, possible DMA issue

November 1, 2016, 4:05 am

≫ Next: OMAP-L138 USB OTG USB0_ID Connection?

≪ Previous: SATA Cable Connection with OMAP-L138 LCDK

Processor is OMAP-L138, running Linux 3.10.0 on the ARM. Linux has SPIDEV enabled and spi-davinci providing the low-level SPI support. SPI0 and SPI1 are both used, but SPI0 is only used on startup to send some configuration settings. SPI1 is used during normal for the application to communicate with other devices. Only SCS2 on SPI1 is used. SPI links are set up to use DMA for transfers.

With no other application processing running, SPI0 can send large data packets (up to 511 byte limit) using SPIDEV driver and IOCTL command for simultaneous read/write. Data is sent with no problems.

SPI1 can send small data packets (7 bytes) using SPIDEV driver and IOCTL command with no apparent problems.

However during normal running with multiple application threads running, if SPI1 tries to send larger data packets then the SPI often sends zero instead of the actual Tx data. It may lose the entire packet, or it may only zero out some of the packet. The more heavily loaded the ARM is, the more likely this is to happen. If I add printk reporting of the packet in spi_davinci.c function davinci_spi_bufs() before Tx, it reports the data correctly and data corruption stops. If I just take a checksum of the Tx data and printk that, it still confirms that the Tx data is correct but the data corruption comes back. So a delay before running the SPI transfer fixes it.

To me, this looks like a problem with DMA and caching. The extra delay allows the processor time to write cached data back, but when running normally the DMA reads data from the buffer before the cache has been flushed back. I would expect transfers to do a cache flush/clean before starting. I can't see it in the spi-davinci.c code, but it should be part of the DMA engine calls to run this.

I do have a relatively old version of spi-davinci.c, but I've checked against the latest Linux branch and there have been no changes which would affect this.

I have found one bug in the driver, where

 		t->tx_dma = dma_map_single(&spi->dev, buf,
				t->len, DMA_FROM_DEVICE);

should be DMA_TO_DEVICE, since the Tx is DMA'ing from memory to the SPI device. I tried changing this, but it did not fix the problem.

↧

OMAP-L138 USB OTG USB0_ID Connection?

November 1, 2016, 5:32 am

≫ Next: Brownout conditions for OMAPL138BZWTD4 and TMS320C6748 processors

≪ Previous: Linux spi-davinci driver: SPI Tx sends all zeros instead of actual data, possible DMA issue

Hi Support,

For OTG mode, do NOT connect the USB0_ID pin, that is, leave the pin floating. Is this correct?

Thanks.

↧

Brownout conditions for OMAPL138BZWTD4 and TMS320C6748 processors

November 1, 2016, 7:48 pm

≫ Next: NOT ABLE TO DEBUG ARM UBL BOOTLOADER OMAPL137

≪ Previous: OMAP-L138 USB OTG USB0_ID Connection?

Hi,

Is there any specific brownout condition/thresholds given for OMAPL138BZWTD4 and TMS320C6748 processors?

No information was provided for brownout conditions in the processor datasheet.

Regards,

Archana Rao

↧

NOT ABLE TO DEBUG ARM UBL BOOTLOADER OMAPL137

November 2, 2016, 1:00 am

≫ Next: Unable to read "uImage" from mmc 0:1

≪ Previous: Brownout conditions for OMAPL138BZWTD4 and TMS320C6748 processors

Team,

I am trying to build the davinci code that is provided DaVinci-PSP-SDK-03.20.00.13

I am trying to build the code for ARM UBL

My intention is to do Inline debugging of ARMUBL source code so the settings(SDRAM ,PINMUX)that I have configured is proper for customised omapl137 board !

I am able to do inline debugging for DSP UBL and succeeded I now want the same thing to be done on ARM so that later I can check for the uboot prompt if all the ubl is proper.

I am not able to do inline debugging for ARM not sure why! but when I click on debug selection I get an error as attached in the image

Image may be NSFW.
Clik here to view.

Warnings that I have is

Image may be NSFW.
Clik here to view.

I am able to rebuild the project and .out file gets generated!

But the build is actually not working and showing some error

Image may be NSFW.
Clik here to view.

Kindly need help on this!

Thank you

Deepak R

↧

Unable to read "uImage" from mmc 0:1

November 2, 2016, 10:42 pm

≫ Next: mplayer for omapl138

≪ Previous: NOT ABLE TO DEBUG ARM UBL BOOTLOADER OMAPL137

I'm using OMAPL138+ MT29F4G08ABADAWP for my project,

and the kernel: 3.2.0

uboot : 2009.11

and we have some boards,maybe 100 ps

at the first time, and all boards can work OK, and then power down,

and then power up,

then ,the question maybe will come on,the kernel refuse boot,(however , not every time it appears)

and logs are as below:

OMAP-L138 initialization passed!

Booting TI User Boot Loader

UBL Version: 1.65

UBL Flashtype: NAND

Starting NAND Copy...

Valid magicnum, 0x55424CBB, found in block 0x00000006.

DONE

Jumping to entry point at 0xC1080000.

U-Boot 2009.11 ( 9月 15 2015 - 04:52:33)

I2C: ready

DRAM: 128 MB

NAND: 512 MiB

MMC: davinci: 0

Bad block table found at page 262080, version 0x01

Bad block table found at page 262016, version 0x01

*** Warning - bad CRC or NAND, using default environment

In: serial

Out: serial

Err: serial

ARM Clock : 300000000 Hz

DDR Clock : 150000000 Hz

EMIFA CLock : 150000000 Hz

DSP Clock : 300000000 Hz

ASYNC3 Clock : 150000000 Hz

Enet config : 0

MMC 0 Enable : 0

Mach_Number: 2650

Resetting ethernet phy

hellowode++++++++++++++++0+++++++++++++++++!

hellowode++++++++++++++++1+++++++++++++++++!

hellowode++++++++++++++++2+++++++++++++++++!

Resetting Beep Pin_hellowode!

Set Ethernet MAC addrress!

00:50:c2:e6:77:22

Net: Ethernet PHY: GENERIC @ 0x1f [0x80000000]

Hit any key to stop autoboot: 0

Loading from nand0, offset 0x120000

** Unknown image type

reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **

reading uImage

** Unable to read "uImage" from mmc 0:1 **

8192 KiB M25P64 at 0:0 is now current device

Wrong Image Format for bootm command

ERROR: can't get kernel image!

OEM > print

bootargs=console=ttyS2,115200n8 ip=192.168.4.191 mem=64M@0xc0000000

bootcmd=if nboot.e 0xc0700000 0 0x120000; then setenv bootargs ${mem} ${bootargs} root=ubi0:ubifs rootfstype=ubifs ubi.mtd=4,2048; bootm 0xc0700000; fi; if mmc rescan 0; then if fatload mmc 0 0xc0600000 boot.scr; then source 0xc0600000; fi; if fatload mmc 0 0xc0700000 uImage; then setenv bootargs ${mem} ${bootargs} root=/dev/mmcblk0p2 rw rootwait; bootm 0xc0700000; fi; fi; if sf probe 0; then sf read 0xc0700000 0x80000 0x220000;setenv bootargs ${mem} ${bootargs}root=/dev/mmcblk0p2 rw rootwait;bootm 0xc0700000;fi

bootdelay=1

baudrate=115200

bootfile="uImage"

hwconfig=dsp:wake=yes

serverip=192.168.4.58

ipaddr=192.168.4.191

mmc_flash_uimage=mmc rescan 0; fatload mmc 0 0xc0700000 uImage;nand erase 0x120000 0x400000;nand write 0xc0700000 0x120000 0x400000;

mmc_flash_ubifs=mtdparts default; nand erase ubifs;ubi part ubifs 2048;ubi create ubifs;mmc rescan 0; fatload mmc 0 0xc0000000 ubifs.img;ubi write 0xc0000000 ubifs 0xd00000;

tftp_flash_uimage=tftp 0xc0700000 uImage;nand erase 0x120000 0x400000;nand write 0xc0700000 0x120000 0x400000;

tftp_flash_ubifs=mtdparts default; nand erase ubifs;ubi part ubifs 2048;ubi create ubifs;tftp 0xc0000000 ubifs.img;ubi write 0xc0000000 ubifs 0xd00000;

stdin=serial

stdout=serial

stderr=serial

ethaddr=00:50:c2:e6:77:22

ver=U-Boot 2009.11

is there anyone can help me?

Thanks very much!

↧

mplayer for omapl138

November 2, 2016, 11:00 pm

≫ Next: Detecting and mounting NAND Flash

≪ Previous: Unable to read "uImage" from mmc 0:1

hai sir,

i tried to cross compile mpalyer in my linux host but i am getting same error as previously i mentioned

can you please send me mlayer binary to my id mohammed.hussain@starcominfotech.com

Below is the error

1.root@caravel:/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem/MPlayer-1.0rc2# arm-arago-linux-gnueabi-gcc -v

Using built-in specs.

COLLECT_GCC=arm-arago-linux-gnueabi-gcc

Target: arm-arago-linux-gnueabi

Configured with: /sim/scratch_a0850442/arago-tmp-arago/work/i686-armv5te-sdk-arago-linux-gnueabi/gcc-cross-sdk-4.5-r41.2+svnr170880/gcc-4_5-branch/configure --build=i686-linux --host=i686-linux --target=arm-arago-linux-gnueabi --prefix=/arago-2011.09/armv5te --exec_prefix=/arago-2011.09/armv5te --bindir=/arago-2011.09/armv5te/bin --sbindir=/arago-2011.09/armv5te/bin --libexecdir=/arago-2011.09/armv5te/libexec --datadir=/arago-2011.09/armv5te/share --sysconfdir=/arago-2011.09/armv5te/etc --sharedstatedir=/arago-2011.09/armv5te/share/com --localstatedir=/arago-2011.09/armv5te/var --libdir=/arago-2011.09/armv5te/lib --includedir=/arago-2011.09/armv5te/include --oldincludedir=/arago-2011.09/armv5te/include --infodir=/arago-2011.09/armv5te/share/info --mandir=/arago-2011.09/armv5te/share/man --enable-largefile --disable-nls --enable-ipv6 --with-gnu-ld --enable-shared --enable-languages=c,c++,objc,fortran --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=arm-arago-linux-gnueabi- --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp --disable-libmudflap --with-float=soft --with-sysroot=/arago-2011.09/armv5te/arm-arago-linux-gnueabi --with-build-time-tools=/sim/scratch_a0850442/arago-tmp-arago/sysroots/i686-linux/usr/armv5te/arm-arago-linux-gnueabi/bin --with-build-sysroot=/sim/scratch_a0850442/arago-tmp-arago/sysroots/armv5te-arago-linux-gnueabi --disable-libunwind-exceptions --with-mpfr=/sim/scratch_a0850442/arago-tmp-arago/sysroots/i686-linux/usr --with-system-zlib --enable-__cxa_atexit

Thread model: posix

gcc version 4.5.3 20110311 (prerelease) (GCC)

2.root@caravel:/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem#tar -jxvf MPlayer-1.0rc2.tar.bz2

3.root@caravel:/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem#cd MPlayer-1.0rc2

4.root@caravel:/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem/MPlayer-1.0rc2# ./configure --prefix=/usr/local/filesystem_omapl138 --enable-cross-compile --cc=arm-arago-linux-gnueabi-gcc --host-cc=gcc --as=arm-arago-linux-gnueabi-as --ar=arm-arago-linux-gnueabi-ar --ranlib=arm-arago-linux-gnueabi-ranlib --target=arm-linux --disable-ivtv

Detected operating system: Linux

Detected host architecture: arm

Checking for arm-arago-linux-gnueabi-gcc version ... 4.5.3, ok

Checking for host cc ... gcc

Checking for cross compilation ... yes

Checking for assembler support of -pipe option ... yes

Checking for compiler support of named assembler arguments ... yes

Checking for .align is a power of two ... yes

Checking for ARMv5TE (Enhanced DSP Extensions) ... no

Checking for ARMv6 (SIMD instructions) ... no

Checking for iWMMXt (Intel XScale SIMD instructions) ... no

Checking for -lposix ... no

Checking for -lm ... yes

Checking for langinfo ... yes

Checking for language ... using en (man pages: en )

Checking for enable sighandler ... yes

Checking for runtime cpudetection ... no

----------------------------------------------------------

Install prefix: /usr/local/filesystem_omapl138

Data directory: /usr/local/filesystem_omapl138/share/mplayer

Config direct.: /usr/local/filesystem_omapl138/etc/mplayer

----------------------------------------------------------

NOTE: The --enable-* parameters unconditionally force options on, completely

skipping autodetection. This behavior is unlike what you may be used to from

autoconf-based configure scripts that can decide to override you. This greater

level of control comes at a price. You may have to provide the correct compiler

and linker flags yourself.

If you used one of these options (except --enable-gui and similar ones that

turn on internal features) and experience a compilation or linking failure,

make sure you have passed the necessary compiler/linker flags to configure.

If you suspect a bug, please read DOCS/HTML/en/bugreports.html.

5.root@caravel:/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem/MPlayer-1.0rc2# make

./version.sh `arm-arago-linux-gnueabi-gcc -dumpversion`

arm-arago-linux-gnueabi-gcc -I./libavcodec -I./libavformat -Wdisabled-optimization -Wno-pointer-sign -Wdeclaration-after-statement -I. -I. -I./libavutil -Wall -Wno-switch -Wpointer-arith -Wredundant-decls -O4 -pipe -ffast-math -fomit-frame-pointer -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DHAVE_CONFIG_H -c -o mplayer.o mplayer.c

libvo/font_load.h:97:13: warning: 'render_one_glyph' defined but not used

libvo/font_load.h:98:12: warning: 'kerning' defined but not used

----------------------------------------------------------

ve_x264.c:235:36: error: 'x264_param_t' has no member named 'b_bframe_pyramid'

ve_x264.c: In function 'control':

ve_x264.c:245:20: warning: unused variable 'mod'

make[1]: *** [ve_x264.o] Error 1

make[1]: Leaving directory `/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem/MPlayer-1.0rc2/libmpcodecs'

make: *** [libmpcodecs/libmpcodecs.a] Error 2

root@caravel:/home/ram/Desktop/ti-sdk-omapl138-lcdk-01.00.00/filesystem/MPlayer-1.0rc2#

↧

Detecting and mounting NAND Flash

November 3, 2016, 1:22 pm

≫ Next: SM320C6748-HIREL EVM

≪ Previous: mplayer for omapl138

Hello,

First of all, my board has the following hardware:

CPU: AM1705
SPI Flash : K0XMFI011 (Spansion) - 4MBytes - Connected to SPI0
Nand Flash: S34ML01G200TFI000 (Spansion) - 128MBytes - Connected to EMIFA
SDR SDRAM : AS4C16M16SA (Alliance Memory) - 32MBytes - Connected to EMIFB - Only one RAM chip
Ethernet : LAN8720a
Audio : TLV320AIC3106
Power : TPS65023

U-boot is inside a SPI flash chip connected at SPI0.

Now my question:
For an application I need my board to mount filesystem that is located in another computer. Using a NFS server I did this succesfully.

I also need at the same time to have access to an onboard NAND flash chip for storing data. I have looked inside the /dev folder but there are no device nodes like mtdX and mtdblockX, with X=0, 1, ... n. Does this mean that my NAND flash is not being detected? How can I mount this flash memory so it can be seen like a "secondary hard drive" for storing data?.

Thanks for your help in advance.

Patricio

↧

SM320C6748-HIREL EVM

November 3, 2016, 4:45 pm

≫ Next: SDRAM INLINE DEBUGGING NOT WORKING

≪ Previous: Detecting and mounting NAND Flash

Dear all,

my AA customer is interested in the evaluation of the SM320C6748-HIREL, is the TMDSLCDK6748 kit the right evaluation kit for the part ?

thanks,

Domenico

↧

SDRAM INLINE DEBUGGING NOT WORKING

November 4, 2016, 6:21 am

≫ Next: UBOOT FILES TO BE MODIFIED FOR OMAPL137 LINUX

≪ Previous: SM320C6748-HIREL EVM

Team

I have an issue in debugging the code using sdram

I am trying to achieve the following

I have added a led toggle code in my DSP-UBL code

My intention to do this

As i am using the custom board i want to know weather the dspubl was up and weather it got executed.so i heave added led toggle function

But when i try to debug inline i can see the values changes in the gpio register but my led will not blink!

My doubt about the issue is that in the linker file I have an address executing the code from L2RAM as mentioned

MEMORY
{
L2RAM org=0x80010000 len=0x00010000 /* L2 RAM/Cache */
////L2RAM : org = 0xc3000000, len = 0x1000000
}

SECTIONS
{
.text > L2RAM
.const > L2RAM
.bss > L2RAM
.far > L2RAM
.switch > L2RAM
.stack > L2RAM
.data > L2RAM
.cinit > L2RAM
.sysmem > L2RAM
.cio > L2RAM
}

but when i change it to sdram 0xc3000000,the code gets debugged and the led toggle and mean while 4/5 times or by luck it might have executed once I get a error message stating as mentioned below

MEMORY
{
//// L2RAM org=0x80010000 len=0x00010000 /* L2 RAM/Cache */
L2RAM : org = 0xc3000000, len = 0x1000000
}

Image may be NSFW.
Clik here to view.

Not sure how to debug and make sure dspubl is executed!

Even though the arm has the uart prints enabled in the code My intention is to make sure that dsp is running before arm by toggling leds

Need help on this working from past weeks to boot it on my custom board!

Kindly help asap

Thank you

Deepak R

↧

UBOOT FILES TO BE MODIFIED FOR OMAPL137 LINUX

November 4, 2016, 6:33 am

≫ Next: Installing and compile a program with OpenCV to run on OMAP l-138 lcdk

≪ Previous: SDRAM INLINE DEBUGGING NOT WORKING

tEAM I AM TRYING TO BOOT OMAPL137 ON MY CUSTOM BOARD!

I HAVE CHANGED THE CODE ACCORDINGLY FOR SPI CONFIGURATION IN ARM AND DSP -UBL.

I NEED TO KNOW WHAT COULD BE THE CHANGES THAT HAS TO BE DONE IN UBOOT FOR THE FOLLOWING CONFIGURATION IN THE SOURCE NEED A QUICK UPDATE ON THE FILES THAT HAS TO BE MODIFIED

IF ONLY ARM AND DSP UBL IS CHANGED IS THAT SUFFICIENT AND U BOOT CODE IS NOT REQUIRED TO MODIFLY

kINDLY LET ME KNOW THE VIEW WHAT FILES HAS TO BE CHANGED WITH RESPECT TO THE SPI CONF

tHANK YOU

dEEPAK R

↧

Installing and compile a program with OpenCV to run on OMAP l-138 lcdk

November 5, 2016, 9:29 am

≫ Next: BCH8 on OMAP-L138

≪ Previous: UBOOT FILES TO BE MODIFIED FOR OMAPL137 LINUX

Hi experts,

I am trying to compile a simple program using OpenCV 2.4.13, but i got always a bunch of errors while compiling.. Can you help me understand how can i compile the program?

I completed this instructions successfully:
http://processors.wiki.ti.com/index.php/Building_OpenCV_for_ARM_Cortex-A8

the program:

#include <opencv/cv.h> //main OpenCV header
#include <opencv/highgui.h> //GUI header

int main() {

// declare a new IplImage pointer
IplImage* myimage;

// load an image
myimage = cvLoadImage("springbreak.jpg",1); //change the file name to your own image

//create a new window & display the image
cvNamedWindow("Smile", 1);
cvShowImage("Smile", myimage);

//wait for key to close the window
cvWaitKey(0);
cvDestroyWindow("Smile");
cvReleaseImage(&myimage);
return 0;
}

The commad used to compile (i am specifying an installation folder that i have on my host pc):

arm-arago-linux-gnueabi-gcc opencv_hello.c -o opencv_hello -I /home/pfreire/openCV/build/install/include
/tmp/cck0hzXw.o: In function `cvRound':
opencv_hello.c:(.text+0x1c): undefined reference to `lrint'
/tmp/cck0hzXw.o: In function `cvDecRefData':
opencv_hello.c:(.text+0xf00): undefined reference to `cvFree_'
opencv_hello.c:(.text+0xfa8): undefined reference to `cvFree_'
/tmp/cck0hzXw.o: In function `cvGetRow':

(...) undefined reference for a lot of things

Thanks,

Regards,

Pedro

↧

BCH8 on OMAP-L138

November 6, 2016, 6:12 am

≫ Next: Returned test clock in OMAPL138BZWTD4 processor

≪ Previous: Installing and compile a program with OpenCV to run on OMAP l-138 lcdk

Hi.
We have OMAP-L138 board with Davinci nand controller. Is BCH8 ECC is supported in the Linux software for this controller?
I am looking through the Linux kernel Davinci Nand driver code and the maximum i see is 4bit HW ecc...

↧