Hi David, A few steps to try. have you tested your kernel on the MAX10 Neek? Have you tried running the kernel directly using nios2-downloag -g ? One easy way of seeing what goes on is to simply put a signaltap on your Nios2. You can see a lot from the memory-accesses it makes. There's also a nice nios plugin for signaltap, but I haven't used it much, I'm not sure if it was MMU capable.
Hope this helps. Walter On 11/18/2016 11:01 PM, David Cemin wrote: > Hi > > We are developing a custom board based on a Max10 device. We are > trying to bring up linux on it (we have done this successfully on a > MAX10 Neek evaluation board already, and our hardware design is based > off that board) > > Ive compiled the linux kernel and generated the hex as in: > $ elf2flash --base=0x0 --input=vmlinux --end=0xfffffff --reset=0x0 > --boot=$SOPC_KIT_NIOS2/components/altera_nios2/boot_loader_cfi.srec > nios2-elf-objcopy -O ihex vmlinux.flash vmlinux.hex > > So the command above will embed the default bootloader to the linux > image. > > we are trying to boot it up but I dont see anything on the serial > port. I am assuming that what I did above for the kernel is correct, > but i might be wrong. > > What are the normal steps for debugging the default bootloader? Is > there a way of seeing (through Jtag for instance) whats going on on > the default bootloader ? > > Its important to mention that the example applications (hello world + > memory test) are running fine. > > Thank you > > regards, > > David > > -- > > _+1 (343) 777-1735_ David Cemin http://coveloz.com > <http://coveloz.com/> > > > > > <http://coveloz.com/> > > > > _______________________________________________ > Rfi mailing list > Rfi@lists.rocketboards.org > http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
_______________________________________________ Rfi mailing list Rfi@lists.rocketboards.org http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
