topic Re: i.MX28 On-Board Diagnostics Suite (OBDS) in i.MX Processors

i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Tue, 01 Jul 2014 11:02:41 GMT

Hi Qiang_FSL , raymondwang, igorpadykov YuriMuhin_ng YixingKong fernandolopes lategoodbye GraceH

I am using i.MX28 On-Board Diagnostics Suite (OBDS) to test memory,uart,can,usb etc of my MCIMX28EVK board.

I have followed the commands specified in the pdf available with imx28 OBDS Source.

Since I am using linux , I followed this step

./tools/linux/build_obds.sh

The above command created diag-obds-mx28evk.bin, diag-obds-mx28evk.elf, mx28-obds.sb, ipl files in output/mx28/bin folder.

I have used the steps specified in the pdf to program .sb file to sd card

./tools/windows/cfimager.exe \-f ./output/mx28/bin/mx28-obds.sb \-d g -a

But the command failed.

run-detectors: unable to find an interpreter for ./tools/windows/cfimager.exe

How to load this boot stream image to sd card?

Does the obds test need rootfs image?

Regards

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

igorpadykov — Tue, 01 Jul 2014 11:27:32 GMT

Hi Pt

it is Windows utility, not Linux.

Best regards

chip

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

fernandolopes — Tue, 01 Jul 2014 11:27:39 GMT

Hi pt.

The OBDS has nothing related to a rootfs or even linux. It is just a simple code that is loaded and runs directly from ram.

If you want to load a .sb image to an sd card on a linux environment, you probably want to use the linux cfimager instead of the windows .exe version!

BR,

Fernando.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Tue, 01 Jul 2014 11:34:51 GMT

Hi fernandolopes

The linux cfimager is missing in imx_28_obds_release_v1_0 . I have searched for it ,but only windows cfimager is available.

Regards

Re: Re: i.MX28 On-Board Diagnostics Suite (OBDS)

fernandolopes — Tue, 01 Jul 2014 11:44:23 GMT

Indeed there is no linux cfimager with the obds package.

To be used on linux there is a script named mk_mx28_sd.

My copy is attached. I got it from the i.MX28 SDK (L2.6.35_10.12.01_SDK) on the folder L2.6.35_10.12.01_SDK_scripts.

Best regards,

Fernando.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Tue, 01 Jul 2014 12:31:45 GMT

Hi fernandolopes

I tried mk_mx28 script but its asking for rootfs..I modified the script and flashed stream files to memory card ...but after that when i power on i just get a big hex number..i think its not booting

Then i tried the windows cfimager.exe then i got an error like this how to solve it?

cfimager.exe -f ..\..\output\mx28\bin\mx28-obds.sb -d g -a

Failed to unlock drive, closing anyway!

Error: error -24

Re: Re: i.MX28 On-Board Diagnostics Suite (OBDS)

fernandolopes — Tue, 01 Jul 2014 12:46:44 GMT

What is the HEX number you get on DUART? The attached list may help you translate the error code to english. It is for i.MX23, but the ROM code on i.MX28 is almost the same (or it is the same, I dont't know, maybe some of the freescale folks can confirm tell you).

I have never used the windows cfimager, so I do not know what this error mean. I remember I got the cfimager sources once, but I couldn't find them here. I am sure they are available somewhere. You can dig into the code to know what caused that error message.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

lategoodbye — Tue, 01 Jul 2014 14:34:33 GMT

Hi Pt,

there are two common pitfalls with cfimager.exe.

1) Please don't use the outdated cfimager version from the ODBS. Take it from the MfgTool.

2) cfimager requires admin privileges. So run the tool always in a admin console.

BR Stefan

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Wed, 02 Jul 2014 05:02:25 GMT

Thanks fernandolopes. The hex number from DUART is 0x8020A01D.

#define ERROR_DDI_SD_MBR_NOT_FOUND (ERROR_DDI_GROUP | ERROR_DDI_SD_DRIVER_GROUP | 0x1D)

0x8020A01D ?

Regards

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Wed, 02 Jul 2014 07:21:51 GMT

Thanks lategoodbye

Successfully programmed sb file to sd card.

cfimager.exe -f mx28-obds.sb -d <drive to which card reader connected> -a

for example,

it card reader is connected to drive E then

cfimager.exe -f mx28-obds.sb -d g -a

(if you are programming sd for the first time then use -a at the end.)Other wise

cfimager.exe -f mx28-obds.sb -d g

Re: Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Wed, 02 Jul 2014 09:14:22 GMT

Hi Qiang_FSL raymondwang fernandolopes lategoodbye igorpadykov YixingKong

Anyone have spi test code for imx28?

Regards

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

jimmychan — Mon, 07 Jul 2014 06:52:36 GMT

I think you can take the spi test in the imx-test package for reference. (to extract the source code , you can type this LTIB command ./ltib -p imx-test -m prep)

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Mon, 14 Jul 2014 15:51:24 GMT

Thanks jimmychan.I will try it.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Mon, 18 Aug 2014 07:01:02 GMT

Hi Qiang_FSL

I want to change the order of test functions in OBDS tool suite. How could I do that?

Regards

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

PeterChan — Mon, 18 Aug 2014 09:55:54 GMT

The test order in i.MX28 OBDS depends on the linking order of these tests in the ".test_launch" section. To boost a test to run in front of the others, use "RUN_TEST_EARLY" instead of "RUN_TEST" to define the test. If you need to customize the test order to a particular sequence, please modify the main.c.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Mon, 18 Aug 2014 10:33:45 GMT

Thanks . "RUN_TEST_EARLY" will make that test to run at first. I understood that.

But I do not know how to change the order. Please help.

Regards

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

PeterChan — Mon, 18 Aug 2014 10:51:59 GMT

Please modify main.c to run each test in the order you want.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Tue, 19 Aug 2014 05:12:31 GMT

I tried to study the code. I didn't understand the flow of the code completely.

The run_tests() function calls these test functions. I have seen that there is three for loop to call test functions.Also I know that its related to linker script. And the RUN_TEST_EARLY function will execute at first. But I didn't understand how to change the order in main.c file. Should I have to define different array for each test ?

Regards

Re: Re: i.MX28 On-Board Diagnostics Suite (OBDS)

PeterChan — Wed, 20 Aug 2014 02:07:56 GMT

Please refer to the definition of RUN_TEST macro. It simply declares a static function "obds_##func" and then create a pointer in the ".test_launch" section pointing to this function.

#define RUN_TEST_COMMON(name, func) \

static int obds_##func (void) \

{ \

obds_test_t test_func = (obds_test_t) func; \

record_test_result(name, test_func()); \

return 0; \

}

#define RUN_TEST(name, func) \

RUN_TEST_COMMON(name, func) \

static obds_test_t __obds_test_##func __attribute__ ((used)) __attribute__ ((section(".test_launch"))) = obds_##func;

In run test, every pointer in ".test_launch" section will go though and execute its pointed test function "obds_##func".

To customize the tests in any order, please remove the "static" declaration in RUN_TEST_COMMON() and then call each "obds_##func()" in the order you want.

Re: i.MX28 On-Board Diagnostics Suite (OBDS)

pt — Wed, 20 Aug 2014 07:29:23 GMT

Hi PeterChan,

Thank you.I understand how to change the order.

I have a doubt on the flow of the code. In the run_tests() function, using for loop we call the functions. The function address is stored in an array.

In the code,

__test_launch_start[], __test_launch_end[] are arrays related to of RUN_TEST function.

static obds_test_t __obds_test_##func __attribute__ ((used)) __attribute__ ((section(".test_launch"))) = obds_##func;

This will allow us to use a special section test_launch.

But how the address is stored in the array? Is that done by linker script? Can you clarify my doubt?

Regards