This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Looking at that code, I am not sure it should be included in the kernel build. I am guessing that your kernel config is not correct. This Linux source tree has the file am3517_evm_defconfig from which you can start with. That config file probably won't exactly match your EVM. Compare that config file with one from your EVM manufacturer.
Dear All, I have been running through a problem .. my kernel image starts booting and stops at starting kernel..... Configuration selected for creating uImage is am3517_evm_defconfig. i have referred this site http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux#Problem_.232_-_No_more_output_is_seen_on_the_console_after_.22booting_the_kernel.22 but trying all the changes mentioned in the above site ..has not helped me.. 1.Using the defconfiguration -> i changed the bootargs 'console=ttyS2,115200n8' 2.changing the bootargs for 2.6 -> 'console=ttyS2,115200n8' O=not zero The output is as below.... Texas Instruments X-Loader 1.47 (Mar 24 2011 - 15:54:47) Booting from nand . . . Starting OS Bootloader... U-Boot 2010.06-rc1 (Mar 24 2011 - 15:55:56) OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz TAM3517 TWISTER Board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 256 MiB In: serial Out: serial Err: serial Customer/Vender : TechNexion Project/Board : tam3517 Sequence Number : 1052000000000069 revision : TN15 1.0 eth0 addr : 00:1F:7B:15:01:10 eth1 addr : 00:1F:7B:15:01:11 eth2 addr : 00:1F:7B:15:01:12 eth3 addr : 00:1F:7B:15:01:13 Die ID #30e20000000000000155dc140400f016 Net: Ethernet PHY: GENERIC @ 0x00 DaVinci EMAC, smc911x-0 Hit any key to stop autoboot: 1 0 Using DaVinci EMAC device TFTP from server 192.168.1.233; our IP address is 192.168.1.54 Filename 'uImage'. Load address: 0x80008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######## done Bytes transferred = 2369032 (242608 hex) ## Booting kernel from Legacy Image at 80008000 ... Image Name: Linux-2.6.33.7-rt29 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2368968 Bytes = 2.3 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK XIP Kernel Image ... OK OK Starting kernel ...
The default kernel config is for the EVM. It seems you have a different board:
>Customer/Vender : TechNexion Project/Board : tam3517
Are you sure you can run that with the same kernel config?
Regards.
Ps> any chance you can get your Carriage Return issue fixed so that we can all read your comments more easily?
I took a look at the resources at the TechNexion website. They have a Linux kernel based up TI's PSP-03.00.01.06. The archive is called xuk-src.tar.bz2. That file is included with the BSP that came with the board. It is also available as 58MB download from their site.
The Linux kernel source in xuk-src.tar.bz2 is supposed to contain Angstrom and Android default configs for your board. I would guess that the Angstrom default config is closest to the DVSDK/OMAP distro you are trying to compile. Your board appears to the twister rather than the thb3517 so the default file should be tam3517_twister_defconfig.
Compare tam3517_twister_defconfig and the am3517_evm_defconfig. If you are lucky and there are not many changes, you should be able to copy the changes from tam3517_twister_defconfig over to am3517_evm_defconfig.
Even then, you will probably have to port over tam3517 specific code into the OMAP kernel. That might be quite involved as you might have add a new board type to the kernel build system. Maybe applying RT patches to the existing TechNexion might be easier. I don't know.
Dear Norman !
Thanks for your reply!
I have provided the same source code along with the tam3517, and i am able to boot with it. the default configuration i am selecting is tam3517_twister_defconfig.
with this configuration i have booted through SDcard .
But as you said i can compare the two config files :
1.The RTLinux source code downloaded from Git source tree which provides am3517_evm_defconfig
2.xuk-src.tar.gz -->tam3517_twister_defconfig
now, when i make any changes manually to the configuration file the compilation ends with error.
I compared the two configuration files there are not much changes
[root@localhost kernel]# make ARCH=arm am3517_evm_defconfig
#
# configuration written to .config
#
[root@localhost kernel]# make
[root@localhost linux-omap3]# make ARCH=arm CROSS_COMPILE=/home/Linux/Sourcery/arm-2010.09/bin/arm-none-linux-gnueabi- uImage modules
now for the default configurations the compilation is without error but the when i boot the kernel image it stucks at .....starting kernel.
Texas Instruments X-Loader 1.47 (Mar 24 2011 - 15:54:47)
Booting from nand . . .
Starting OS Bootloader...
U-Boot 2010.06-rc1 (Mar 24 2011 - 15:55:56)
OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
TAM3517 TWISTER Board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Customer/Vender : TechNexion
Project/Board : tam3517
Sequence Number : 1052000000000069
revision : TN15 1.0
eth0 addr : 00:1F:7B:15:01:10
eth1 addr : 00:1F:7B:15:01:11
eth2 addr : 00:1F:7B:15:01:12
eth3 addr : 00:1F:7B:15:01:13
Die ID #30e20000000000000155dc140400f016
Net: Ethernet PHY: GENERIC @ 0x00
DaVinci EMAC, smc911x-0
Hit any key to stop autoboot: 1 0
Using DaVinci EMAC device
TFTP from server 192.168.1.233; our IP address is 192.168.1.54
Filename 'uImage'.
Load address: 0x80008000
Loading: *#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
########
done
Bytes transferred = 2369032 (242608 hex)
## Booting kernel from Legacy Image at 80008000 ...
Image Name: Linux-2.6.33.7-rt29
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2368968 Bytes = 2.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
what could be the problem...
I read that if the u-boot id and mach id [kernel ] is difft then it can create problem but how to confirm the ids are difft.
I don't think matching mach IDs would get you much further. It is very likely that there are major HW differences as well.
I suggest you diff the TechNexion and TI kernel source. Then port over the TAM3517 changes into the TI kernel source. You will be essentially adding support for the TAM3517 board in the TI kernel. The idea is that you will make a tam3517_twister kernel and not a modified am3517_evm kernel. Try to leave the AM3517 code unchanged. Possible files to look out for:
arch/arm/tools/mach-types
- check that TAM3517 is in the list.
include/generated/mach-types.h
- auto-generated file, check that TAM3517 macros are here
arch/arm/configs/tam3517_twister_defconfig
- TI's am3517_evm_defconfig and TechNexion's tam3517_twister_defconfig merged together
- pay attention to the order of CONFIG options. They must match the order in Kconfig
arch/arm/mach-omap2/Kconfig
- add config option for TAM3517
- should be able to copy from TechNexion version
- pay attention to the order of CONFIG options. They must match the other in defconfig
arch/arm/mach-omap2/Makefile
- add in target for TAM3517
- should be able to copy from TechNexion version
There will changes to other files and new files. An important one will be the pinmux configuration.
Dear Norman !
Thank you very Much !
I have started working on your suggestions.
Thanks and regards
Hrishikesh!