MaaXBoard-RT: SDK examples for you - my experience

The next SDK project works on MaaXBoard-RT:

tjaekel/MaaXBoard-RT_lwip_httpsrv_freertos_cm7: MaaxBoard RT HTTP server with FreeRTOS (github.com)

It is changed to 100M PHY and connector.
1G PHY on board is different: still to modify project to use also 1G ETH connector
(take it from "golden reference", "out-of-box" demo, merge it to this project...

Why did it crash?

The original project has crashed immediately in ResetHandler, when the INTs were enabled.
The reason was:
During the initialization of memory sectors, esp. .bss section and fill with zeros - there was one write to a non-existing memory (0x83000000).

Right after INT enable, inside ResetHandler() - the BusFault_Handler() was triggered. It was pending due to wrong .bss initialization and kicked in
immediately after INT enable.

Main reason and fix:

Check carefully which memories are used, in the "MCU Setting". It is not enough just to modify Flash and SDRAM size, just: also check carefully if any other memory region
is used and invalid!
When you setup an SDK project, this "MCU Setting" is taken from SDK examples and might be still wrong!

You can use "Import" (and "Export"):
Export from a working project, e.g. "out-of-box" demo and import
(or import my XML file here, see in next post).

It works for me, with 100M connector.
Just modify the IP address used for your network.

the link to XML file does not work, try again to attach here the file...

<info flash_driver='MaaXBoard_S26KS256.cfx'>
 <chip>
  <memory id='Flash' type='Flash' is_ro='true' can_program='true'></memory>
  <memory id='RAM' type='RAM'></memory>
   <memoryInstance id='BOARD_FLASH' derived_from='Flash' location='0x30000000' size='0x2000000' driver='${workspace_loc:}/${ProjName}/xip/MaaXBoard_S26KS256.cfx'  edited='true'  />
   <memoryInstance id='BOARD_SDRAM' derived_from='RAM' location='0x80000000' size='0x2000000'   edited='true'  />
   <memoryInstance id='SRAM_OC1' derived_from='RAM' location='0x20240000' size='0x80000'   edited='true'  />
   <memoryInstance id='SRAM_OC2' derived_from='RAM' location='0x202c0000' size='0x40000'   edited='true'  />
   <memoryInstance id='NCACHE_REGION' derived_from='RAM' location='0x20300000' size='0x40000'   edited='true'  />
   <memoryInstance id='SRAM_OC_ECC1' derived_from='RAM' location='0x20340000' size='0x10000'   edited='true'  />
   <memoryInstance id='SRAM_OC_ECC2' derived_from='RAM' location='0x20350000' size='0x10000'   edited='true'  />
   <memoryInstance id='SRAM_DTC_cm7' derived_from='RAM' location='0x20000000' size='0x40000'   edited='true'  />
   <memoryInstance id='SRAM_ITC_cm7' derived_from='RAM' location='0x0' size='0x40000'   edited='true'  />
 </chip>
</info>

A new working project: the DualCore demo from SDK, with RPC (using FreeRTOS):

tjaekel/MaaXBoard-RT_erpc_two_way_rpc_rpmsg_rtos_cm4: DualCore RCP demo, from SDK, bi-directional RPC with FreeRTOS (github.com)

The next SDK project works on MaaXBoard-RT:

tjaekel/MaaXBoard-RT_lpspi_edma_b2b_transfer_master_cm7: MaaXBoard-RT LPSPI4 demo (github.com)

The LPSPI4 (as SPI on J1 header), plus GPIO INT Demo.

See also this thread:

 MaaXBoard-RT: LPSPI4 and GPIO INT for you 

I have now enough SDK examples working and I have started to merge several projects into my one: "MaaXBoard-RT_SPIder":

Please, find my active project here:

tjaekel/MaaXBoard-RT_SPIder: MaaXBoard-RT SPIder framework (github.com)

Experience:

If you create an SDK example using USB, "both" INT handlers are setup (for every SDK example project), the USB_OTG1_IRQHandler() as well as USB_OTG2_IRQHandler() are defined,
always and both with calling the same handler.

OK, it results in an "already defined" error, but which one is which?
(never both are needed at the same time, even programmed this way in SDK examples).

If you use USB-C (as USB device only possible):
implement USB_OTG1_IRQHandler().

If you use the User USB (the USB-A connector: device and master possible):
implement USB_OTG2_IRQHandler().

Summary:

I have all the SDK examples (as building blocks) for my project working.
I will stop to comment here, not adding more comments here.

It was working fine to import SDK examples, to modify those to make them working as well as to merge now several projects together for "my project"
(I have merged: SPI example, USB VCP example, USB Memory device example, using FreeRTOS...).

If you like: track my progress on GitHub:

tjaekel/MaaXBoard-RT_SPIder: MaaXBoard-RT SPIder framework (github.com)

Enjoy the MaaXBoard-RT (as I do).

BTW:

if you need the latest files, in "board", esp. file "pin_mux.c", you can get it from my project:

tjaekel/MaaXBoard-RT_SPIder: MaaXBoard-RT SPIder framework (github.com)

Every new SDK Example comes with a "reduced" file "pin_mux.c":
Not all pins are configured, just the ones needed for THIS example.

If you merge projects - you have to merge also the code in "void BOARD_InitPins(void)"!
(check if all pins/features needed are also configured, this file "accumulates" all pin configs needed)

I have now both PHYs working, the 100M and the 1G (a different PHY chip used).
I can access with two web browsers to both ports, also the mDNS is working (using a name, like "maaxboard" vs. "maaxboardg".

The project is here:

GitHub - tjaekel/MaaXBoard-RT_SPIder: MaaXBoard-RT SPIder framework

When you try to merge two SDK examples together into one project:

• watch out which method is used to allocate stack for FreeRTOS:
  look at: "FreeRTOSConfig.h" and #define configFRTOS_MEMORY_SCHEME 3  //or 4?
• Select which file. e.g. "${ProjDir}/freertos/freertos-kernel/portable/MemMang/heap_3.c" is used (or heap4.c - just one of them):
  disable the not used files via "Resource Configurations" -> "Exclude from build..." (or enable the other one needed)
• Watch on the SDK example - which should work, the memory configuration, esp. watch for:
  project "Properties" -> "C/C++ Build" -> "Settings" -> "MCU Linker" -> "Managed Linker Script"
  if you have at least the same size for "Heap"
  If your project crashes or does not work as expected, potentially the memory regions have a wrong size (often Heap is too small).

If all is compile clean, but it crashes or does not work during run-time: potentially the "Heap" and "Stack" size are wrong (too small).
Watch the debug console (this MCU-LINK UART): it might give you a hint (e.g. it enters "assert" or a "__BKPT").

The SDK example "wifi_cli_cm7" works:

GitHub - tjaekel/MaaXBoard-RT_wifi_cli_cm7: MaaXBoard-RT with WIFI demo (connect to AP, provide an AP)

Just change in file "app_config.h" (done):

//#define WIFI_IW416_BOARD_MURATA_1XK_M2
#define WIFI_88W8987_BOARD_MURATA_1ZM_USD

The board needs a reset or power-cycle (Murata WiFi chip not reset):
a new debug session (and FW flashed) - the chip cannot be initialized.
But the project FW works fine after resetting the board.