Thanks guys! The EABI configuration was the problem. My busybox was not compiled with AEABI, so I disabled it in the compiler config, and now I get to the shell prompt.
However, there seems to be a problem with the serial interrupt now. While pressing keys generates a serial interrupt, no text will be displayed in the terminal. However, my hello world program will print text if it is run instead of /bin/sh. I'll dig into this a little deeper and see if I can figure out what is going on. Thanks again, Joe -----Original Message----- From: Tobias Knutsson [mailto:[email protected]] Sent: Thursday, June 18, 2009 8:48 AM To: Nori, Sekhar Cc: Young, Joseph; [email protected] Subject: Re: Start-up boot problems You should also check that there is no mismatch between kernel and userspace ABI. For example if your userspace (busybox i presume) is compiled with a EABI compiler, CONFIG_AEABI should be set. It could also be the other way around, old userspace with EABI-enabled kernel. In that case i think you can try CONFIG_OABI_COMPAT. On Tue, Jun 16, 2009 at 16:35, Nori, Sekhar<[email protected]> wrote: > On Tue, Jun 16, 2009 at 19:55:00, Young, Joseph wrote: >> Hello all, >> >> I am working to port the Davinci Linux kernel to another TI chip, >> Jacinto2, but am experiencing problems. The two devices are very >> similar (DSP, ARM core) but have different development boards and >> some address differences. >> >> The J2 Linux boot is very close to completion, but upon executing the >> 'run_init_process' command ( in 'kernel_execve' , when it executes >> the arm assembly code), everything freezes. This occurs when the >> system > > Joe, > > When you say freezes, does it 'appear' frozen because of lack of > activity on the serial? If you can connect using an JTAG emulator, do you see > any exception? > >> executes the specified 'init' program passed by the bootloader and >> transfers everything to user space. >> >> I have tried passing the linuxrc, init, /bin/sh, and /bin/ash >> programs as the init command. I have also written a 'hello world' >> type program that would simply print something out (It works like I >> expect for the Davinci kernel). I am pretty confident I have the >> different board and device settings, the memory map, and all of the >> registers correctly set up, but perhaps this is not the case. The >> problem is, I'm not sure how to even start debugging it. >> >> Has anyone else ever run into anything like this? Does anyone have >> any suggestions to try? > > This can be because the serial interrupt is not working properly. As I > recall, this stage is the first time serial interrupt is exercised. > > Thanks, > Sekhar > > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > -- Hälsningar/Regards Tobias Knutsson _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
