[ell-i-developers] Re: Partially working recursive make -- please test!

  • From: Ivan Raul <supra.material@xxxxxxxxx>
  • To: "ell-i-developers@xxxxxxxxxxxxx" <ell-i-developers@xxxxxxxxxxxxx>
  • Date: Tue, 19 Aug 2014 01:34:27 +0300

Dear All,

I included a special case for the RCC->CFGR register to always keep the PLL
as switched clock. With that the initialisation of the stm32f4 completes as
expected up to the InitRecords

BR, Ivan



With Warm Regards, Ivan Raul


On Mon, Aug 18, 2014 at 11:42 PM, Eero Hakala <eero.k.hakala@xxxxxxxxx>
wrote:

> There is something missing in the request as its not merged into Ell-i
> Runtime - however I copied the changed parts from the pull request and got
> a clean compile for emulator also. I still get a segmentation fault, also
> there must be something odd happening as it gets more than 20000 rows of
> (identical) output before crashing. The beginning is quite normal:
> RCC:CR:200ff83|=1
> RCC:CFGR:=0
> RCC:CR:200ff83&=fef6ffff
> RCC:PLLCFGR:=24003010
> RCC:CR:200ff83&=fffbffff
> RCC:CIR:=0
> RCC:CR:200ff83&2
> RCC:CFGR:0&=fffffffc
> RCC:CFGR:0|=0
> RCC:CR:200ff83|=10000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> RCC:CR:201ff83&20000
> ...
>
>
> -eero-
>
> PS from ellduino I get this one:
> RCC:CR:200ff83|=1
> RCC:CFGR:8&=f8ffb80c
> RCC:CR:200ff83&=fef6ffff
> RCC:CR:200ff83&=fffbffff
> RCC:CFGR:8&=ffc0ffff
> RCC:CFGR2:0&=fffffff0
> RCC:CFGR3:0&=fffffeac
> RCC:CR2:ff80&=fffffffe
> RCC:CIR:=0
> FLASH:ACR:=11
> RCC:CFGR:8|=0
> RCC:CFGR:8|=0
> RCC:CFGR:8&=ffc0ffff
> RCC:CFGR:8|=280000
> RCC:CR:200ff83|=1000000
> RCC:CR:300ff83&2000000
> RCC:CFGR:280008&=fffffffc
> RCC:CFGR:280008|=2
> RCC:CFGR:28000a&c
> InitRecord: 804a9c2 type: 9090 count: 0
>
>
>
>
> On Mon, Aug 18, 2014 at 10:32 PM, Ivan Raul <supra.material@xxxxxxxxx>
> wrote:
>
>> Hi, it is in Feature make work-in-progress (feature-make-wip)
>>
>> With Warm Regards, Ivan Raul
>>
>>
>> On Mon, Aug 18, 2014 at 9:27 PM, Eero Hakala <eero.k.hakala@xxxxxxxxx>
>> wrote:
>>
>>> Hi Ivan that is excellent! Jess!
>>>
>>> In which branch of the runtime is you pull request?
>>>
>>>
>>> -eero-
>>>
>>>
>>>
>>> On Mon, Aug 18, 2014 at 10:06 PM, Ivan Raul <supra.material@xxxxxxxxx>
>>> wrote:
>>>
>>>> Dear All,
>>>>
>>>> I have created a pull request for the initial compilation of the
>>>> stm32f4discover board on the emulator.
>>>>
>>>> However, it needs additional checking.
>>>>
>>>> From the hardware side, I tested and successfully run a blinky on the
>>>> board with the new startup code.
>>>>
>>>> BTW, Today I got full permission to work on this project  without any
>>>> conflicts regarding competition, copyright, etc.
>>>>
>>>> Have a very nice evening
>>>>
>>>>
>>>> BR, Ivan
>>>>
>>>> With Warm Regards, Ivan Raul
>>>>
>>>>
>>>> On Fri, Aug 15, 2014 at 4:20 PM, Pekka Nikander <pekka.nikander@xxxxxx>
>>>> wrote:
>>>>
>>>>> > Jess exactly like that in Ubuntu also!
>>>>> >
>>>>> > Inputting just plain make functions OK and make clean is also OK,
>>>>> the residue thats left is:
>>>>> > ...
>>>>> > -rwxrwxr-x 1 eero eero 395139 Aug 15 16:01 libsketch.so
>>>>>
>>>>> Ok, thanks!
>>>>>
>>>>> I pushed this to master.
>>>>>
>>>>> I'd appreciate if you Eero (or someone) opened tickets for the
>>>>> remaining libsketch.so (or better yet add a clean:: rule in app.mk to
>>>>> remove it and make a pull request), and another ticket for rewriting the
>>>>> stm32f4discovery startup code into C.
>>>>>
>>>>> The next step now is to get the rest of Asif's changes to the emulator
>>>>> so that we can actually start running the RF test cases against the master
>>>>> branch.  We penciled down Wed 27th for continuing this work with Asif (as 
>>>>> I
>>>>> won't have time before that), but it would be good if someone else managed
>>>>> to push the ball forward already before that.  That is, as the next step
>>>>> Asif's changes need review, and they need to be rebased on the top of the
>>>>> new master.
>>>>>
>>>>> --Pekka
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Other related posts: