Trace on Vybrid with DS-5

cancel
Showing results for 
Search instead for 
Did you mean: 

Trace on Vybrid with DS-5

Jump to solution
2,046 Views
Contributor III

I am now using TWR-VF65SG10 Tower Board , and I can boot from SD card, by the way I am on windows host

I'm trying to use DS-5 to trace on this board, and I follow the step as follow link

https://www.google.com.tw/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjmk7Sfs...

here's one step

"Plug in an Ethernet and connect it to your local PC. The board is set to static IP of 169.254.0.100. Set your PC to something similar like 169.254.0.1."

so I unplug my host ethernet cable, and use crossover cable to connect the target board and my host(windows)

but the ip address showed from the A5 is 192.168.1.3  so I changed the IP addr to it

"Adjust the host’s networking so that it can communicate with the target. TCP/IP (for example Ethernet) is used to communicate with the target when doing application level debug and Streamline profiling"

I change my host (win7) IP address to 192.168.1.1 and default gateway to 192.168.1.254

but it didn't work

I was wondering where did it go wrong,

1 Solution
308 Views
Community Manager
This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!

View solution in original post

0 Kudos
23 Replies
309 Views
Community Manager
This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!

View solution in original post

0 Kudos
307 Views
Senior Contributor II

Hi,
    I have reproduced your issue and seen the continuous error (CA5:Error: mcc_send error: 6). This causes MQX portion has not booted first before Linux, to rectify you need to try and load the MQX after linux boots.
please refer this document to load the mqxboot after linux boots.
https://linuxlink.timesys.com/docs/wiki/engineering/userguide_vybrid_mcc#Out-of-Box-Demo

Please also refer the similar issue from here.
https://community.nxp.com/thread/335559#comment-458714

Thanks,

Timesys support.

307 Views
Senior Contributor II

Hi,

      sorry for the delayed response I am trying to reproduce the issue in the mean time could you check all the modules (gator,..) are present in the /lib/modules/3.13.9-ts-armv7l/extra/.

Thanks,

Timesys support.

307 Views
Contributor III

Hi ,

There are only gator.ko and mcc.ko in the /lib/modules/3.13.9-ts-armv7l/extra/

thanks,

0 Kudos
307 Views
NXP Apps Support
NXP Apps Support

Timesys Support  do you have an update?

0 Kudos
307 Views
NXP Apps Support
NXP Apps Support

timesyssupport​ please continue with the follow up.

0 Kudos
307 Views
Senior Contributor II

Hi,   
    > which package should I select for busybox init ?  

  TSWO_PLATFORM_TEMPLATE_BUSYBOX_INIT should be set
The TSWO_PLATFORM_* tokens are only for initial selection template feature in
Factory. I could see that busybox is selected in your workorder no other packages are necessary for the busybox.

The "can't open /dev/ttyDefault: No such file or directory" error happens if
/dev/ttyDefault does not point to the same serial device as the 'console='
in the bootarg.

One can fix this by updating /etc/inittab in his rootfs and change
'ttyDefault' in this file to the 'console=' device node.

I have recreated the issue in ll5 and got the kernel image for 3.13 instead of 3.0. This will be reported to our internal bug tracking mechanism.

>Is that ok I use the old uboot and old kernel image?
That will be fine. Our build system will automatically select the supported u-boot version when you select the target board so its better if you use the new one.

Thanks.
Timesys support.

307 Views
Contributor III

Hi timesyssupport

I already put the new u-boot and new kernel image into SD card, and I tried to connect it to my router, but I couldn't find the device on my router client list,

so I add two lines in S98-vybrid-out-of-box-demo file

modprobe gator

./usr/bin/gatord &

I got the following message while running

gator: Unknown symbol perf_event_create_kernel_counter (err 0)

gator: Unknown symbol perf_event_release_kernel (err 0)

FATAL: Error inserting gator (/lib/modules/3.13.9-ts-armv7l/extra/gator.ko): Unknown symbol in module, or unknown parameter (see dmesg)

I can't type any command while its running since an active demo is running, is there any way I can fix it and get the board being seen on the router so that I can use SSH or STREAMLINE to monitor it ?

0 Kudos
307 Views
Senior Contributor II

Hi,
   I have reproduced issue and seen that you are missing init system. Please select and build busybox init in the ll5 web build system and generate new build. Once you are able to boot then try and trace. Please share the web build link to see if kernel 3.0 is selected. As per your work order 3.13 is selected (TSWO_KERNEL_3_13=y).

Thanks and Regards,
Timesys support.

307 Views
Contributor III

Hi timesyssupport

I choose the busybox package, but I still found the following result in the workorder.txt

#

# Target Platform Templates

#

TSWO_PLATFORM_TEMPLATES=y

# TSWO_PLATFORM_TEMPLATE_BUSYBOX_INIT is not set

# TSWO_PLATFORM_TEMPLATE_SYSTEMV_INIT is not set

# TSWO_PLATFORM_TEMPLATE_DEBUGGING is not set

# TSWO_PLATFORM_TEMPLATE_DEVELOPMENT is not set

# TSWO_PLATFORM_TEMPLATE_TESTING is not set

which package should I select for busybox init ?

and the the output image was still uImage-3.13-ts-armv7l

I didn't change the bootloader, even though I change the file name to uImage-3.0-ts-armv7l, it still didn't work, so I used my original uImage-3.0-ts-armv7l

result :

can't open /dev/ttyDefault: No such file or directory

CA5: Start of constructor

Number of cores to monitor: 1

Button text is Disable core

can't open /dev/ttyDefault: No such file or directory

QLock::lock(): Invalid argument

QLock::unlock(): Unlock without corresponding lock

QLock::lock(): Invalid argument

QLock::unlock(): Unlock without corresponding lock

can't open /dev/ttyDefault: No such file or directory

can't open /dev/ttyDefault: No such file or directory

can't open /dev/ttyDefault: No such file or directory

QLock::lock(): Invalid argument

QLock::unlock(): Unlock without corresponding lock

QLock::lock(): Invalid argument

QLock::unlock(): Unlock without corresponding lock

QLock::lock(): Invalid argument

can't open /dev/ttyDefault: No such file or directory

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

CA5: Tx request to 1,0,1 from 0,0,0

CA5:Error: mcc_send error: 6

I still didn't see my board on my switch after I plug in the ethernet cable

so my

bootloader    old (since I didn't know where to put the new one, while keeping the old one)  ask for uImage-3.0-ts-armv7l

kernel image   old (uImage-3.0-ts-armv7l)

rfs                    new ( from the build output)

besides the busybox init, what else did I miss?

and which package should I select for busybox init?

Is that ok I use the old uboot and old kernel image?

If not, where should I put the new uboot and keep the old one in case something wrong happen?

Thanks

0 Kudos
307 Views
Senior Contributor II

Hi,
       I am unable to reproduce your issue. In order to debug the issue properly Please send it across the work order (.config file)  which is in the top level factory directory.

Thanks,
Timesys support.

307 Views
Contributor III

Hi timesyssupport

I guess it was because I didn't change the u-boot

but I can't find any u-boot file in my SD card in any partition,

even though I changed the new kernel image

I got the message:

U-Boot 2013.07-00004-gaae4ee8 (Jun 05 2014 - 16:00:42)

CPU:   Freescale Vybrid 600 family rev1.2 at 396 MHz

Reset cause: EXTERNAL RESET

Board: TWR-VF65GS10

DRAM:  128 MiB

WARNING: Caches not enabled

NAND:  256 MiB

MMC:   FSL_SDHC: 0

In:    serial

Out:   serial

Err:   serial

Net:   FEC

Hit any key to stop autoboot:  1     0

reading logo.bmpC?391734 bytes read in 51 ms (7.3 MiB/s)

reading accelerometer_example_twrvf65gs10_m4.bin

71116 bytes read in 25 ms (2.7 MiB/s)

reading uImage-3.0-ts-armv7l

** Unable to read file uImage-3.0-ts-armv7l **

Wrong Image Format for bootm command

ERROR: can't get kernel image!

=>

so I tried to put the new u-boot in my SD card in SD_KERNEL partition (there are two partitions, SD_KERNEL and SD_RFS), I still got the same error message.

the new kernel image is uImage-3.13-ts-armv7l, so I could tell from the message that the u-boot was the original one, but I can't find it in the SD card or it was on the board?

when I keep pressing the reset botton and plug in the power, there will a bootloader partition show up, should I drop in there? but I found that if I drop any thing in there, the file I drop in will disappear, so if that's the only way, how can I keep the original u-boot, in case something goes wrong, that I could make it back.

I still don't know whether I missed something when choosing the building packages, that cause the following result

running on original kernel image (3.0)

can't open /dev/ttyDefault: No such file or directory

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

and I found one thing, even though I chose kernel version 3.0, the building result still was 3.13

|----------------------------------------|

| Board Name | twr_vf600 |

| Architecture | armv7l |

| Kernel Architecture | arm |

| Kernel Version | 3.13 |

| Package Output | TGZ |

|----------------------------------------|

System

Board architecture armv7l

Kernel architecture arm

Kernel version 3.0

0 Kudos
307 Views
NXP Apps Support
NXP Apps Support

timesyssupport​ please continue with the follow up.

0 Kudos
307 Views
Senior Contributor II

Hi,

      could you use our web factory/LL5 to generate a new build and proceed further with your vybrid tracing in DS5.

0 Kudos
307 Views
Contributor III

Hi,

Thanks, I found the website. I have a question, after a new build, the build status is always "queued", where can I download the file, or should I install anything else for further downloading?

Thanks,

0 Kudos
307 Views
Senior Contributor II

Hi,

Once your build finishes, you will be able to access a download link from your LinuxLink dashboard. The build will be in the 'queued' state if there were numerous other builds submitted before yours; if your build is still in the queued state, please let us know (along with a link to the build) so we can review.

Thanks,

Timesys Support

307 Views
Contributor III

Hi timesyssupport

I can download the file, and I tried two cases:

1. new kernel image and new file system,

the screen will show "can't load kernel image", but i guess it was because i didn't change the bootloader

I don't have the original bootloader file, I'm afraid if I drag the uboot to the board, and if something goes wrong, I can't make it back to the right one

So I tend to try the second case

2. Kernel image old one, new file system (with gator in it), but I put some lines in S98-vybrid-out-of-box-demo

insmod  /lib/modules//3.13.9-ts-armv7l/extra/gator.ko

the screen will show

     gator: disagrees about version of symbol module_layout

     insmod: can't insert '/lib/modules/3.13.9-ts-armv7l/extra/gator.ko': invalid module format

     if i use old file system and copy gator.ko and gatord to the old one, the above message would still appear

the following message will also be on the screen, I am not sure whether it's right or not

can't open /dev/ttyDefault: No such file or directory

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

CA5: Tx request to 1,0,1 from 0,1,1

CA5: Accelerometer data received: 0,0,63,59

I still can't find the board in DHCP client list on my switch, after i plugged in the ethernet cable

do you know how can I fix it ?

Thanks,

0 Kudos
307 Views
Senior Contributor II

hi,

      If you want to make sure that you have gator daemon running please run ps -d | grep gatord.

If you have no daemon running then you should get all the gator driver and deamon from DS 5 installation directory; ex: /usr/local/DS-5/arm/gator/driver-src/gator-driver.tar.gz.

Thanks,

Timesys support.

307 Views
Contributor III

Hi timesyssupport​,

I can't get into LINUX while it's running since I can't use SSH connect to it and I was running OOBE by default, so I couldn't run ps -d | grep gatord, and I have no idea whether gator daemon is running.

I checked the SD card, and there are two sections, SD_KERNEL and SD_RFS, and I couldn't find gatord in the file system, so I guess I should get the file from DS-5 dir.

I read the REAME and it says I should put the gatord in the same file as gator.ko, but I also couldn't find gator.ko, so should I rebuild the kernel, or just build the gatord and gator.ko and put the in anywhere (or specific dir?) in the file system?

I really don't want to rebuild the kernel and I don't have the kernel source code, so is there any better way that I could simply get the gator.ko (there's a prebuilt gatord in DS-5 dir), put them in the SD card and run successfully?

Thanks,

0 Kudos
307 Views
Senior Contributor II

Hello,

               Please do the following changes both in the host and target.

In the host please do the following changes

Address: 192.168.10.5

Netmask: 255.255.255.0

Gateway: 192.168.10.1

And in the target please uncomment and edit the interfaces file as given below (vi /etc/network/interfaces)

Address: 192.168.10.22

Netmask: 255.255.255.0

Gateway: 192.168.10.1

Make sure both the gateway addresses are same and you are using ethernet crossover cable to connect from host to target. Once you done the changes please reboot the target so that changes will take effect run ifconfig to make sure that the necessary changes are there. If you still cant see the ip address when you run ifconfig then run ifconfig eth0 up 192.168.10.22.

Thanks

Timesys support