Re: RISC-V interrupts

2017-06-07 22:41 GMT+03:00 Hesham Almatary : > On Thu, Jun 8, 2017 at 2:26 AM, Denis Obrezkov > wrote: > > 2017-06-07 14:44 GMT+03:00 Sebastian Huber > > : > >> > >> On 06/06/17 18:58, Hesham Almatary wrote: > >> > >>> Originally RTEMS had a one big linkcmd for each platform, which > >>> defines

Re: RISC-V interrupts

2017-06-08 12:24 GMT+03:00 Denis Obrezkov : > 2017-06-07 22:41 GMT+03:00 Hesham Almatary : > >> On Thu, Jun 8, 2017 at 2:26 AM, Denis Obrezkov >> wrote: >> > 2017-06-07 14:44 GMT+03:00 Sebastian Huber >> > : >> >> >> >> On 06/06/17 18:58, Hesham Almatary wrote: >> >> >> >>> Originally RTEMS had a

RTEMS-libbsd USB interrupt issue[GSOC]

Hi all, I am porting Beagle USB from FreeBSD to RTEMS-libbsd, the file i ported is from freebsd/sys/arm/ti/am335x, the file is: AM335x_musb.c , am335x_usbss.c ,etc. BSP: Beaglebone Black, CPU:AM335x The issue i meeted is : When the USB1_DRVVBUS pin pull high, the interrupt vector 0x19 occured

Re: RISC-V interrupts

2017-06-08 17:49 GMT+03:00 Denis Obrezkov : > 2017-06-08 12:24 GMT+03:00 Denis Obrezkov : > >> 2017-06-07 22:41 GMT+03:00 Hesham Almatary : >> >>> On Thu, Jun 8, 2017 at 2:26 AM, Denis Obrezkov >>> wrote: >>> > 2017-06-07 14:44 GMT+03:00 Sebastian Huber >>> > : >>> >> >>> >> On 06/06/17 18:58, He

Re: RISC-V interrupts

Hi Denis, Does your board support any accesses to > 0x8000. Note you still use such region in your linker script, which shouldn't be used if your board doesn't support it. I'd suggest your read about memory mapping on your board and fix the linker script accordingly. Regards, Hesham On Fri,

Re: RISC-V interrupts

2017-06-09 1:52 GMT+03:00 Hesham Almatary : > Hi Denis, > > Does your board support any accesses to > 0x8000. Note you still > use such region in your linker script, which shouldn't be used if your > board doesn't support it. I'd suggest your read about memory mapping > on your board and fix t

Re: RISC-V interrupts

On 09/06/2017 09:09, Denis Obrezkov wrote: > > I think I found the problem. It seems that this gdb build supports 16 KiB of > RAM > (as in Freedom E300 specification). > I changed the value of RAM length to 16 KiB, so now I can execute further. > Thanks! > Some gdb simulators have target optio