mimxrt: Use -Og instead of -O0 for DEBUG builds.

Thanks for the hint, Damien. The DEBUG build got very large recently.
The major difference is, that inline function are now inlined and
not included as a function. That's good and maybe bad. The good thing is,
that the code speed si now close to the final code. It could be worse
in single step debugging. I'll see.

Setting this option caused a new warning and a formatting error
to pop up at different places. Fixed as well.

ports/mimxrt/Makefile

@@ -125,7 +125,7 @@ LIBS = $(shell $(CC) $(CFLAGS) -print-libgcc-file-name)
 
 # Tune for Debugging or Optimization
 ifeq ($(DEBUG),1)
-CFLAGS += -O0 -ggdb
+CFLAGS += -Og -ggdb
 LDFLAGS += --gc-sections
 CFLAGS += -fdata-sections -ffunction-sections
 else

ports/mimxrt/hal/phy/device/phydp83848/fsl_phydp83848.c

@@ -25,7 +25,7 @@
 #define PHY_PHYSTS_LINK_MASK          0x0001U /*!< The PHY link up mask. */
 
 #define PHY_RMII_MODE                 0x20
-#define PHY_RMII_REV1_0               0x10   
+#define PHY_RMII_REV1_0               0x10
 
 /*! @brief Defines the timeout macro. */
 #define PHY_READID_TIMEOUT_COUNT 1000U

ports/mimxrt/mimxrt_flash.c

@@ -79,7 +79,7 @@ status_t flash_erase_block(uint32_t erase_addr) {
 // the vfs driver takes care for erasing the sector if required
 status_t flash_write_block(uint32_t dest_addr, const uint8_t *src, uint32_t length) __attribute__((section(".ram_functions")));
 status_t flash_write_block(uint32_t dest_addr, const uint8_t *src, uint32_t length) {
-    status_t status;
+    status_t status = 0;
     uint32_t size;
     uint32_t next_addr;