I didn't succed to boot the DVSDK 3.10_19 uImage on my leopard board (dm365)
I try the uImage-dm365-evm.bin from the download page and I also try to build it.
can you send me your .config or/and give me some explanation how to do this ?
I didn't succed to boot the DVSDK 3.10_19 uImage on my leopard board (dm365)I try the uImage-dm365-evm.bin from the download page and I also try to build it.
I have included my kernel .config file to my TI forum profile http://e2e.ti.com/members/1347615/default.aspx
Is this still available? I don't see it at the given URL.
the file you are looking for is on TI's community page:
thanks, I found it right where you said it'd be. Now I have to understand using it.
I downloaded linux-davinci-staging.tar.gz from the 3.10.00.19 Product Download page. tar -zxvf-ed it and got a ./git dir below my download dir.
There must be 200 "*config*" files in ./git, but no config.config nor a kernel.config. What do I do with your config.config file?
Then, what should I specify on the ./git/configure line to get this thing built?
Also, you reference arago-demo-image-dm365-evm.tar.gz If that is your filesys, why do you also mention DVSDK 3.10 for the DM365EVM. Do I need both? Where might I find build instructions for these? I assume they are similar to the ones in the TI Getting Started Gide?
Sorry to be so dim.
Hi Mike, Chris,
I downloaded the PSP Linux Kernel Source from the link in my last post. You will need to register at TI's homepage to get the DVSDK 3.10 for the DM365EVM. The Leopardboard is pretty the same board as the EVM from TI. Some parts are missing, like the S-Video decoder. But you can disable the TVP51xx in the kernel.
I am using NFS to boot my Linux FS (arago-demo-image-dm365-evm.tar.gz).For the networkcard the right network adapter/PHY has to be enabled:
the last time I worked with the Leopardboard and the DVSDK is a while ago...
The config file I put into my folder is made to configure a certain DM365 EVM board's kernel (2.6.32-rc2-davinci1) to run on the Leopardboard. The config file enables, I think, the network adapter and the USB stuff... But there is more to that.
Every bootloader (like TI's UBL or U-Boot) sends parameter to the kernel, like a MACHINE_ID, which differs between the Leopardboard and TI's EVM. If the kernel does not recognize the MACHINE_ID, because it was build for a different board, it won't start at all and without giving you notice why it doesn't start.
I invested a lot of work in writing my own bootloader, which gets the kernel from NAND or UART and sends my own MACHINE_ID. If you want to do that you will need good literature. I recommend the kernel's help files located in the document folder.
But the best way to get started with a new development platform is using its software development kit, and only its designated development kit. The TI's kit won't work, because of different MACHINE_ID and also different periferal hardware and wirring of the processor. But back in the days two companies offered theire leopardboard adapted software development kits to the TI community. And I think they still do.