On 29/7/19 4:35 pm, Sebastian Huber wrote:
> On 29/07/2019 08:24, Chris Johns wrote:
>> On 29/7/19 4:16 pm, Sebastian Huber wrote:
>>> On 29/07/2019 08:12, Chris Johns wrote:
On 29/7/19 4:08 pm, Sebastian Huber wrote:
> On 29/07/2019 08:04, Chris Johns wrote:
>>> The new one is probabl
On 29/07/2019 08:24, Chris Johns wrote:
On 29/7/19 4:16 pm, Sebastian Huber wrote:
On 29/07/2019 08:12, Chris Johns wrote:
On 29/7/19 4:08 pm, Sebastian Huber wrote:
On 29/07/2019 08:04, Chris Johns wrote:
The new one is probably:
0x00200080
I am not sure about the 0x80 tail, it should be t
On 29/7/19 4:16 pm, Sebastian Huber wrote:
> On 29/07/2019 08:12, Chris Johns wrote:
>> On 29/7/19 4:08 pm, Sebastian Huber wrote:
>>> On 29/07/2019 08:04, Chris Johns wrote:
> The new one is probably:
>
> 0x00200080
>
> I am not sure about the 0x80 tail, it should be the same a
On 29/07/2019 08:12, Chris Johns wrote:
On 29/7/19 4:08 pm, Sebastian Huber wrote:
On 29/07/2019 08:04, Chris Johns wrote:
The new one is probably:
0x00200080
I am not sure about the 0x80 tail, it should be the same as it was previously.
Better but interrupts?
The address 0x0020 works w
On 29/7/19 4:08 pm, Sebastian Huber wrote:
> On 29/07/2019 08:04, Chris Johns wrote:
>>> The new one is probably:
>>>
>>> 0x00200080
>>>
>>> I am not sure about the 0x80 tail, it should be the same as it was
>>> previously.
>> Better but interrupts?
>>
>> The address 0x0020 works with hello bu
On 29/07/2019 08:04, Chris Johns wrote:
The new one is probably:
0x00200080
I am not sure about the 0x80 tail, it should be the same as it was previously.
Better but interrupts?
The address 0x0020 works with hello but ticker prints the "TEST VERSION"
banner and then nothing more.
Then t
On 29/7/19 3:55 pm, Sebastian Huber wrote:
> What was the old start address?
START_ADDR=0x8000
ENTRY_ADDR=0x8000
> The new one is probably:
>
> 0x00200080
>
> I am not sure about the 0x80 tail, it should be the same as it was previously.
Better but interrupts?
The address 0x0020
On 29/07/2019 07:49, Chris Johns wrote:
On 29/7/19 3:45 pm, Sebastian Huber wrote:
On 29/07/2019 07:36, Chris Johns wrote:
On 29/7/19 3:23 pm, Sebastian Huber wrote:
could someone with a Raspberry Pi please test this patch.
RTEMS failed to start. It has broken something. I retested by ru
On 29/7/19 3:45 pm, Sebastian Huber wrote:
> On 29/07/2019 07:36, Chris Johns wrote:
>> On 29/7/19 3:23 pm, Sebastian Huber wrote:
>>>
>>> could someone with a Raspberry Pi please test this patch.
>>>
>>
>> RTEMS failed to start. It has broken something. I retested by running master
>> again.
>
>
On 29/07/2019 07:36, Chris Johns wrote:
On 29/7/19 3:23 pm, Sebastian Huber wrote:
could someone with a Raspberry Pi please test this patch.
RTEMS failed to start. It has broken something. I retested by running master
again.
The start address changes with this patch. How does this system
On 29/7/19 3:23 pm, Sebastian Huber wrote:
>
> could someone with a Raspberry Pi please test this patch.
>
RTEMS failed to start. It has broken something. I retested by running master
again.
Chris
___
devel mailing list
devel@rtems.org
http://lists.r
Hello,
could someone with a Raspberry Pi please test this patch.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on
12 matches
Mail list logo
