Error: Illegal access to … when flashing custom board emmc

Forums Devices OSD32MP15x Error: Illegal access to … when flashing custom board emmc

Viewing 1 reply thread
  • Author
    Posts
    • #13509
      DamianDamian
      Participant

        Hello,

        I want to upgrade my hardware with OSD32MP157C from dunfell to new openstlinux kirkstone 4.1 release november 2022 because we want to use Linux RT.

        I have written custom device tree files based on BRK (https://github.com/octavosystems/OSD32MP1-BRK-device-tree). We use EMMC.

        Compiling for tf-a, u-boot, fip and kernel is fine.

        However when I try to flash my image flashlayout to my custom board I get a “ERROR: Illegal access to 0xfffffff0:”

        See following console output:

        NOTICE:  CPU: STM32MP157C?? Rev.Z
        NOTICE:  Model: Octavo OSD32MP1 BRK board
        INFO:    PMIC version = 0x21
        INFO:    Reset reason (0x214):
        INFO:      IWDG2 Reset (rst_iwdg2)
        INFO:    FCONF: Reading TB_FW firmware configuration file from: 0x2ffe2000
        INFO:    FCONF: Reading firmware configuration information for: stm32mp_io
        INFO:    Using USB
        INFO:      Instance 2
        INFO:    Boot used partition fsbl1
        NOTICE:  BL2: v2.6-stm32mp1-r2.0(debug):v2.6-dirty(a1f02f4f)
        NOTICE:  BL2: Built : 13:14:26, Nov 23 2021
        INFO:    BL2: Doing platform setup
        INFO:    RAM: DDR3-DDR3L 16bits 533000Khz
        INFO:    Memory size = 0x20000000 (512 MB)
        INFO:    DFU USB START...
        INFO:    phase ID :3, Manifestation 3 at c710effa
        INFO:    Send detach request
        INFO:    Receive DFU Detach
        INFO:    DFU USB STOP...
        INFO:    BL2: Loading image id 1
        INFO:    Loading image id=1 at address 0x2ffff000
        INFO:    Image id=1 loaded: 0x2ffff000 - 0x2ffff226
        INFO:    FCONF: Reading FW_CONFIG firmware configuration file from: 0x2ffff000
        INFO:    FCONF: Reading firmware configuration information for: dyn_cfg
        INFO:    FCONF: Reading firmware configuration information for: stm32mp1_firewall
        INFO:    BL2: Loading image id 4
        INFO:    Loading image id=4 at address 0x2ffc5000
        INFO:    Image id=4 loaded: 0x2ffc5000 - 0x2ffd9820
        INFO:    BL2: Skip loading image id 8
        INFO:    BL2: Skip loading image id 9
        INFO:    BL2: Loading image id 2
        INFO:    Loading image id=2 at address 0xc0500000
        INFO:    Image id=2 loaded: 0xc0500000 - 0xc0512088
        INFO:    BL2: Loading image id 16
        INFO:    Loading image id=16 at address 0x2ffc0000
        INFO:    Image id=16 loaded: 0x2ffc0000 - 0x2ffc3ef8
        INFO:    BL2: Loading image id 5
        INFO:    Loading image id=5 at address 0xc0100000
        INFO:    Image id=5 loaded: 0xc0100000 - 0xc01e4534
        NOTICE:  BL2: Booting BL32
        INFO:    Entry point address = 0x2ffc5000
        INFO:    SPSR = 0x1d3
        NOTICE:  SP_MIN: v2.6-stm32mp1-r2.0(debug):v2.6-dirty(a1f02f4f)
        NOTICE:  SP_MIN: Built : 13:14:26, Nov 23 2021
        INFO:    ARM GICv2 driver initialized
        INFO:    Set calibration timer to 60 sec
        INFO:    stm32mp1 IWDG1 is secure
        INFO:    SP_MIN: Initializing runtime services
        INFO:    SP_MIN: Preparing exit to normal world
        ERROR:   Illegal access to 0xfffffff0:
        ERROR:   	FAIL_ID = 0x4c0
        ERROR:   	Non-Secure
        ERROR:   	Privilege
        ERROR:   	Read
        PANIC at PC : 0x2ffc9739
        
        Exception mode=0x00000016 at: 0x2ffc9739

        This is output from Cube Programmer:

        $ STM32_Programmer_CLI -c port=USB1 -w flashlayout_epis-image-core-dev/trusted/FlashLayout_emmc_stm32mp157c-osd32mp1-epis-shuttle-sps-trusted.tsv 
              -------------------------------------------------------------------
                                STM32CubeProgrammer v2.13.0                  
              -------------------------------------------------------------------
        
        
        
        USB speed   : High Speed (480MBit/s)
        Manuf. ID   : STMicroelectronics
        Product ID  : DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000
        SN          : 004600293230510632393433
        DFU protocol: 1.1
        Board       : --
        Device ID   : 0x0500
        Device name : STM32MP15xx
        Device type : MPU
        Revision ID : --  
        Device CPU  : Cortex-A7
        
        Start Embedded Flashing service
        
        
        
        Memory Programming ...
        Opening and parsing file: tf-a-stm32mp157c-osd32mp1-epis-shuttle-sps-usb.stm32
          File          : tf-a-stm32mp157c-osd32mp1-epis-shuttle-sps-usb.stm32
          Size          : 220,38 KB 
          Partition ID  : 0x01 
        
        Download in Progress:
        [==================================================] 100% 
        
        File download complete
        Time elapsed during download operation: 00:00:01.087
        
        RUNNING Program ... 
          PartID:      :0x01 
        Start operation done successfully at partition 0x01
        
        
        Memory Programming ...
        Opening and parsing file: fip-stm32mp157c-osd32mp1-epis-shuttle-sps-trusted.bin
          File          : fip-stm32mp157c-osd32mp1-epis-shuttle-sps-trusted.bin
          Size          : 1,06 MB 
          Partition ID  : 0x03 
        
        Download in Progress:
        [==================================================] 100% 
        
        File download complete
        Time elapsed during download operation: 00:00:01.452
        
        RUNNING Program ... 
          PartID:      :0x03 
        
        Reconnecting the device ...

        Board does no reconnect to host …

        What is wrong in my configuration or device tree?

        Error messages come from tf-a, not sure if it is related to u-boot and fip.

        Is an update to openstlinux 4.1 release planned with BRK device trees? If yes, when is it planned?

        Any suggestion is appreciated! Thanks!

        Greez Dmn

         

         

      • #13527
        Neeraj Dantu
        Moderator

          Damian,

          Apologies for the late reply. Currently Octavo’s plan is to support major revisions of OpenSTLinux. Here is the latest meta-octavo layer that supports OpenSTLinux v4.0: https://github.com/octavosystems/meta-octavo-osd32mp1/tree/kirkstone. The device tree files are added in as patches(for example: https://github.com/octavosystems/meta-octavo-osd32mp1/tree/dunfell/recipes-kernel/linux/files for the kernel).

          Best,

          Neeraj

      Viewing 1 reply thread
      • You must be logged in to reply to this topic.