Re: Error Running HelloWorld on new BSP

2016-06-17 Thread Gedare Bloom
Break at get_baud_div() or initialize(), since they appear in your printout of the *frame, which is the interrupted thread context at the point of the unhandled exception. On Fri, Jun 17, 2016 at 1:44 PM, Olufowobi, Habeeb wrote: > Hi Joel, > > When I set the breakpoint at boot_card, this how far

Re: Error Running HelloWorld on new BSP

2016-06-17 Thread Olufowobi, Habeeb
Hi Joel, When I set the breakpoint at boot_card, this how far I could get; (gdb) step _Terminate (the_source=RTEMS_FATAL_SOURCE_EXCEPTION, is_internal=false, the_error=536874976) at ../../../../../../../rtems.git/c/src/../../cpukit/score/src/interr.c:52 52 _CPU_Fatal_halt( the_source

Re: Error Running HelloWorld on new BSP

2016-06-17 Thread Joel Sherrill
On Fri, Jun 17, 2016 at 11:33 AM, Olufowobi, Habeeb < habeeb.olufow...@bison.howard.edu> wrote: > Hi, > > I was able to print the frame and below is the result. Also, I realised > the problem is from the uart. Any ideas on how to resolve this? > > > (gdb) print *frame > $1 = {register_r0 = 115200,

Re: Error Running HelloWorld on new BSP

2016-06-17 Thread Olufowobi, Habeeb
Hi, I was able to print the frame and below is the result. Also, I realised the problem is from the uart. Any ideas on how to resolve this? (gdb) print *frame $1 = {register_r0 = 115200, register_r1 = 1, register_r2 = 0, register_r3 = 1073790976, register_r4 = 0, register_r5 = 0, register_r6

Error Running HelloWorld on new BSP

2016-06-15 Thread Olufowobi, Habeeb
Hi, I have been working on getting the console running for the past few days but I am still getting some errors. I realized that the system control configuration of the board family (LM3S69XX) was different so I had to rewrite the bspstart.c and the lm3s69xx.h to suit the TM4C129E I am working on.