On Thu, Mar 31, 2011 at 12:18 PM, Goichon Francois
wrote:
> After looking a bit further, I saw that the range checking on on the pager's
> physical memory mapping capability fails: the default capability allows the
> pager to map physical pages from 0x100 to 0xe00, while the UART's
> base
On Thu, Mar 31, 2011 at 2:03 PM, Kirangadu bobbu wrote:
> I can see something like this in console WINDOW OF INSIGHT:
>
> 0x81103194 in vfprintf (stream=0xe8bd8800, format=0x81102bb0 "", arg={__ap =
> 0x81149544}) at loader/libs/c/src/vfprintf.c:90
> 0x81102fa8 in printf (format=0x81102bb0 "") at
2011/3/31 Kirangadu bobbu :
> I tried "step-in" . At the below red coloured branch instruction , program
arm-none-eabi-gdb --command=path/to/gdbinit
--
Dawid Ciężarkiewicz
B-Labs. http://b-labs.com/
___
codezero-devel mailing list
codezero-devel@l
On Thu, Mar 31, 2011 at 12:53 PM, Kirangadu bobbu wrote:
> Hello,
Hi,
> I am new to this codezero environment.
> I tried building helloworld program as per the documentation.
> But i tried running final .elf in insight where it got strucked at the call
> :
> bl
> in main.c
>
What do you mean
I tried "step-in" . At the below red coloured branch instruction , program
excution stopped:
0x8110036c:push{r11, lr}
-0x81100370:addr11, sp, #4; 0x4
-0x81100374:subsp, sp, #16;
0x10
-0x81100378:strr0, [r11, #
Hi ,
I went on step by step excution in assembly mode,
at the instruction bl , GUI is not responsding any more
even i gave step over command:
I can see something like this in console WINDOW OF INSIGHT:
*
0x81103194 in vfprintf (stream=0xe8bd8800, format=0x81102bb0 "", arg={__ap =
0x81149544}) a
Hello,
I am new to this codezero environment.
I tried building helloworld program as per the documentation.
But i tried running final .elf in insight where it got strucked at the call
:
bl
in main.c
Can anyone please let me know whats the problem
-kiranbobbu
__
Hello everyone,
I have trouble running the baremetal UART driver example (from
source). My problem happens when I try to map the UART's base to a
virtual page.
After looking a bit further, I saw that the range checking on on the
pager's physical memory mapping capability fails: the defaul
