Actions
Forum Thread Details
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 353 subscribers
  • Views 761 views
  • Users 0 members are here
Related

How do I login to Pulsar Linux on Microzed?

shanedora

I just booted the pulsar linux image that came with my microzed board. I went ahead and setup minicom so I could see the boot process. My host computer is a laptop running CentOS 7 (NOT WINDOWS). It's giving me a login prompt as such...

cube-10-12-15-cube-server login:

On the pulsar linux getting started guide it says to use the credials at the login prompt

root:incendia

Minicom doesn't let me type in anything. So how am I suppose to log in to it? Where are these instructions at? Can I setup a ssh session and if so where are the instructions for this? Direct links much appreciated in setting up a ssh session.

A few restrictions are...

I cannot plug this board into a modem. I need to plug the zed into my laptop which is connected to wifi.

~S

  • 0

    Hello scy86dev,

    Was your MicroZed shipped with Pulsar Linux?  Was the MicroZed purchased recently?  The reason I ask is that we  do not directly support Wind River Pulsar Linux from our side anymore and so I did not think we were shipping SD cards with it loaded anymore either.

    The quickest way to get to a command prompt is to go through the serial terminal as you are doing.  These threads may be helpful in getting your serial terminal working:

    http://microzed.org/content/usb-uart-problem

    http://microzed.org/content/microzed-cant-get-hello-world-print-anything-consoleminicom

    I don't think you will need a modem for the board, although you may want to use wired Ethernet on MiniZed to connect to your network.

    Best Regards,

    -Kevin

  • 0 in reply to zedhed

    Kevin ~ I'm assuming you're the same Kevin that replied to the posts you mentioned above on adding udev rules? If so, would you be so kind to help me understand a few udev settings you made....

    ENV{ID_MM_DEVICE_IGNORE}="1"
    You mentioned you did this to prevent the modem manager from touching the USB-UART device that is the target board. I guess I don't understand what the modem manager is and when it's appropriate to ensure it's ignore. I googled "Modem Manager" a bit but most tutorials were alittle above my head to grasp the full picture of it's purpose.

    sudo usermod -a -G dialout AES_CM
    Who and where did this AES_CM user come from? I've never heard of such as user. Exteremely confused what this is. I thought I only need to add myself (my user account i log in with) to the dialout group?

    ATTR{idVendor} and the ATTR{idProduct}
    How did you find these two attributes from the command line? Would you be so kind to show me how I can determine these two values? Also you matched these keys to idVendor being "04b4" and idProduct being "0008". What if my MicroZed board has different vendor and product id's? Will they? This is why I ask in how I can effectively determine what the two are myself.

  • 0

    I'm going to add something to this post real quick as part of the solution I found. Zedhead provided me with a great post on configuring minicom and udev rules on a linux box. However, in that post you'll need to change a few things based on your enviornment.

    First, verify the product and vendor id of your device. The id that is listed in the post is specific to their board. You can accomplish this as...
    lsusb
    The first 4 hex characters are the vendor id and the last are the product id. Therefore, the vendor id in "10c4:ea60" would be "10c4" and the product ID would be "ea60".

    Second, I have no idea who this AES_CM user is that is being referenced in the following command from that post...
    sudo usermod -a -G dialout AES_CM
    This username I'm assuming is that person's personal username???? I've always added myself to the dialout group so if your username is billyBobBlue then issue...
    sudo usermod -a -G dialout billyBobBlue

     

  • 0

    Hi scy86dev,

    I am by far not an expert at the "Why" explanation and this is probably the wrong board to find out the deep details on CentOS Linux behavior.

    I use Google to find many answers myself too.  Here is where I pulled some of that information from:

    https://linux-tips.com/t/prevent-modem-manager-to-capture-usb-serial-devices/284/2

    You are correct, on my lab machine, the username we use is AES_CM so maybe on your machine you would use this instead to add your user to the dialout group:

    sudo usermod -a -G dialout scy86dev

    Derived from here:

    https://github.com/cTn-dev/Phoenix-FlightController/blob/master/extras/Configurator/readme.txt

    I think the 04b4 Vendor ID will not change since it is for Silicon Labs USB-UART converter used on MicroZed.

    I think that the Product ID default value also will not change but it is my understanding that you can use tools to change that value on some Silicon Labs parts if you wished to do so. 

    Some information here also on where to find these VID and PID values from Kernel debug output messages:

    https://www.silabs.com/content/usergenerated/asi/cloud/attachments/siliconlabs/en/community/groups/interface/forum/jcr:content/content/primary/qna/cp2012_interfacewih-wwdm/cp2012log.txt

    Best Regards,

    -Kevin

  • 0

    Okay, great!

    Thank you for posting your results on this!  I am sure it is helpful to others!

    Best Regards,

    -Kevin