Problem with fs_init after importing to Segger Embedded Studio

[phild]

Hi, 

I followed the instructions for importing the Thing:52 firmware into SES and managed to get the firmware compiled and loading, and the code reaches the main function without any apparent problem. When it gets to the application though I get an error in m_ble_flash_init. The problem is in the structure returned by FS_SECTION_ITEM_GET(i) within fs_init (called within m_ble_init->m_ble_flash_init->fsd_init) - particularly in these lines (fstorage.c:363) : - 

p_config_i = FS_SECTION_ITEM_GET(max_index);

        p_config_i->p_end_addr   = p_current_end;
        p_config_i->p_start_addr = p_current_end - (p_config_i->num_pages * FS_PAGE_SIZE_WORDS);

The write of p_current_end to p_config_i>p_end_addr doesn't happen and the value remains 0. The same is true for p_config_i->p_start_addr. 

p_current_end is 0x00080000, i.e. the end of the flash section - as expected. The p_config pointer is pointing to 0x5beac. 

Of course what then happens is that p_current_end gets update to 0x0: - 

p_current_end = p_config_i->p_start_addr;

This causes problems later on. 

There are earlier warnings which Iooked into. The first on happens because all the structure values are 0, so the drv_ext_light_off driver tries to setup a timer with timeout_ticks = 0, so this generated an NRF_ERROR_INVALID_PARAM error. 

It seems these errors could all be down to the same root cause - the inability to write to these structures. 

Any idea what I am doing wrong? 

Thanks in advance for any help.

Phil.

p.s. If it is useful - here is the trace from the debug console.

 main :INFO:===== Thingy started! =====

drv_ext_light :WARNING:Err code returned in file: /Users/derrick/work/third-party/Nordic-Thingy52-FW/source/drivers/drv_ext_light.c, line: 754, code 7 
drv_ext_light :WARNING:Err code returned in file: /Users/derrick/work/third-party/Nordic-Thingy52-FW/source/drivers/drv_ext_light.c, line: 858, code 7 
drv_ext_light :WARNING:Err code returned in file: /Users/derrick/work/third-party/Nordic-Thingy52-FW/source/drivers/drv_ext_light.c, line: 754, code 7 
drv_ext_light :WARNING:Err code returned in file: /Users/derrick/work/third-party/Nordic-Thingy52-FW/source/drivers/drv_ext_light.c, line: 858, code 7 
m_env :INFO:Init: 
m_motion :INFO:Init 
m_sound :INFO:Sound_init 
m_ble :WARNING:Too few random bytes available. Trying again 
m_ble :WARNING:Too few random bytes available. Trying again 
m_ble :WARNING:Too few random bytes available. Trying again 
m_ble :INFO:Available random bytes: 16 
m_ble :INFO:Random value (hex): 2x2x2x2x
m_ble_flash :INFO:Initialization
m_ble_flash :WARNING:Err code returned in file: /Users/derrick/work/third-party/Nordic-Thingy52-FW/source/modules/m_ble_flash.c, line: 197, code 11 
m_ble :ERROR: m_ble_flash_init failed - 11
main :ERROR: id = 16385, pc = 0, file = /Users/derrick/work/third-party/Nordic-Thingy52-FW/project/pca20020_s132/main.c, line number: 304, error code = 11 = NRF_ERROR_INVALID_DATA

[phild]

Hi Edvin, 

Thank you for your help and detailed response. One problem with your app_timer_start workaround (and it probably isn’t a big problem) is that the processor is already executing the incorrect branch of code. In this case, the intention is to turn the LED off (as this is called from drv_ext_light_off)

    else if (reg_vals->on_time       == 0 &&
             reg_vals->on_intensity  == DRV_EXT_LIGHT_INTENSITY_OFF &&
             reg_vals->off_time      == 0 &&
             reg_vals->off_intensity == 0 &&
             reg_vals->fade_in_time  == 0 &&
             reg_vals->fade_out_time == 0 )
    {
        *led_drv_status = LED_DRV_DISABLED_LIGHT_OFF;
        *power_optim_possible = true;

From line 457 or drv_ext_light.c

Because of the round() differences, the fade_in_time and fade_out_time are non-zero and so the correct branch (above) is not taken and the following one is: -

    else if (reg_vals->off_time      == 0)

    {

        *led_drv_status = LED_DRV_ENABLED_SINGLE_SHOT;

        if (reg_vals->off_intensity == 0)

        {

            *power_optim_possible = true;

        }

    }

(Line 476).

This may not be a problem but I wonder if it waste more power as it enables the IO extender oscillator when it isn’t really needed. 

[Edvin]

That is correct, 

Also, I saw that my implementation made my LEDs work a bit buggy. No crash, but sometimes the wrong color for a limited amount of time.

Did you look into the flash_placement.xml and thumb_crt0.s files from the porting guide? Did you manage the flash part? It should not be necessary to use only RAM.

 

At least for me, the combination of the flash_placement.xml and addiing the fs_data_ lines in the thumb_crt0.s file worked for me.

 

BR,

Edvin

[phild]

Hi Edvin, 

Yes I updated the flash_placement.xml and use the thumb_crt0.s from SES 3.4 with the edits that you detailed, but the results were the same.

Thanks again for all your help - it is very much appreciated.

BR,

Phil 

[phild]

BTW I changed my fix for the round so that it now checks the divisor is non-zero before performing the round.

    /* Fade in */
    divisor = (REG_RISEFALL_TIME_LOW_MULTIPLIER * (reg_val->on_intensity - (4 * reg_val->off_intensity)) * (255 / m_clkx_tics_pr_sec));
    uint32_t fade_in_time_low_mult_reg  = (divisor == 0) ? 0 : (uint32_t) round( (real_val->fade_in_time_ms / divisor) / 1000 ) ;                                                          

    divisor = (REG_RISEFALL_TIME_HIGH_MULTIPLIER * (reg_val->on_intensity - (4 * reg_val->off_intensity)) * (255 / m_clkx_tics_pr_sec));
    uint32_t fade_in_time_high_mult_reg = (divisor == 0) ? 0 : (uint32_t) round( (real_val->fade_in_time_ms / divisor) / 1000 );
 

This is committed to my GitHub account and the ses_import branch has been merged back into the main branch.

[Edvin]

Hello Phil,

I never actually managed to compile your git repo. There were some weird compilator issues. I looked in your master branch just now, and I couldn't find the thumb_crt0.s file. It is usually located in the Segger Embedded Studio install path, and not in the project folder, but it was included in your ses-port branch, if I remember correctly.

 

Would it be possible to send a copy of the file as it looks now?

 

BR,

Edvin