Unable to set GOLDVIP S32G Docker image issue

[Chandan1]

Same thing followed by S32g gold vip manual to create Gold VIP docker Images.

By using Putty configuration we set the baud-rate and mapped to respective mini-com port

And we run the respective commands with mentioned in S32g GoldVIP manual chapter 5.

During in GUI after run the NXPlocal host demo link, we set it the same parameters as mentioned in manual.so we get some issue. whatever i get issue is mentioned in below snap.

So but i i executed same commands procedure mentioned in manual automatically enable the Ethernet port by using docker, but it is not enabled.

And i tried by some commands and enable the Ethernet port again showing same error.

Kindly requesting to you community please help here  

[gmocanu]

Hello,

The GUI executes some scripts that are available in the GoldVIP Docker container image. In this case, that error should show up if the corresponding script couldn't be executed. Could you try to run from a shell of the GoldVIP Docker container a "default" command such as `sudo ./eth-slow-path-host.sh <ethif_connected_to_p2a> <ethif_connected_to_p3b>`?

Kind regards,
George

[Chandan1]

Hello George

Again i followed same steps as mentioned in GOLDVIP S32G

Upto Chapter 5.2 executed correctly

Then give this command [* sudo docker exec -it goldvip /bin/bash] its not executed properly what ever i facing issues are mentioned in screenshots.

Then i selcted Ethernet 0 and 1 ports UP and i will run the slow path command as mentioned in 11.2 chapter.

whatever the NXPlocal demo says Chapter 5.3 steps i executed clearly again its shows same issue 

whatever the PFE_MAC2;;;;;;PFE_MAC0 (2.5G mode);;;;;;PFE_MAC1(Connect to AQR113C or AQR107);;;; and configured the same address by reference manuals

after executing this command [$ sudo docker exec -it goldvip /bin/bash] find issue like this$ sudo expect /home/vip/device_utils.exp /dev/ttyUSB0....This command executed properlythen we open the NXPlocal host demo, configured same parameters as mentioned in DocFound same errorHope you understand ethernet ports are UPAgain i executed same command as mentioned Document and your messageSame issue found againAgain i changed ports done same steps againFound same Issue 

Regards

Chandan K S

[gmocanu]

Hello,

Thanks for the detailed description of the steps you follow.

It seems like there are some issues with the host-target connection (given the output of eth-slow-path-host.sh where we can observe that ping between host and target is not working - "4 packets transmitted, 0 received, 100% packet loss, time 3058ms"). I would suggest checking again the cable connections and trying a simple ping test to ensure that all the required links are working (this will imply connecting to the serial console of the device to apply the network configuration - choose whichever tool you are most comfortable with). Something like the following should indicate whether the links are properly set up:

# On target:
$ ip link set pfe2 up
$ ip addr flush dev pfe2
$ ip addr add 10.0.100.1/24 dev pfe2

# On host:
$ ip link set <host_netif> up
$ ip addr flush dev <host_netif>
$ ip addr add 10.0.100.2/24 dev <host_netif>
$ ping 10.0.100.1

One additional comment, regarding "after executing this command [$ sudo docker exec -it goldvip /bin/bash] find issue [...]": the aforementioned command can be used from another terminal to start a new shell session in the container. It shouldn't be used in the already-opened shell of the container.

Kind regards,
George

[Chandan1]

Hello George

Thanks for Guidance and Information.

But actually we have facing issue chapter 5th itself.

After executing in chapter 5th in 5.2 Deploy GoldVIP Docker image. it shows docker command not found & not executed.

Note:So we already tried installed whole docker installation and Flashed GoldVip binaries to SD card again..

Whatever facing issue mentioned in screenshot please help here.

Regards

Chandan K S

[gmocanu]

Hello,

The $ sudo docker exec -it goldvip /bin/bash should NOT be executed in the already-opened shell of the container. Please run it from another terminal (while the terminal where you ran $ sudo docker run [...] command is still open). However, the fact that this command fails in your scenario does not have any effect on the next steps.

Best regards,
George