named pipe issue on Davinci
hi,
I tried to the following code on DM355 platform, but always got stuck at
fopen(),
it never returned. Any help would be appreicated.
#include
#include
#include
int main()
{
char MY_NAMMED_PIPE[64]="/tmp/mypipe";
FILE *dps=NULL;
printf("mkfifo on %s\n", MY_NAMMED_PIPE);
if (mkfifo(MY_NAMMED_PIPE, 0777)) {
perror("Error with Server FIFO");
exit(1);
}
printf("fopen on %s\n", MY_NAMMED_PIPE);
dps=fopen(MY_NAMMED_PIPE,"w");
if(dps == NULL) {
perror("Error opening the FIFO\n");
exit(2);
}
while(1){
// do sth
}
exit(0);
}
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
dm6467 nand filesystem question
Hey, all I am trying to boot kernel and filesystem from the NAND on the 6467 EVM. Please help! 1. The nand partition is 0x-0x0008 : "bootloader" 0x0008-0x000a : "params" 0x000a-0x004a : "kernel" 0x004a-0x0800 : "filesystem" 2. The "filesystem" and "kernel" have been erased and programmed with "nand erase" and "nand write" from u-boot. nboot command finds the kernel section OK and continues the boot. bootargs is "console=ttyS0,115200n8 noinitrd rw root=/dev/mtdblock3" 3. The related booting message is nand_davinci nand_davinci.0: Using 1-bit hardware ECC NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit) No oob scheme defined for oobsize 256 Scanning device for bad blocks Creating 4 MTD partitions on "nand_davinci.0": 0x-0x0008 : "bootloader" 0x0008-0x000a : "params" 0x000a-0x004a : "kernel" 0x004a-0x0800 : "filesystem" nand_davinci nand_davinci.0: hardware revision: 2.2 Registering Audio Devices. Total communication peripherals (ASP) : 2 Codec with ID = 0 on ASP = 0 is initialized.Using minor number : 3 Configuring the McASP as Master Configuring the McASP 1 for DIT SPDIF on ASP = 1 isinitialized.Using minor number : 19 NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 16384) NET: Registered protocol family 1 NET: Registered protocol family 17 end_request: I/O error, dev mtdblock3, sector 0 Buffer I/O error on device mtdblock3, logical block 0 end_request: I/O error, dev mtdblock3, sector 0 Buffer I/O error on device mtdblock3, logical block 0 end_request: I/O error, dev mtdblock3, sector 8 Buffer I/O error on device mtdblock3, logical block 1 end_request: I/O error, dev mtdblock3, sector 8 Buffer I/O error on device mtdblock3, logical block 1 end_request: I/O error, dev mtdblock3, sector 16 Buffer I/O error on device mtdblock3, logical block 2 end_request: I/O error, dev mtdblock3, sector 16 Buffer I/O error on device mtdblock3, logical block 2 end_request: I/O error, dev mtdblock3, sector 24 Buffer I/O error on device mtdblock3, logical block 3 end_request: I/O error, dev mtdblock3, sector 24 Buffer I/O error on device mtdblock3, logical block 3 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3) Please HELP Thank you all ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
NAND uboot params
What is the best way to read the "bootdelay" param from the linux kernel? Looks like the NAND param sector address starts from 0x4200 + 0x8, an ioremap failed. Anyone knows how to read the u-boot params on the NAND from the kernel? Thx a ton! ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
uboot upgrade
Hi, I made some changes to the u-boot, but how to program the new uboot.bin into the nand on the DM6467? I mean, by using the uboot commands, instead of the JTAG/CCS. Could not find related info. Thanks for your help! ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
uboot upgrade on dm6467
The PSP document suggests "nand read 8200 0x2 0x800". However, this command failed, when I tried to upgrade u-boot from the running u-boot. *** DM6467 EVM # nand read 8200 2 800 NAND read: device 0 offset 0x2, size 0x800 2048 bytes read: ERROR DM6467 EVM # *** Did somebody successfully upgrade the u-boot from a running u-boot, please share some lights! ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: uboot upgrade
Tried that. did not work for 6467. --- On Tue, 3/3/09, Lori Gao wrote: > From: Lori Gao > Subject: Re: uboot upgrade > To: gb...@yahoo.com > Cc: davinci-linux-open-source@linux.davincidsp.com, > davinci-linux-open-source-boun...@linux.davincidsp.com > Date: Tuesday, March 3, 2009, 6:28 PM > Hi: > > I am't familiar with the 6467, but in dm355 the u-boot > can update itself. > > the command sequence: > > down the u-boot bin file: using uart or network > for example: tftp 0x80700 u-boot.bin > > nand erase 0x2 //in > dm355 the size of u-boot > should be smaller than 128KB, otherwise, you have to take > more actions. > > nand write 0x8070 > 0x2 > > > > > Lori Gao > > R&D center(Shanghai) > Rayco (Shanghai) Medical Products Company Limited > Carestream Health Inc. > > > > gather bzbz > Sent by: > davinci-linux-open-source-boun...@linux.davincidsp.com > 03/04/2009 10:12 AM > Please respond to > gb...@yahoo.com > > > To > davinci-linux-open-source@linux.davincidsp.com > cc > > Subject > uboot upgrade > > > > > > > > Hi, > > I made some changes to the u-boot, but how to program the > new uboot.bin > into the nand on the DM6467? I mean, by using the uboot > commands, instead > of the JTAG/CCS. Could not find related info. Thanks for > your help! > > > > > ___ > Davinci-linux-open-source mailing list > Davinci-linux-open-source@linux.davincidsp.com > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: uboot upgrade on dm6467
Thanks! --- On Tue, 3/3/09, Rajashekhara, Sudhakar wrote: > From: Rajashekhara, Sudhakar > Subject: RE: uboot upgrade on dm6467 > To: "gb...@yahoo.com" , > "davinci-linux-open-source@linux.davincidsp.com" > > Date: Tuesday, March 3, 2009, 10:05 PM > Try the following to re-write the NAND with different u-boot > image: > > 1. Read from NAND offset 0x2 to some RAM address (For > Ex: 0x8200). > 2. Erase the NAND completely with "nand erase" > command from u-boot. > 3. Download the latest u-boot.bin file through the Ethernet > using tftp command. This will get downloaded to some RAM > address (Ex: 8070). > 4. Calculate the number of pages the new u-boot.bin will > occupy using the formaula: (file_size/NAND_PAGE_SIZE) + 1. > Here NAND_PAGE_SIZE for DaVinci-HD is 2048. > 5. Write the downloaded u-boot.bin to NAND offset 0x20800. > 6. Modify the contents of RAM (@ 0x8200) which has the > contents from NAND offset 0x2, so that offset 0x8208 > reflects the correct number of pages across which u-boot.bin > spans. > 7. Write back the contents modified above to NAND offset > 0x2. > 8. Restart the board. Board will now boot the latest > u-boot. > > Sometimes, when you read back the NAND, though U-Boot > reports ERROR, read will be successful. This can be verified > by dumping the contents of the memory. > > Regards, Sudhakar > > From: > davinci-linux-open-source-boun...@linux.davincidsp.com > [davinci-linux-open-source-boun...@linux.davincidsp.com] On > Behalf Of gather bzbz [gb...@yahoo.com] > Sent: Wednesday, March 04, 2009 8:07 AM > To: davinci-linux-open-source@linux.davincidsp.com > Subject: uboot upgrade on dm6467 > > The PSP document suggests "nand read 8200 0x2 > 0x800". However, this command failed, when I tried to > upgrade u-boot from the running u-boot. > > *** > DM6467 EVM # nand read 8200 2 800 > > NAND read: device 0 offset 0x2, size 0x800 > 2048 bytes read: ERROR > DM6467 EVM # > *** > > Did somebody successfully upgrade the u-boot from a running > u-boot, please share some lights! > > > > > > ___ > Davinci-linux-open-source mailing list > Davinci-linux-open-source@linux.davincidsp.com > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
DVFlasher possible for NAND on DM6467?
Hi, I was very happy with DVFlasher for the NOR on DM6446. What about NAND on DM6467? Any updates? Thanks ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
DM6467 EVM Video issue
Hi, When running the encode demo on the EVM, I find that if I disconnect the video source, then wait for a few second, then plug back the source in, the pictures shown will be messed up. Most of the time, the screen will be devided into upper half and bottom half. Any ideas. Thanks ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: DM6467 EVM Video issue
Thanks. Any programmable way to detect the loss of sync situation so we can toggle the stream_on/off? --- On Sun, 3/15/09, Jadav, Brijesh R wrote: > From: Jadav, Brijesh R > Subject: RE: DM6467 EVM Video issue > To: "gb...@yahoo.com" , > "davinci-linux-open-source@linux.davincidsp.com" > > Date: Sunday, March 15, 2009, 9:11 PM > Hi, > > This is because DMA and VPIF go out of sync and the way to > solve this issue is to reset the VPIF by streaming off and > then streaming it on again. > > Thanks, > Brijesh Jadav > > > -Original Message- > > From: > davinci-linux-open-source-boun...@linux.davincidsp.com > > > [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] > On > > Behalf Of gather bzbz > > Sent: Saturday, March 14, 2009 5:36 AM > > To: davinci-linux-open-source@linux.davincidsp.com > > Subject: DM6467 EVM Video issue > > > > > > Hi, > > > > When running the encode demo on the EVM, I find that > if I disconnect > > the video source, then wait for a few second, then > plug back the > > source in, the pictures shown will be messed up. Most > of the time, the > > screen will be devided into upper half and bottom > half. > > > > Any ideas. Thanks > > > > > > > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
tvp7002 driver for 1080p
Hi, is the tvp7002 driver updated for 1080p? so far I can see only 1080i supported in the release. Thanks. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
memory map and encodeCombo.x64P
Hi, I recently changed the memory map of my dm6446 dvevm board from 256M to 128M, but how to recompile the encodeCombo.x64P (or the loopbackCombo.x64P)? Have not found any related files.I know how to recompile the examples under codec_engine Thanks Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: memory map and encodeCombo.x64P
When I tried to run the encode-decode sample, I got
the followings
[EMAIL PROTECTED]:/opt# ./encodedecode
Encodedecode demo started.
Display set to 720x480 and no zoom
Assertion failed (((drvObj != NULL) &&
(IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj ==
NULL) && (cmdId == CMD_PROC_ATTACH))). File : drv_a6
OC T:0x402c8568: Comm_create('encodedecode', ...)
failed: status 0x80008002
Encodedecode Error: Failed to open codec engine
encodedecode
[EMAIL PROTECTED]:/opt#
So I guess I need to recompile the servers according
to new memory map?
Please advise.
--- gather bzbz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I recently changed the memory map of my dm6446 dvevm
> board from 256M to 128M, but how to recompile the
> encodeCombo.x64P (or the loopbackCombo.x64P)? Have
> not
> found any related files.I know how to recompile
> the examples under codec_engine
>
> Thanks
>
>
>
>
>
>
> Looking for last minute shopping deals?
> Find them fast with Yahoo! Search.
>
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
> ___
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: memory map and encodeCombo.x64P
yes, I think I have. For DM6446, a change in the
memory map will trigger a recompiling of the codec
server, dsplink, right?
--- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
> Have you gone through the following:
>
http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map
>
> Regards,
> Mugdha
>
> -Original Message-
> From:
>
[EMAIL PROTECTED]
>
[mailto:[EMAIL PROTECTED]
> On
> Behalf Of gather bzbz
> Sent: Thursday, March 13, 2008 11:52 AM
> To: gather bzbz;
> davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: memory map and encodeCombo.x64P
>
> When I tried to run the encode-decode sample, I got
> the followings
>
> [EMAIL PROTECTED]:/opt# ./encodedecode
> Encodedecode demo started.
> Display set to 720x480 and no zoom
> Assertion failed (((drvObj != NULL) &&
> (IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj ==
> NULL) && (cmdId == CMD_PROC_ATTACH))). File : drv_a6
> OC T:0x402c8568:
> Comm_create('encodedecode', ...)
> failed: status 0x80008002
> Encodedecode Error: Failed to open codec engine
> encodedecode
> [EMAIL PROTECTED]:/opt#
>
> So I guess I need to recompile the servers according
> to new memory map?
>
> Please advise.
>
> --- gather bzbz <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I recently changed the memory map of my dm6446
> dvevm board from 256M
> > to 128M, but how to recompile the encodeCombo.x64P
> (or the
> > loopbackCombo.x64P)? Have not found any related
> files.I know how
> > to recompile the examples under codec_engine
> >
> > Thanks
> >
> >
> >
> >
> >
> >
>
>
> > Looking for last minute shopping deals?
> > Find them fast with Yahoo! Search.
> >
>
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
> > ___
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> >
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> >
>
>
>
>
>
>
> Never miss a thing. Make Yahoo your home page.
> http://www.yahoo.com/r/hs
> ___
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: memory map and encodeCombo.x64P
Thank you for the confirmation. So, where to find the
files to recompile the server for a different memory
map? I would assume the nice write-ups in the wiki on
the related topic still apply.
Please help
--- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
> Yes, it will.
>
> Regards,
> Mugdha
>
> -Original Message-
> From: gather bzbz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 13, 2008 1:58 PM
> To: Kamoolkar, Mugdha;
> davinci-linux-open-source@linux.davincidsp.com
> Subject: RE: memory map and encodeCombo.x64P
>
> yes, I think I have. For DM6446, a change in the
> memory map will
> trigger a recompiling of the codec server, dsplink,
> right?
>
> --- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
>
> > Have you gone through the following:
> >
>
http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map
> >
> > Regards,
> > Mugdha
> >
> > -Original Message-
> > From:
> >
>
[EMAIL PROTECTED]
> >
>
[mailto:[EMAIL PROTECTED]
> > On
> > Behalf Of gather bzbz
> > Sent: Thursday, March 13, 2008 11:52 AM
> > To: gather bzbz;
> > davinci-linux-open-source@linux.davincidsp.com
> > Subject: Re: memory map and encodeCombo.x64P
> >
> > When I tried to run the encode-decode sample, I
> got the followings
> >
> > [EMAIL PROTECTED]:/opt# ./encodedecode
> Encodedecode demo started.
> > Display set to 720x480 and no zoom
> > Assertion failed (((drvObj != NULL) &&
> (IS_OBJECT_VALID (drvObj,
> > SIGN_DRV))) || ((drvObj ==
> > NULL) && (cmdId == CMD_PROC_ATTACH))). File :
> drv_a6 OC T:0x402c8568:
> > Comm_create('encodedecode', ...)
> > failed: status 0x80008002
> > Encodedecode Error: Failed to open codec engine
> encodedecode
> > [EMAIL PROTECTED]:/opt#
> >
> > So I guess I need to recompile the servers
> according to new memory
> > map?
> >
> > Please advise.
> >
> > --- gather bzbz <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > I recently changed the memory map of my dm6446
> > dvevm board from 256M
> > > to 128M, but how to recompile the
> encodeCombo.x64P
> > (or the
> > > loopbackCombo.x64P)? Have not found any related
> > files.I know how
> > > to recompile the examples under codec_engine
> > >
> > > Thanks
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
> >
> > > Looking for last minute shopping deals?
> > > Find them fast with Yahoo! Search.
> > >
> >
>
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
> > > ___
> > > Davinci-linux-open-source mailing list
> > > Davinci-linux-open-source@linux.davincidsp.com
> > >
> >
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> > >
> >
> >
> >
> >
> >
>
> >
> > Never miss a thing. Make Yahoo your home page.
> > http://www.yahoo.com/r/hs
> > ___
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> >
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> >
>
>
>
>
>
>
> Never miss a thing. Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: memory map and encodeCombo.x64P
I mean, where to find the original source files for
loopbackCombo.x64P or encodeCombo.x64P in the original
TI demos so I can change the memory maps and recompile
for my board myself?
Can help plz?
--- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
> Chris can confirm, but I think the write-ups should
> apply. As far as I
> know, you'll have to make the changes in the files
> that you have
> already. You'll probably not find any ready-made
> file for the different
> memory map that you need, since there could be so
> many different
> variations of the memory maps as per everyone's
> specific needs.
>
> Regards,
> Mugdha
>
> -Original Message-
> From: gather bzbz [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 4:38 AM
> To: Kamoolkar, Mugdha;
> davinci-linux-open-source@linux.davincidsp.com
> Subject: RE: memory map and encodeCombo.x64P
>
> Thank you for the confirmation. So, where to find
> the files to recompile
> the server for a different memory map? I would
> assume the nice write-ups
> in the wiki on the related topic still apply.
>
> Please help
>
> --- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
>
> > Yes, it will.
> >
> > Regards,
> > Mugdha
> >
> > -Original Message-
> > From: gather bzbz [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, March 13, 2008 1:58 PM
> > To: Kamoolkar, Mugdha;
> > davinci-linux-open-source@linux.davincidsp.com
> > Subject: RE: memory map and encodeCombo.x64P
> >
> > yes, I think I have. For DM6446, a change in the
> memory map will
> > trigger a recompiling of the codec server,
> dsplink, right?
> >
> > --- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
> >
> > > Have you gone through the following:
> > >
> >
>
http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map
> > >
> > > Regards,
> > > Mugdha
> > >
> > > -Original Message-
> > > From:
> > >
> >
>
[EMAIL PROTECTED]
> > >
> >
>
[mailto:[EMAIL PROTECTED]
> > > On
> > > Behalf Of gather bzbz
> > > Sent: Thursday, March 13, 2008 11:52 AM
> > > To: gather bzbz;
> > > davinci-linux-open-source@linux.davincidsp.com
> > > Subject: Re: memory map and encodeCombo.x64P
> > >
> > > When I tried to run the encode-decode sample, I
> > got the followings
> > >
> > > [EMAIL PROTECTED]:/opt# ./encodedecode
> > Encodedecode demo started.
> > > Display set to 720x480 and no zoom
> > > Assertion failed (((drvObj != NULL) &&
> > (IS_OBJECT_VALID (drvObj,
> > > SIGN_DRV))) || ((drvObj ==
> > > NULL) && (cmdId == CMD_PROC_ATTACH))). File :
> > drv_a6 OC T:0x402c8568:
> > > Comm_create('encodedecode', ...)
> > > failed: status 0x80008002
> > > Encodedecode Error: Failed to open codec engine
> > encodedecode
> > > [EMAIL PROTECTED]:/opt#
> > >
> > > So I guess I need to recompile the servers
> > according to new memory
> > > map?
> > >
> > > Please advise.
> > >
> > > --- gather bzbz <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > >
> > > > I recently changed the memory map of my dm6446
> > > dvevm board from 256M
> > > > to 128M, but how to recompile the
> > encodeCombo.x64P
> > > (or the
> > > > loopbackCombo.x64P)? Have not found any
> related
> > > files.I know how
> > > > to recompile the examples under
> codec_engine
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
> > >
> > > > Looking for last minute shopping deals?
> > > > Find them fast with Yahoo! Search.
> > > >
> > >
> >
>
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
> > > >
> ___
> > > > Davinci-linux-open-source mailing list
> > > > Davinci-linux-open-source@linux.davincidsp.com
> > > >
> > >
> >
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> > > >
> > >
> > >
> > >
Codec server loading error
Guys,
I recompile the video_copy server to fit my new memory
map, everything looks good, then I copy
the video_copy.x64P, app.out, in.dat to the nfs
server. After the board boots up, I get errors when I
tried to run the ./app.out
app.out: ELF 32-bit LSB executable, ARM, version 1
(SYSV), for GNU/Linux 2.4.17, dynamically linked (uses
shared libs), not strippd
[EMAIL PROTECTED]:/opt/# ./app.out
App-> Application started.
CE T:0x4003a6e8: Engine_open('video_copy', 0x0,
0xbefffc3c)
CE T:0x4003a6e8: rserverOpen('./video_copy.x64P'),
count = 0
OP T:0x4003a6e8: Process_create('./video_copy.x64P',
0xbefffc40)
OP T:0x40946b60: daemon()
OP T:0x40946b60: Process_create> Initializing DSP
PROC...
OP T:0x40946b60: Process_create> Attaching to DSP
PROC...
OP T:0x40946b60: Process_create> Opening MSGQ pool...
OP T:0x40946b60: Process_create> Loading
./video_copy.x64P on DSP (1 args)...
OP T:0x40946b60: Process_create> Operation FAILED,
status=-2147450861[0x80008013]
OP T:0x40946b60: Process_delete> Entered.
OP T:0x40946b60: Process_delete> Closing remote
transport...
OP T:0x40946b60: Process_delete> Closing remote
transport FAILED, status=0x8000800b.
OP T:0x40946b60: Process_delete> Stopping DSP...
OP T:0x40946b60: Process_delete> Stopping DSP FAILED,
status=0x8000801b
OP T:0x40946b60: Process_delete> Closing pool...
OP T:0x40946b60: Process_delete> Detaching from DSP...
OP T:0x40946b60: Process_delete> Destroying DSP...
(object, that is)
OP T:0x40946b60: putReply(0x2): proc = 0x1d3e8
OP T:0x4003a6e8: Process_delete(0x1d3e8)
OP T:0x4003a6e8: Process_delete(0x1d3e8) freeing
object ...
OP T:0x4003a6e8: Process_delete() Returning.
CE T:0x4003a6e8: rserverOpen('./video_copy.x64P'):
0x1c634 done.
Assertion failed (((drvObj != NULL) &&
(IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj ==
NULL) && (cmdId == CMD_PROC_ATTACH))).6
OC T:0x4003a6e8: Comm_create('video_copy', ...)
failed: status 0x80008002
CE T:0x4003a6e8: Engine_close(0x1d3b8)
CE T:0x4003a6e8: rserverClose(0x1c634), count = 1
OP T:0x4003a6e8: Process_delete(0x0)
OP T:0x4003a6e8: Process_delete() Returning.
CE T:0x4003a6e8: rserverClose(0x1c634) done.
CEapp-> ERROR: can't open engine video_copy
App-> Application FAILED.
OP T:0x40946b60: putReply(0x1): proc = 0x0
OP T:0x40946b60: daemon() terminating
So what gives?
Thank you all!
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Codec server loading error
Yeah, 0x80008013 means param_out_of_range.
I followed the sample in the wiki to change the memory
map to 128M from 256M. I am using dsplink v1.30, so I
think I do not need to worry about the ARM-side stuff
(seems only dsplink v1.40 users should?). I will
double-check my modifications again.
Meanwhile, anyone succeeded in changing the memory map
to 128M for video_copy test?
Thank you all.
--- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
> There's some problem in your memory configuration.
> 0x80008013 is
> DSP_ERANGE, which comes when the memory
> configuration of DSP executable
> does not match ARM-side configuration. Hence loading
> the DSP has failed.
>
> Regards,
> Mugdha
>
> -Original Message-
> From:
>
[EMAIL PROTECTED]
>
[mailto:[EMAIL PROTECTED]
> On
> Behalf Of gather bzbz
> Sent: Friday, March 14, 2008 3:16 PM
> To: davinci-linux-open-source@linux.davincidsp.com
> Subject: Codec server loading error
>
>
> Guys,
>
> I recompile the video_copy server to fit my new
> memory map, everything
> looks good, then I copy the video_copy.x64P,
> app.out, in.dat to the nfs
> server. After the board boots up, I get errors when
> I tried to run the
> ./app.out
>
> app.out: ELF 32-bit LSB executable, ARM, version 1
> (SYSV), for GNU/Linux
> 2.4.17, dynamically linked (uses shared libs), not
> strippd
> [EMAIL PROTECTED]:/opt/# ./app.out
> App-> Application started.
> CE T:0x4003a6e8: Engine_open('video_copy', 0x0,
> 0xbefffc3c)
> CE T:0x4003a6e8: rserverOpen('./video_copy.x64P'),
> count = 0 OP
> T:0x4003a6e8: Process_create('./video_copy.x64P',
> 0xbefffc40)
> OP T:0x40946b60: daemon()
> OP T:0x40946b60: Process_create> Initializing DSP
> PROC...
> OP T:0x40946b60: Process_create> Attaching to DSP
> PROC...
> OP T:0x40946b60: Process_create> Opening MSGQ
> pool...
> OP T:0x40946b60: Process_create> Loading
> ./video_copy.x64P on DSP (1
> args)...
> OP T:0x40946b60: Process_create> Operation FAILED,
> status=-2147450861[0x80008013] OP T:0x40946b60:
> Process_delete> Entered.
> OP T:0x40946b60: Process_delete> Closing remote
> transport...
> OP T:0x40946b60: Process_delete> Closing remote
> transport FAILED,
> status=0x8000800b.
> OP T:0x40946b60: Process_delete> Stopping DSP...
> OP T:0x40946b60: Process_delete> Stopping DSP
> FAILED, status=0x8000801b
> OP T:0x40946b60: Process_delete> Closing pool...
> OP T:0x40946b60: Process_delete> Detaching from
> DSP...
> OP T:0x40946b60: Process_delete> Destroying DSP...
> (object, that is)
> OP T:0x40946b60: putReply(0x2): proc = 0x1d3e8 OP
> T:0x4003a6e8:
> Process_delete(0x1d3e8) OP T:0x4003a6e8:
> Process_delete(0x1d3e8) freeing
> object ...
> OP T:0x4003a6e8: Process_delete() Returning.
> CE T:0x4003a6e8: rserverOpen('./video_copy.x64P'):
> 0x1c634 done.
> Assertion failed (((drvObj != NULL) &&
> (IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj ==
> NULL) && (cmdId == CMD_PROC_ATTACH))).6
> OC T:0x4003a6e8: Comm_create('video_copy', ...)
> failed: status 0x80008002
> CE T:0x4003a6e8: Engine_close(0x1d3b8)
> CE T:0x4003a6e8: rserverClose(0x1c634), count = 1 OP
> T:0x4003a6e8:
> Process_delete(0x0) OP T:0x4003a6e8:
> Process_delete() Returning.
> CE T:0x4003a6e8: rserverClose(0x1c634) done.
> CEapp-> ERROR: can't open engine video_copy
> App-> Application FAILED.
> OP T:0x40946b60: putReply(0x1): proc = 0x0 OP
> T:0x40946b60: daemon()
> terminating
>
> So what gives?
>
> Thank you all!
>
>
>
>
>
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
>
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>
> ___
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Codec server loading error
Yes, already rebuilt the dsplink and cmem. Thought you
were talking about the arm-side applications.
I already checked all the memory map related
modifications. There seems to be nothing wrong...
--- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
> Actually, it's the other way around. If you are
> using DSPLink 1.3x, you
> *do* need to worry about the ARM-side stuff. DSPLink
> 1.4x onwards makes
> it easier for you, and the number of steps you need
> to perform are
> lesser.
> Can you go through the wiki once more to ensure
> you've made all the
> changes:
>
http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map
> #Rebuilding_DSP_Link_1.30
>
> Regards,
> Mugdha
>
> -Original Message-
> From: gather bzbz [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 4:03 PM
> To: Kamoolkar, Mugdha;
> davinci-linux-open-source@linux.davincidsp.com
> Subject: RE: Codec server loading error
>
> Yeah, 0x80008013 means param_out_of_range.
>
> I followed the sample in the wiki to change the
> memory map to 128M from
> 256M. I am using dsplink v1.30, so I think I do not
> need to worry about
> the ARM-side stuff (seems only dsplink v1.40 users
> should?). I will
> double-check my modifications again.
>
> Meanwhile, anyone succeeded in changing the memory
> map to 128M for
> video_copy test?
>
> Thank you all.
>
> --- "Kamoolkar, Mugdha" <[EMAIL PROTECTED]> wrote:
>
> > There's some problem in your memory configuration.
> > 0x80008013 is
> > DSP_ERANGE, which comes when the memory
> configuration of DSP
> > executable does not match ARM-side configuration.
> Hence loading the
> > DSP has failed.
> >
> > Regards,
> > Mugdha
> >
> > -Original Message-
> > From:
> >
>
[EMAIL PROTECTED]
> >
>
[mailto:[EMAIL PROTECTED]
> > On
> > Behalf Of gather bzbz
> > Sent: Friday, March 14, 2008 3:16 PM
> > To: davinci-linux-open-source@linux.davincidsp.com
> > Subject: Codec server loading error
> >
> >
> > Guys,
> >
> > I recompile the video_copy server to fit my new
> memory map, everything
>
> > looks good, then I copy the video_copy.x64P,
> app.out, in.dat to the
> > nfs server. After the board boots up, I get errors
> when I tried to run
>
> > the ./app.out
> >
> > app.out: ELF 32-bit LSB executable, ARM, version 1
> (SYSV), for
> > GNU/Linux 2.4.17, dynamically linked (uses shared
> libs), not strippd
> > [EMAIL PROTECTED]:/opt/# ./app.out
> > App-> Application started.
> > CE T:0x4003a6e8: Engine_open('video_copy', 0x0,
> > 0xbefffc3c)
> > CE T:0x4003a6e8: rserverOpen('./video_copy.x64P'),
> count = 0 OP
> > T:0x4003a6e8: Process_create('./video_copy.x64P',
> > 0xbefffc40)
> > OP T:0x40946b60: daemon()
> > OP T:0x40946b60: Process_create> Initializing DSP
> PROC...
> > OP T:0x40946b60: Process_create> Attaching to DSP
> PROC...
> > OP T:0x40946b60: Process_create> Opening MSGQ
> pool...
> > OP T:0x40946b60: Process_create> Loading
> ./video_copy.x64P on DSP (1
> > args)...
> > OP T:0x40946b60: Process_create> Operation FAILED,
>
> > status=-2147450861[0x80008013] OP T:0x40946b60:
> > Process_delete> Entered.
> > OP T:0x40946b60: Process_delete> Closing remote
> transport...
> > OP T:0x40946b60: Process_delete> Closing remote
> transport FAILED,
> > status=0x8000800b.
> > OP T:0x40946b60: Process_delete> Stopping DSP...
> > OP T:0x40946b60: Process_delete> Stopping DSP
> FAILED,
> > status=0x8000801b OP T:0x40946b60: Process_delete>
> Closing pool...
> > OP T:0x40946b60: Process_delete> Detaching from
> DSP...
> > OP T:0x40946b60: Process_delete> Destroying DSP...
> > (object, that is)
> > OP T:0x40946b60: putReply(0x2): proc = 0x1d3e8 OP
> > T:0x4003a6e8:
> > Process_delete(0x1d3e8) OP T:0x4003a6e8:
> > Process_delete(0x1d3e8) freeing
> > object ...
> > OP T:0x4003a6e8: Process_delete() Returning.
> > CE T:0x4003a6e8: rserverOpen('./video_copy.x64P'):
> > 0x1c634 done.
> > Assertion failed (((drvObj != NULL) &&
> (IS_OBJECT_VALID (drvObj,
> > SIGN_DRV))) || ((drvObj ==
> > NULL) && (cmdId == CMD_PROC_ATTACH))).6 OC
> T:0x4003a6e8:
> > Comm_create('video_copy', ...)
> > failed: status 0x80008002
> > CE T:0x4003a6e8: Engine_close(0x1d3b8) CE
> T:0x4003a6e8:
> > rserverClose(0x1c634), count = 1 OP
> > T:0x
u-boot splash on dm6446
Hi, all, anybody knows what the current u-boot splash image support for dm6446 is? I know that the code needed some modifications to display a splash image in the u-boot right after the power-on back a while ago. Were those modifications made public yet, by TI or by any nice people? Or we still need to go through the cycle ourselves? I check the u-boot 1.3.2 code, seems that CONFIG_XX_SPLASH_IMAGE needs a TI fb driver (hw_init) that does not exist. That flag compiles fine with older version but does not seem to do anything, even I specified the splashimage. Best to all. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
u-boot splash on davinci
Hi, all, anybody knows what the current u-boot splash image support for dm6446 is? I know that the code needed some modifications to display a splash image in the u-boot right after the power-on back a while ago. Were those modifications made public yet, by TI or by any nice people? Or we still need to go through the cycle ourselves? I check the u-boot 1.3.2 code, seems that CONFIG_XX_SPLASH_IMAGE needs a TI fb driver (hw_init) that does not exist. That flag compiles fine with older version but does not seem to do anything, even I specified the splashimage. Best to all. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Help! Davinci SYS_248 error!!
Hi, I cross_compiled a program that used to work on a x86 machine. everything
goes fine, but when launch the program, the program exits without any error
message. So I ran the strace and it showed that the last stack is SYS_248
unfinished with exit code 0.
Any help?
It is so similar to the problem reported here
http://linux.omap.com/pipermail/davinci-linux-open-source/2006-May/49.html
[root at davincievm:browser]# strace ./firefox
execve("./firefox", ["./firefox"], [/* 14 vars */]) = 0
uname({sys="Linux", node="davincievm", ...}) = 0
brk(0) = 0xab000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=17592186044416, ...}) = 0
mmap2(NULL, 31899, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4002
close(3)= 0
open("/lib/libncurses.so.5", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\30\335\0"..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0744, st_size=17592186044416, ...}) = 0
lseek(3, 224268, SEEK_SET) = 224268
read(3, "\24\0\0\0T\0\0\0\25\0\0\0MontaVista Software\0"..., 116) = 116
mmap2(NULL, 292240, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x40028000
mprotect(0x4005f000, 66960, PROT_NONE) = 0
mmap2(0x4006, 61440, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x30) = 0x4006
mmap2(0x4006f000, 1424, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4006f000
close(3)= 0
open("/lib/tls/libdl.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\324\t\0"..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0644, st_size=17592186044416, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4007
lseek(3, 4892, SEEK_SET)= 4892
read(3, "\24\0\0\0T\0\0\0\25\0\0\0MontaVista Software\0"..., 116) = 116
mmap2(NULL, 41104, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x40071000
mprotect(0x40073000, 32912, PROT_NONE) = 0
mmap2(0x40079000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x40079000
close(3)= 0
open("/lib/tls/libc.so.6", O_RDONLY)= 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0107\1\000"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=17592186044416, ...}) = 0
lseek(3, 1039100, SEEK_SET) = 1039100
read(3, "\24\0\0\0T\0\0\0\25\0\0\0MontaVista Software\0"..., 116) = 116
mmap2(NULL, 1091588, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x4007c000
mprotect(0x4017a000, 51204, PROT_NONE) = 0
mmap2(0x4017c000, 36864, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf8) = 0x4017c000
mmap2(0x40185000, 6148, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40185000
close(3)= 0
mprotect(0x40181000, 8192, PROT_READ) = 0
mprotect(0x4007a000, 4096, PROT_READ) = 0
mprotect(0x4001e000, 4096, PROT_READ) = 0
syscall_983045(0x40070d10, 0x2, 0x1, 0x4001f050, 0, 0x4001f050, 0x4001f3c8,
0, 0x4001f0a0, 0x4001f050, 0x4001f000, 0xbef
ff96c, 0, 0xbefff850, 0x40002784, 0x400102e4, 0x8010, 0x40070d10,
0xd0b0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
munmap(0x4002, 31899) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open("/dev/tty", O_RDWR|O_NONBLOCK|O_LARGEFILE) = 3
close(3)= 0
brk(0) = 0xab000
brk(0xac000)= 0xac000
brk(0xad000)= 0xad000
getuid32() = 0
getgid32() = 0
geteuid32() = 0
getegid32() = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
time(NULL) = 1072959157
brk(0xae000)= 0xae000
brk(0xaf000)= 0xaf000
open("/etc/mtab", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=4398046511104, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4002
read(3, "rootfs / rootfs rw 0 0\n/dev/root"..., 1024) = 402
close(3)= 0
munmap(0x4002, 4096)= 0
open("/proc/meminfo", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=4398046511104, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4002
read(3, "MemTotal:90584 kB\nMemFre"..., 1024) = 598
close(3)= 0
munmap(0x4002, 4096)= 0
brk(0xb)= 0xb
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL},
Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot
NO, u-boot has nothing to do with the IOCTL. it is the davincifb driver in the OS that causes trouble. There are other compatibility issues with the new SDK 1.3. Code migrations are needed.--- On Thu, 5/15/08, Gbzbz Gbzbz <[EMAIL PROTECTED]> wrote:> From: Gbzbz Gbzbz <[EMAIL PROTECTED]>> Subject: Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot> To: "davinci" , "Vim Venture" <[EMAIL PROTECTED]>> Date: Thursday, May 15, 2008, 1:10 PM> > cellspacing='0' cellpadding='0'> border='0'>> style='font:inherit;'>NO, u-boot has nothing to> do with the IOCTL. it is the davincifb driver in the OS> that causes trouble. There are other compatibility issues> with the new SDK 1.3. Code migrations are> needed.--- On Thu, 5/15/08,> Vim Venture> <[EMAIL PROTECTED]>> wrote:From: Vim> Venture> <[EMAIL PROTECTED]>Subject: Demos> not working in SDK 1.3, uBoot 1.2 does not> bootTo: "davinci"> Date:> Thursday, May 15, 2008, 7:30> PMHi everyone,I am> using the SDK v1.30 release on the DM6446, and none of the> demos will run for me.When I run the> decode demo, I get the following> > error.--[EMAIL PROTECTED]:/opt/dvsdk/dm6446#> ./decode -v data/> davincieffect_ntsc.m2vDecode demo> started.Decode Error: Failed to get the requested> screen size: 720x480 at 16 bppDecode Error: Failed> ioctl FBIOPUT_VSCREENINFO on> /dev/fb/0Total I-frames: 1, P-frames:> 2, B-frames: 0, IDR-frames: 0 rejected:> 0[EMAIL PROTECTED]:/opt/dvsdk/dm6446#--Similar> errors occur with the other demos. I am currently using> uBoot 1.1.3. The release notes for SDK 1.30 say> that an upgrade to uBoot 1.2 is needed, but my> DM6446 EVM will not boot with uBoot 1.2. It is > unresponsive and I have to revert back to 1.1.3> with DVFlasher to get a proper boot. I'm> not sure if these 2 problems are related. Could > the version of uBoot affect> FBIOPUT_VSCREENINFO?My boot-time video> args are> set as:video = dm6446fb:vid0> = 720x480x16,2025K @0,0> :vid1=720x480,[EMAIL PROTECTED],0:osd0=720x480,[EMAIL PROTECTED],0:osd1=720x480,[EMAIL PROTECTED],0Has> anyone else bumped into this> problem?Regards,-Vim___Davinci-linux-open-source> mailing> listDavinci-linux-open-source@linux.davincidsp.comhttp://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source> > > > > > ___> Davinci-linux-open-source mailing list> Davinci-linux-open-source@linux.davincidsp.com> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot
NO, u-boot has nothing to do with the IOCTL. it is the davincifb driver in the OS that causes trouble. There are other compatibility issues with the new SDK 1.3. Code migrations are needed. --- On Thu, 5/15/08, Gbzbz Gbzbz <[EMAIL PROTECTED]> wrote: From: Gbzbz Gbzbz <[EMAIL PROTECTED]> Subject: Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot To: "davinci" , "Vim Venture" <[EMAIL PROTECTED]> Date: Thursday, May 15, 2008, 1:10 PM NO, u-boot has nothing to do with the IOCTL. it is the davincifb driver in the OS that causes trouble. There are other compatibility issues with the new SDK 1.3. Code migrations are needed. --- On Thu, 5/15/08, Vim Venture <[EMAIL PROTECTED]> wrote: From: Vim Venture <[EMAIL PROTECTED]> Subject: Demos not working in SDK 1.3, uBoot 1.2 does not boot To: "davinci" Date: Thursday, May 15, 2008, 7:30 PM Hi everyone, I am using the SDK v1.30 release on the DM6446, and none of the demos will run for me. When I run the decode demo, I get the following error. -- [EMAIL PROTECTED]:/opt/dvsdk/dm6446# ./decode -v data/ davincieffect_ntsc.m2v Decode demo started. Decode Error: Failed to get the requested screen size: 720x480 at 16 bpp Decode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 Total I-frames: 1, P-frames: 2, B-frames: 0, IDR-frames: 0 rejected: 0 [EMAIL PROTECTED]:/opt/dvsdk/dm6446# -- Similar errors occur with the other demos. I am currently using uBoot 1.1.3. The release notes for SDK 1.30 say that an upgrade to uBoot 1.2 is needed, but my DM6446 EVM will not boot with uBoot 1.2. It is unresponsive and I have to revert back to 1.1.3 with DVFlasher to get a proper boot. I'm not sure if these 2 problems are related. Could the version of uBoot affect FBIOPUT_VSCREENINFO? My boot-time video args are set as: video = dm6446fb:vid0 = 720x480x16,2025K @0,0 :vid1=720x480,[EMAIL PROTECTED],0:osd0=720x480,[EMAIL PROTECTED],0:osd1=720x480,[EMAIL PROTECTED],0 Has anyone else bumped into this problem? Regards, -Vim ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot
Yes. At least it is broken with old demos from all the vendors, including TI itself. Fixing those may not be hard at all though. --- On Thu, 5/15/08, Vim Venture <[EMAIL PROTECTED]> wrote: > From: Vim Venture <[EMAIL PROTECTED]> > Subject: Re: Demos not working in SDK 1.3, uBoot 1.2 does not boot > To: "gather bzbz" <[EMAIL PROTECTED]> > Cc: "davinci" > Date: Thursday, May 15, 2008, 1:34 PM > Thanks for the reply, > > Are you saying that the SDK 1.3 demos just plain don't > work yet? > If that is the case, I should switch back to the SDK v1.2. > > -Vim > > > On May 15, 2008, at 1:26 PM, gather bzbz wrote: > > > NO, u-boot has nothing to do with the IOCTL. it is the > davincifb > > driver > > in the OS that causes trouble. There are other > compatibility issues > > with the new SDK 1.3. Code migrations are needed. > > > > > > --- On Thu, 5/15/08, Gbzbz Gbzbz > <[EMAIL PROTECTED]> wrote: > > From: Gbzbz Gbzbz <[EMAIL PROTECTED]> > > Subject: Re: Demos not working in SDK 1.3, uBoot 1.2 > does not boot > > To: "davinci" > , > "Vim > > Venture" <[EMAIL PROTECTED]> > > Date: Thursday, May 15, 2008, 1:10 PM > > > > NO, u-boot has nothing to do with the IOCTL. it is the > davincifb > > driver in the OS that causes trouble. There are other > compatibility > > issues with the new SDK 1.3. Code migrations are > needed. > > > > --- On Thu, 5/15/08, Vim Venture > <[EMAIL PROTECTED]> wrote: > > From: Vim Venture <[EMAIL PROTECTED]> > > Subject: Demos not working in SDK 1.3, uBoot 1.2 does > not boot > > To: "davinci" > > > Date: Thursday, May 15, 2008, 7:30 PM > > > > Hi everyone, > > I am using the SDK v1.30 release on the DM6446, and > none of the demos > > will run for me. > > When I run the decode demo, I get the following > > error. > > > > > -- > > [EMAIL PROTECTED]:/opt/dvsdk/dm6446# ./decode -v data/ > > davincieffect_ntsc.m2v > > Decode demo started. > > Decode Error: Failed to get the requested screen size: > 720x480 at 16 > > bpp > > Decode Error: Failed ioctl FBIOPUT_VSCREENINFO on > /dev/fb/0 > > > > Total I-frames: 1, P-frames: 2, B-frames: 0, > IDR-frames: 0 rejected: 0 > > [EMAIL PROTECTED]:/opt/dvsdk/dm6446# > > > -- > > > > Similar errors occur with the other demos. I am > currently using uBoot > > 1.1.3. The release notes for SDK 1.30 say that an > upgrade to uBoot > > 1.2 is needed, but my DM6446 EVM will not boot with > uBoot 1.2. It is > > unresponsive and I have to revert back to 1.1.3 with > DVFlasher to get > > a proper boot. I'm not sure if these 2 problems > are related. Could > > the version of uBoot affect FBIOPUT_VSCREENINFO? > > > > My boot-time video args are > > set as: > > video > > = > > dm6446fb:vid0 > > = > > 720x480x16,2025K > > @0,0 > > > :vid1=720x480,[EMAIL PROTECTED],0:osd0=720x480,[EMAIL > PROTECTED],0:osd1=720x480,[EMAIL PROTECTED],0 > > > > Has anyone else bumped into this problem? > > > > Regards, > > -Vim > > > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > > > > > > > > > > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > > > > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Anyone see this month's Embedded Systems Design?
Actually the knowledges on the Linux side will sooner or later _OR_ more or less become public assets. The difficult part of almost every embedded project resides in the vendor specific portion. Like for davinci, it is not TCP/IP that causes confusions, it is the davincifb, resizer, dsplink, cmemk, codecs (etc) that frustrates people. With companies like greenhill, you are working at their mercy, pay or not. --- On Fri, 5/16/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > Subject: Re: Anyone see this month's Embedded Systems Design? > To: [EMAIL PROTECTED] > Cc: davinci-linux-open-source@linux.davincidsp.com > Date: Friday, May 16, 2008, 11:51 AM > On Fri, 16 May 2008, [EMAIL PROTECTED] wrote: > > Is there any alternative to Linux? I can see none. > Montavista is not > sacred--as a matter of fact I personally don't like > it--but it is one of > almost infinite choices and do respect their work. Their > weakness grows > directly from their strength--they are trying to support > almost every CPU on > this planet that is capable of running Linux. It is mission > impossible but > it deserves highest respect. I don't think any company > on this planet > could've done better dealing with such an enormous > task. > > Yes, it is much easier to write and maintain a crippled > weirdo, limited in > every respect, for a couple of CPUs. But that is nothing to > be proud of > engineeringwise; it's several orders of magnitude > simpler task. Also it is > single vendor weirdo, without source code, with royalties > at every corner > and licence fees for every sneeze. It might be OK for those > who love > communism with its total absence of choice and relative and > very > questionable stability and simplicity. Linux, on the other > hand, is pure > capitalism at its very best--full freedom but much less > guarantees. All > those GPLx licences don't make it socialistic contrary > to popular belief and > to what all those commercial vendors are trying to make > people believe. It's > exactly the opposite. > > They are simply loosing that battle... And there is no a > single entity they > could sue :) > > > Green Hills goes medeval on linux (targeted directly > at Montavista) in > > this article: > > http://www.embedded.com/columns/guest/207402542 > > > > Montavista replies with this article: > > http://www.embedded.com/columns/guest/207602734 > > > > The sad thing is that our development team has had an > experience more > > similar to the first article, so there is some merit > to his blatently > > agenda driven view. > > Hopefully that will turn around in the near future... > > > > Regards, > > David > > > > DAVID A. KONDRAD > > Software Design Engineer > > On-Q/Legrand > > www.onqlegrand.com > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > > > --- > ** > * [EMAIL PROTECTED]KOI8 Net < > The impossible we do > immediately. * > * Las Vegas NV, USA < > Miracles require > 24-hour notice. * > ** > ___ > Davinci-linux-open-source mailing list > Davinci-linux-open-source@linux.davincidsp.com > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
MPEG4ENC puzzles
Trying to get mpeg4enc codecs to work.. I use the codec_servers_1_23 from dvevm_1_20 and copy the .l64P from 100e_v_mpeg4_dm644x_e_1_20.zip. At the end of the compiling, I get >> package/cfg/Srv1_x64P.xdl, line 357: warning: multiple definitions of SECTION named '.intDataMem' >> package/cfg/Srv1_x64P.xdl, line 295: warning: (.text:_MP4VENC_TI_Pre_meFrame_highQuality) not found >> package/cfg/Srv1_x64P.xdl, line 296: warning: (.text:_MP4VENC_TI_Pre_meFrame_highSpeed) not found >> package/cfg/Srv1_x64P.xdl, line 298: warning: (.text:_MP4VENC_TI_mad_4x4) not found >> package/cfg/Srv1_x64P.xdl, line 299: warning: (.text:_MP4VENC_TI_vectmin) not found >> package/cfg/Srv1_x64P.xdl, line 300: warning: (.text:_MP4VENC_TI_mad_hx16_skip2) not found >> package/cfg/Srv1_x64P.xdl, line 301: warning: (.text:_MP4VENC_TI_mad_hx16) not found >> package/cfg/Srv1_x64P.xdl, line 309: warning: (.text:_MP4VENC_TI_frame_ME_P_host) not found >> package/cfg/Srv1_x64P.xdl, line 311: warning: (.text:_MP4VENC_TI_halfsearch) not found >> package/cfg/Srv1_x64P.xdl, line 312: warning: (.text:_MP4VENC_TI_sad_halfpel) not found The server binary Srv1.x64P was generated. But when try to use mpeg4enc, the codecs engine fails. So I guess the mpeg4enc portion was not generated correctly due to the error shown above. All other codecs (h264 enc/dec, mpeg4dec,etc all work fine). So the questions are 1. are these errors due to incompatiblity between the shipped lib (.l64P) and the mpeg4enc link.xdt in the codec_servers_1_23 from dvevm package? Is there any mpeg4enc xdc package available that works without "hacks"? 2. I looked at the dm6446_dvsdk_combos_1_01 from TI's site, inside that package, there is no link.xdt and nothing from dm6446_dvsdk_combos_1_01 compiles? 3. Worst case, how can we fix the above errors? I guess I am the one that is confused by the TI software and codecs packaging/releasing process. codec_servers_1_23 has the xdc packages without library, while 100e_v_mpeg4_dm644x_e_1_20.zip has the library without xdc package, when you put them together, the marriage does not work? ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
(no subject)
I am experimenting different H.264 codecs with TI DVEVM's encode demo.
I use one H.264 codecs first, generate the demo, run it, and write the encoded
frames to a file (test1.264). Also note down the OSD info, like ARM load, DSP
load, FPS, bit rate, etc.
Then I use another H.264 codecs (also from TI, but with another revision),
generate the demo, then repeat the same steps. except that I write to
test2.264, this time.
Everything looks "exactly" the same (OSD info, file size, etc). However, a file
analysis on test1.264 and test2.264 shows big difference!
test1.264 (JVT NAL sequence, H.264 video, baseline @ L 30)
test2.264 (JVT NAL sequence)
Then, as a consequence, I can play test1.264, but not test2.264.
So is it because codecs 2 was not set up right? VIDENC_process("h264enc") all
worked out ok without complaints
Thank you all
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
