TDM Driver and Test on P1020RDB-PD

[naumgrutman]

I am trying to exercise/test the TDM capabilities on P1020RDB-PD

I have followed the Chapter 7.17 within SDK1.9 Manual

Updated Kernel Configure Tree options

Updated default configuration file: mpc85xx_smp_defconfig

Updated device tree file: p1020rdb-pd_32b.dts

Manual mentioned that I should see something similar to the following:

...

...

EDAC MC: Ver: 2.1.0

fsl_tdm: Freescale TDM Driver Adapter:Init

adapter [fsl_tdm] registered

SLIC: FREESCALE DEVELOPED ZARLINK SLIC DRIVER

####################################################

# This driver was created solely by Freescale,     #

# without the assistance, support or intellectual  #

# property of Zarlink Semiconductor. No            #

# maintenance or support will be provided by       #

# Zarlink Semiconductor regarding this driver.     #

####################################################

SLIC probed!

SLIC config success

SLIC: product code 1 read is 4

SLIC: product code 2 read is b3

SLIC: config read is ff

SLIC: config read is 8a

DEV reg is 82

DEV reg after is 2

Mask reg before setting is 3f bf

Mask reg after setting is f6 f6

Read Tx Timeslot for CH1 is 0

Read Tx Timeslot for CH2 is 2

Read Rx Timeslot for CH1 is 0

Read Rx Timeslot for CH2 is 2

Operating Fun for channel 1 is 82

Cadence Timer Reg for CH1 before is 7 ff0 0

Cadence Timer Reg for CH1 after is 1 903 20

Switching control for channel 1 is 20

Operating Fun for channel 2 is a0

Cadence Timer Reg for CH2 before is 7 ff0 0

Cadence Timer Reg for CH2 after is 1 903 20

Switching control for channel 2 is 20

SLIC 1 configuration success

TDM_TEST: Test Module for Freescale Platforms with TDM support

TDM_TEST module installed

...

...

I am getting:

devtmpfs: initialized

NET: Registered protocol family 16

tdm_init

Found FSL PCI host bridge at 0x00000000ffe09000. Firmware bus number: 0->1

PCI host bridge /pcie@ffe09000 (primary) ranges:

Maybe somebody can point out what else needs to be configured…

Please find files attached

Thanks,

Naum

Original Attachment has been moved to: P1020RDB_with_TDM_BootUp.txt.zip

Original Attachment has been moved to: p1020rdb-pd_32b.dts.zip

Original Attachment has been moved to: mpc85xx_smp_defconfig.zip

[naumgrutman]

Hello Yiping,

To continue my previous response...

I have taken your Kernel image and your .DTB image and copied them over mine on the SDcard

I have booted the system up using your Kernel and .DTB and go

The comparison .DOC file is attached...

Also I have included into this message one of the .JPG files

There is something additional that is strange about my setup: Since I switched to bootup from SDcard

I started etting these funny characters "üüàüüüüààüüüàààüàüü" when I was booting from SATA drive

I did not have any funny characters... Maybe you can shed some light on that also...

Thanks,

Naum

[yipingwang]

Hello Naum Grutman,

I am transcending all the images to you, please pay attention to your email box to download it.

Please refer to to u-boot environment(hwconfig) and switch setting.

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[naumgrutman]

Hello Yiping,

I have the following question...

I am using SDK 1.9  which supports P1020RDB-PD... U-Boot and Linux Kernel... everything is working

just fine so far SDK 1.9 includes Linux Kernel 3.12

The SDK 2.0 includes Linux Kernel 4.1 but does not look like P1020RDB-PD is included in SDK2.0

Is there a documentation or sequence of steps to have the Linux Kernel for P1020RDB-PD moved up

i.e. upgraded to Linux 4.1 level or higher... just like is available within SDK 2.0

Thanks,

Naum

[yipingwang]

Hello Naum,

SDK 2.0 Linux Kernel doesn't provide TDM driver.

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[naumgrutman]

Yiping,

Even though the SDK 2.0 Linux Kernel and Linux Kernel 4.1 within it

do not provide the TDM driver...

1. Is it possible to have kernel for P1020RDB-PD upgraded to 4.1 or higher level...?

2. Are there any special steps to achieve it...?

3. Is there a document describing the Upgrade steps...?

Thanks,

Naum

[yipingwang]

Hello Naum,

SDK 2.0 doesn't support P1020RDB either, SDK 1.9 is still recommended to use.

Thanks,

Yiping

[naumgrutman]

Yiping,

1. Is it possible to have kernel for P1020RDB-PD upgraded to 4.1 or higher level...?

2. Are there any special steps to achieve it...?

3. Is there a document describing the Upgrade steps...?

My questions are NOT about SDK 2.0...

I would like to continue using SDK 1.9

but at the same time is it possible to upgrade Linux Kernel within it to 4.0 or higher

or are we stuck at Linux Kernel 3.12 level...???

Thanks,

Naum

[naumgrutman]

Hello Yiping,

You can ignore my previous question...

I was able to answer my own question in regards to U-Boot of the size 768KB

I have loaded U-Boot at the address 0xEFF40000 and everything works just fine...

Thanks again

Naum

[naumgrutman]

Hello Yiping,

I have a few quick questions...

The original P1020RDB-PD box came with the U-Boot that is located at 0xEFF8.0000 address

and its original size is 512KB thru 0xEFFF.FFFF

with the U-Boot parameters stored at 0xEFF6.0000

I have attached files containing portions of memory dumps to this  message

My questions are....

I have rebuilt the U-Boot using the SDK 1.9 that is binary matching yours... ( obviously with the only difference - the time stamp )

the size of this new U-boot that is created by the SDK1.9 is 768KB... and is matching yours U-Boot of the size 768KB perfectly...

Obviously this new U-Boot would not fit into the area of 0xEFF8.0000 thru 0xEFFF.FFFF

1. What is the address where your new U-Boot of the size 768KB is located??? and should be flashed into...???

2. And what is the address where the new U-Boot parameters are located???

3. Can you provide me a similar U-Boot memory dump that will indicate its memory location etc...

Thanks again,

Naum

[naumgrutman]

Hello Yiping,

Thank you for the images... and u-boot parameters...

Using your images I could bring up the system exactly the same way as you have...

So the differences are the fact that I was booting via SDcard and using  fsl-image-full

So I have created fsl-image-core

If I take my kernel and my fsl-image-core and load them in the same fashion as you are

via NOR ramboot  then booting goes smoothly and no funny characters...

I can proceed with the TDM testing...

I will have to figure out what was wrong with SDCard / fsl-image-full combo...

Thank you for you help...

Regards,

Naum

If I have additional question... I will let you know...

[naumgrutman]

Hello Yiping,

I have binary compared your .dtb and mine and they are the same so the .dts must have been the same...

I have compared .config files yours and mine and they are the same also...

I have compared your log and mine and provided the comparison results in the attached .DOC file...

Please correct me if I am wrong but it looks to me that all the red lines on the left side in the second part of your log

are coming from rootfs... I was under impression that and as per manual the items I was looking for to appear

are or should have been a part of NEW kernel image... but it looks to me that they are coming from your rootfs

So is this correct...? New rootfs needs to be supplied...?

Would it be possible for you to attach your zipped U-boot; U-boot parameters; and

zip of your Rootfs... if it is not too much trouble...

Thanks,

Naum

[yipingwang]

Hello Naum Grutman,

I built images with your Kernel configuration and dts file, and verified on my target board without problem, please refer to the attached log.

I attached my built images, please do verification on your target board.

It seems that your Kernel image is not coincident with the configuration file, please rebuild Kernel image with attached config_tdm file.

Have a great day,

Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[naumgrutman]

Hello Yiping,

You can ignore my previous question...

I was able to answer my own question in regards to U-Boot of the size 768KB

I have loaded U-Boot at the address 0xEFF40000 and everything works just fine...

Thanks again,

<http://www.rugged.com/>

Naum Grutman

Tel: ( 818 ) 700-2000 Ext. 163

Fax: ( 818 ) 407-1502

Address: 19756 Prairie St. Chatsworth, CA.91311

E-mail: ngrutman@rugged.com<mailto:ngrutman@rugged.com>

Website: www.rugged.com<http://www.rugged.com/>;

Embedded Computing without Compromise

[naumgrutman]

Hello Yiping,

I have a few quick questions...

The original P1020RDB-PD box came with the U-Boot that is located at 0xEFF8.0000 address

and its original size is 512KB thru 0xEFFF.FFFF

with the U-Boot parameters stored at 0xEFF6.0000

I have attached files containing portions of memory dumps to this message

My questions are....

I have rebuilt the U-Boot using the SDK 1.9 that is binary matching yours... ( obviously with the only difference - the time stamp )

the size of this new U-boot that is created by the SDK1.9 is 768KB... and is matching yours U-Boot of the size 768KB perfectly...

Obviously this new U-Boot would not fit into the area of 0xEFF8.0000 thru 0xEFFF.FFFF

1. What is the address where your new U-Boot of the size 768KB is located??? and should be flashed into...???

2. And what is the address where the new U-Boot parameters are located???

3. Can you provide me a similar U-Boot memory dump that will indicate its memory location etc...

Thanks again,

<http://www.rugged.com/>

Naum Grutman

Tel: ( 818 ) 700-2000 Ext. 163

Fax: ( 818 ) 407-1502

Address: 19756 Prairie St. Chatsworth, CA.91311

E-mail: ngrutman@rugged.com<mailto:ngrutman@rugged.com>

Website: www.rugged.com<http://www.rugged.com/>;

Embedded Computing without Compromise

[naumgrutman]

Hello Yiping,

I suspect that the issue might be the p1020rdb-pd_32b.dts file

would it be possible for you to attach the p1020rdb-pd_32b.dts file that you have used.

I assume that p1020rdb.conf you left the same as it appears in SDK

if not please attach this one also...

Thanks,

Naum