can't login into system

[caohaifeng]

Hello,ALL,

I have two questions when I built mini-profile.

Q1. can't login into system

I can't login into the system when I input "root" after starting kernel .It has no response. Why?

The log of start kernel is attached.

Q2. usb still have problm

USB_H1_VDDA33 & VDDA25 & USB_OTG_VDDA33 & VDDA25 are all correct. OTG is designed as dual role.

The problem is if I set USB_PWREN high level in static void __init mxc_board_init(void) function in bsp file,

the stage of start kernel will stop at mx5_usbh1_init() , and CPU seems shut down, the FAULT led light.

I really don't know how to solve it, it is weird.

Any reply will be appreciated.

Reagrds,

Haifeng

Original Attachment has been moved to: start-kernel-log.txt.zip

[caohaifeng]

Repeat this question.

Can anyone give me a hint ?

Regards,

Haifeng

[weidong_sun]

Hello,Haifeng,

      >>Q1. can't login into system

          If you are using Mini Profile system ( no GUI), password is root. If you are using ubuntu, password is : lucid

          if you can't still log in successfully, Please try to use rootfs in MFG Tool ( It is released by freescale), Check if you can log in system.

      >>Q2. usb still have problem

          USB OTG design is no problem. If microUSB connector is for device and USB host connector is for OTG Host, you can't insert USB cable into 2 connector at same time. Please check it .

Regards,

Weidong

[caohaifeng]

Hi,Weidong,

I used to download file by using dd command.And PC connect to target board with usb-to-uart,the software is minicom.I will try to use MFG tool to download rootfs later.

You didn't understand my questionI about USB. I did not connect any cable to usb connector.

USB_H1 is designed to HOST and OTG is designed to dual role.So the voltage of USB_H1_VBUS would be 5V when initialize the board. The function mx5_usbh1_init() has no code to set  USB_PWREN as 1, so we must initialize USB_PWREN in mx53_xx_io_init(),which is in bsp file,and set USB_PWREN as 1 to ensure  USB_H1_VBUS voltage will be 5V.Then we initialize USB_H1 by mx5_usbh1_init().The problem is if I do that the cpu will be shut down, the FAULT led light. If I delete the function to set USB_PWREN,which is mx5_set_host1_vubs_func() in my bsp file, there is no error when start kernel,but the voltage of USB_H1_VBUS is not correct obviously.Please refer my bsp file.

Regards,

Haifeng

[weidong_sun]

Hello,Haifeng,

      Tell me your phone number, I will call you !

Weidong

[caohaifeng]

Hi,weidong,

I removed the R186, error occured again.The USB_PWREN is 1.07V when board power is on,then drops to 0V.

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 18, io base 0x53f80000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200

fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

Ini�

-----------------

I find a strange phenomenon. If I reset board immediately after error occured, the stage of usb initialization will pass.

The USB_PWREN is 1.07V when board power is on,then drops to 0V,then the voltage of USB_PWREN changed to be 3.3V.It can be held.

And the error information shows below.

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 18, io base 0x53f80000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200

fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

Initial�������Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

ARC USBOTG Device Controller driver (1 August 2005)

mice: PS/2 mouse device common for all mice

input: gpio-keys as /devices/platform/gpio-keys/input/input0

MXC keypad loaded

24bit read error, ret = -5

input: mxc_power_key as /devices/virtual/input/input1

PMIC powerkey probe

DA9052 TSI Device Driver, v1.0

mxc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0

pmic rtc probe start

24bit write error, ret = -5

pmic_rtc: probe of mc34708_rtc.1 failed with error -1

i2c /dev entries driver

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

Linux video capture interface: v2.00

mxc_v4l2_output mxc_v4l2_output.0: Registered device video0

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v0.1.0)

APM Battery Driver

add mma8450 i2c driver

MXC WatchDog Driver 2.0

MXC Watchdog # 0 Timer: initial timeout 60 sec

Bluetooth: Virtual HCI driver ver 1.3

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCIATH3K protocol initialized

Bluetooth: Generic Bluetooth USB driver ver 0.6

usbcore: registered new interface driver btusb

PMIC ADC start probe

24bit read error, ret = -5

Error in mc34708_pmic_adc_init.

mc34708_adc: probe of mc34708_adc.1 failed with error -1

VPU initialized

mxc_asrc registered

gpu mmu enabled

mxsdhci: MXC Secure Digital Host Controller Interface driver

mxsdhci: MXC SDHCI Controller Driver.

mmc0: SDHCI detect irq 0 irq 1 INTERNAL DMA

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

Cirrus Logic CS42888 ALSA SoC Codec Driver

sgtl5000_hw_read: read reg error : Reg 0x00

Device with ID register 0 is not a SGTL5000

mxc_spdif mxc_spdif.0: MXC SPDIF Audio Transmitter

No device for codec mxc spdif

No device for DAI mxc spdif

No device for DAI imx-ssi-1-0

No device for DAI imx-ssi-1-1

No device for DAI imx-ssi-2-0

No device for DAI imx-ssi-2-1

No device for DAI imx-spdif-dai

DMA Sound Buffer Allocated: Playback UseIram=1 ext_ram=1 buf->addr=8d370000 buf->area=f9609000 size=24576

asoc: mxc spdif <-> imx-spdif-dai mapping ok

ALSA device list:

  #0: imx-3stack-spdif (mxc spdif)

TCP cubic registered

NET: Registered protocol family 17

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

can: broadcast manager protocol (rev 20090105 t)

Bluetooth: L2CAP ver 2.14

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO (Voice Link) ver 0.6

Bluetooth: SCO socket layer initialized

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM ver 1.11

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: BNEP filters: protocol multicast

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2

mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:00:01 UTC (1)

IP-Config: Failed to open eth0

IP-Config: No network devices available.

Waiting for root device /dev/mmcblk0p1...

mmc0: error -110 whilst initialising SD card

----------

It is weird.

Haifeng

[weidong_sun]

OK, Haifeng,

      Let us continue to debug it :

(1) add R186 on board.

(2)remove Q15 (2N7002) ,Then shorted it's pin2 and pin3.

     Keep USB_PWREN High in your program. Then re-boot your board, and tell me result !

Regards,

Weidong

[caohaifeng]

Hi,Weidong,

I have modified hardware and software.It seems that there is no error any more.

The voltage of USB_PWREN is 1.07V when power on,then it adjust to 3.2V.

Actually the process of start kernel is successful even I did not modify the USB_PWREN in program.

Regards,

Haifeng

[weidong_sun]

Hello,Haifeng,

      that is to say, After you did: "(2)remove Q15 (2N7002) ,Then shorted it's pin2 and pin3", your system can normally boot.

right ?

Weidong

[caohaifeng]

Hi,Weidong,

That's right.

Haifeng

[weidong_sun · Accepted solution]

Hello,Haifeng,

     According to above debug, we can confirm the issue was caused by USB_PWREN & Q15, Now in order to ensure your design to be valueable for product, Can you continue do a test ?

(1)Restore Q15 to the board.

(2)Change R200(4.7K) to 0.1uF capacitor.(Replace R200 with 0.1uF capacitor)

In BSP, pull USB_PWREN up to high . Then tell me test result !

Regards,

Weidong

[caohaifeng]

Hi,Weidong,

I have modified hardware and software according with your suggestion.

(1)Restore Q15 to the board.

(2)Change R200(4.7K) to 0.1uF capacitor.(Replace R200 with 0.1uF capacitor)

(3)In BSP, pull USB_PWREN up to high when power on.

It works.

The attachment is boot log.

[weidong_sun]

Hello,Hifeng,

     good job !

weidong

[caohaifeng]

Hi,Weidong,

Thank you for your help. Can you explain to me the reason?

Regard,

Haifeng.