public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Nivedita Pitre" <Nivedita.Pitre@p-com•com>
To: <linuxppc-embedded@lists•linuxppc.org>
Subject: Linux booting problems in the IBM Bubinga Board
Date: Wed, 04 Aug 2004 16:32:48 -0700	[thread overview]
Message-ID: <s1110fc4.060@gateway.p-com.com> (raw)


I am using U-boot to boot linux kernel on the IBM Bubinga (405EP board). Using kernel version 2.6.7, which has a default config file for this board. Changed the board info structure to match u-boot's board information structure. Using the mkimage utility in u-boot to create a uImage, which I am downloading via tftpserver to u-boot. Uboot recognizes this image, and jumps into the kernel, after which the system hangs. The last message I see is uncompressing kernel -- OK. I read the manual for u-boot, which suggests modifying the board information structure, and I did that, still have the same problem. After this, I turned on kernel hacking in the config, the CONFIG_SERIAL_TEXT_DEBUG on. This allows me to see some progress on the serial port, the ppc_mach_dep calls output some messages. This tells me that code reaches in start_kernel, however, after console_init, the serial port dies. I assume this is because we initialize the serial port, and turn off early debug. I commented o
 u!
t this part, and enabled early debug messages to continue throughout the start_kernel routine. Also added my own debug messages. So far as I can see, the code goes through till the end of start_kernel without hanging. This makes me think this is a serial port problem in the kernel, but I cannot think what it is. I have configured the UART_TTYSO, SERIAL_CONSOLE, and 8250 drivers in the .config file, and so far as I can see, all the relevant .o files are created, so these drivers are getting compiled. Does anyone have any suggestions for debugging. I am setting up BDI200 to debug this problem. Let me know if there is something else that I am not doing right.

Thanks.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-08-04 23:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 23:32 Nivedita Pitre [this message]
2004-08-05  0:03 ` Linux booting problems in the IBM Bubinga Board Wolfgang Denk
2004-08-05  4:21   ` How to remove JFFS2 'Making dirty' display on RPXlite DW? Song Sam
2004-08-05 13:31     ` David Ho
2004-08-05 14:12     ` Mark Chambers
2004-08-05 14:48       ` David Woodhouse
2004-08-05 14:59         ` Mark Chambers
2004-08-05 15:04           ` David Woodhouse
2004-08-05 14:31     ` David Woodhouse
2004-08-07  7:39       ` Song Sam
2004-08-07  9:50         ` David Woodhouse
2004-08-07 14:14           ` Song Sam
2004-08-09 13:08             ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2004-08-05  0:22 Linux booting problems in the IBM Bubinga Board Nivedita Pitre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s1110fc4.060@gateway.p-com.com \
    --to=nivedita.pitre@p-com$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox