Dear TI E2E Community
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.
Dear TI E2E Community
Hi Srini,
Welcome to our TI E2E forum, here you surely you would get immediate response for your question and technical clarifications.
Sorry for the delayed response.
1. As am newbie in using ti-sdk-am335x-evm-07.00.00.00 where we have uboot & kernel source code , when am trying to modify the uboot & kernel source code ie., am trying to add printks in the source code , compiled & flashed the images onto SD card but am unable to see the print messages that I have added onto the serial console,
Could any body please let me know why I am unable to see the print messages onto the console or am I missing any uboot or kernel configurations that is to be done inorder to see the print messages onto the console
Could you please tell me, which file have you changed for your new printf function.
Those changes were applied in MLO or u-boot or kernel source code ?
Have you confirm that you have booted with latest modified binaries by compilation date ?
If linux kernel,
Have you enabled "kernel bootup log" option in kernel through "make menuconfig" option ?
2. As am newbie to device tree concept as earlier was using board files, Could any body please let me know what is the difference between board file & device tree,Could any body please help me do how to gain the quick understanding of device tree in uboot & linux kernel ti-sdk-am335x-evm-07.00.00.00 & what is significance of uboot & kernel device tree when it would be required & how to modify it
Could you please let me know whether do we have device tree or board file concept in ti-sdk-am335x-evm-07.00.00.00 for both uboot & kernel & the path used for the same
Could you please let me know do we have source code for SPL in uboot , could you please let me know the source code path for the same
Hi Titus,
Thanks a lot for your replies it is very helpful,
As of now am using beaglebone black evm board with ti sdk ti-sdk-am335x-evm-07.00.00.00,
Regarding the prink messages onto the console,
Am adding the printk in the path /linux-3.12.10-ti2013.12.01/drivers/iio/adc/ti_am335x_adc.c
static int tiadc_probe(struct platform_device *pdev)
{
struct iio_dev *indio_dev;
struct tiadc_device *adc_dev;
struct device_node *node = pdev->dev.of_node;
struct property *prop;
const __be32 *cur;
int err;
u32 val;
int channels = 0;
printk(KERN_ERR "ADC TIIIIIIIIIIIIIIIIIIIIIIII \n");
Am unable to get this print message onto the console
I did the below kernel configuration also
1. Inorder to get printk
[*] Kernel low-level debugging functions (read help!) x x
x x Kernel low-level debugging port (Kernel low-level debugging messages via AM33XX UART1) ---> x x
x x [*] Early printk
2. Even adc related configuration is also enabled as shown below
<*> TI's AM335X ADC driver
Basically I am trying to make use of am335x internal adc in this sdk ie., ti-sdk-am335x-evm-07.00.00.00,
Could you please do the needful how this can be resolved ie., printk messages onto the console & please provide how to make use & verify TI's AM335X ADC driver in this sdk
But Am335x internal adc drivers guide which is in net doen't help for this sdk for whichever am using
Could you please do the needful in resolving this issue as early as possible as am stuck with this from more than 15 days
Kindly do the needful,
Awaiting for your replies,
Many Thanks in advance again
Hi Srini,
No worries.
Regarding the prink messages onto the console,
Am adding the printk in the path /linux-3.12.10-ti2013.12.01/drivers/iio/adc/ti_am335x_adc.c
Have you tried "dmesg" command to see the print?
You can also use
printk("ADC TIIIIIIIIIIIIIIIIIIIIIIII\n");
1) Have you seen "ti_am335x_adc.o" object files on the same directory ?
2) After building the kernel, do any change on the same file and check that file compiling or not while building the kernel after modification.
Please attach your complete linux bootup log.
make menuconfig ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
Kernel hacking --->
printk and dmesg options --->
[*] Show timing information on printks
(4) Default message log level (1-7)
[*] Delay each boot printk message by N milliseconds
[*] Enable dynamic printk() support