how to debug? #1128

snikeguo · 2022-08-12T08:51:17Z

snikeguo
Aug 12, 2022

NFAPP has been successfully run!!
But debugging failed

16:46:00.767 [Starting deployment transaction from v2022.2.0.28+91f4b457d1]
16:46:00.769 [Starting debug engine on nanoDevice]
16:46:00.784 [Connecting to debugger engine...OK]
16:46:01.065 [nanoDevice is not STM32, skipping flash dump]
16:46:01.219 [Assemblies to deploy:]
16:46:01.219 [Assembly: NFApp1 v1.0.0.0 (336 bytes)]
16:46:01.239 [Assembly: mscorlib v1.12.0.4 (31832 bytes)]
16:46:01.240 [Deploying 2 assemblies to device]
16:46:02.205 [Incrementally deploying assemblies to the device]
16:46:02.205 [Erasing block @ 0xA00A0000...]
16:46:02.621 [Deploying 0/32168 bytes.]
16:46:02.942 [Deploying 992/32168 bytes.]
16:46:03.238 [Deploying 1984/32168 bytes.]
16:46:03.545 [Deploying 2976/32168 bytes.]
16:46:03.850 [Deploying 3968/32168 bytes.]
16:46:04.157 [Deploying 4960/32168 bytes.]
16:46:04.464 [Deploying 5952/32168 bytes.]
16:46:04.769 [Deploying 6944/32168 bytes.]
16:46:05.076 [Deploying 7936/32168 bytes.]
16:46:05.381 [Deploying 8928/32168 bytes.]
16:46:05.688 [Deploying 9920/32168 bytes.]
16:46:05.994 [Deploying 10912/32168 bytes.]
16:46:06.301 [Deploying 11904/32168 bytes.]
16:46:06.607 [Deploying 12896/32168 bytes.]
16:46:06.914 [Deploying 13888/32168 bytes.]
16:46:07.222 [Deploying 14880/32168 bytes.]
16:46:07.529 [Deploying 15872/32168 bytes.]
16:46:07.845 [Deploying 16864/32168 bytes.]
16:46:08.142 [Deploying 17856/32168 bytes.]
16:46:08.449 [Deploying 18848/32168 bytes.]
16:46:08.757 [Deploying 19840/32168 bytes.]
16:46:09.064 [Deploying 20832/32168 bytes.]
16:46:09.370 [Deploying 21824/32168 bytes.]
16:46:09.676 [Deploying 22816/32168 bytes.]
16:46:09.982 [Deploying 23808/32168 bytes.]
16:46:10.289 [Deploying 24800/32168 bytes.]
16:46:10.595 [Deploying 25792/32168 bytes.]
16:46:10.901 [Deploying 26784/32168 bytes.]
16:46:11.209 [Deploying 27776/32168 bytes.]
16:46:11.514 [Deploying 28768/32168 bytes.]
16:46:11.821 [Deploying 29760/32168 bytes.]
16:46:12.129 [Deploying 30752/32168 bytes.]
16:46:12.434 [Deploying 31744/32168 bytes.]
16:46:12.691 [Deploying 32160/32168 bytes.]
16:46:13.147 [Assemblies successfully deployed to the device]
16:46:13.148 [No flash dump file provided, can't generate deployment image]
16:46:13.163 [Launching debugger provider from v2022.2.0.28+91f4b457d1]
16:46:13.397 [Attempting to connect the debugger engine (1/5)]
16:46:13.397 [Assigning debug engine of target device]
16:46:13.397 [Device running nanoCLR, updating the debug flags...]
16:46:14.562 [The debugger engine is listening to debug events from the nanoDevice target]

snikeguo · 2022-08-12T08:55:29Z

snikeguo
Aug 12, 2022
Author

System Information
HAL build info: WIN_32 PLAYGROUND APP
  Target:   CLR_WIN32
  Platform: WIN32

Firmware build Info:
  Date:        Aug 12 2022
  Type:        FreeRTOS
  CLR Version: 0.0.0.0
  Compiler:    GNU ARM GCC v4.3.0

OEM Product codes (vendor, model, SKU): 0, 0, 0

Serial Numbers (module, system):
  00000000000000000000000000000000
  0000000000000000

Target capabilities:
  Has nanoBooter: NO
  IFU capable: NO
  Has proprietary bootloader: NO

AppDomains:

Assemblies:

Native Assemblies:
  mscorlib v100.5.0.17, checksum 0x004CF1CE
  System.Math v100.0.5.4, checksum 0x46092CB1
  nanoFramework.System.Collections v100.0.1.0, checksum 0x2DC2B090
  nanoFramework.System.Text v100.0.0.1, checksum 0x8E6EB73D
  nanoFramework.ResourceManager v100.0.0.1, checksum 0xDCD7DF4D
  nanoFramework.Runtime.Native v100.0.9.0, checksum 0x109F6F22
  nanoFramework.Runtime.Events v100.0.8.0, checksum 0x0EAB00C9
  EventSink v1.0.0.0, checksum 0xF32F4C3E



++++++++++++++++++++++++++++++++
++        Memory Map          ++
++++++++++++++++++++++++++++++++
  Type     Start       Size
++++++++++++++++++++++++++++++++
  RAM   0x7000a68c  0x00005000
  FLASH 0x00000000  0x00000000



Exception when trying to parse flash map data.


Deployment Map
Empty

4 replies

josesimoes Aug 12, 2022
Maintainer

Seems that something is wrong with the flash mapping.
No way to guess what could be causing this.

From the dev caps above it seems that the build is using FreeRTOS for the Win32 build and that GCC is 4.3. That combination its waaaay of the usual and tested scenarios. 😯

snikeguo Aug 12, 2022
Author

Sorry, that's what I scribbled, I've corrected it:


System Information
HAL build info: SNIKEGUO
  Target:   TC367Target
  Platform: TC367Platform

Firmware build Info:
  Date:        Aug 12 2022
  Type:        FreeRTOS
  CLR Version: 0.0.0.0
  Compiler:    GNU ARM GCC v4.3.0

OEM Product codes (vendor, model, SKU): 0, 0, 0

Serial Numbers (module, system):
  00000000000000000000000000000000
  0000000000000000

Target capabilities:
  Has nanoBooter: NO
  IFU capable: NO
  Has proprietary bootloader: NO

AppDomains:

Assemblies:

Native Assemblies:
  mscorlib v100.5.0.17, checksum 0x004CF1CE
  System.Math v100.0.5.4, checksum 0x46092CB1
  nanoFramework.System.Collections v100.0.1.0, checksum 0x2DC2B090
  nanoFramework.System.Text v100.0.0.1, checksum 0x8E6EB73D
  nanoFramework.ResourceManager v100.0.0.1, checksum 0xDCD7DF4D
  nanoFramework.Runtime.Native v100.0.9.0, checksum 0x109F6F22
  nanoFramework.Runtime.Events v100.0.8.0, checksum 0x0EAB00C9
  EventSink v1.0.0.0, checksum 0xF32F4C3E



++++++++++++++++++++++++++++++++
++        Memory Map          ++
++++++++++++++++++++++++++++++++
  Type     Start       Size
++++++++++++++++++++++++++++++++
  RAM   0x7000a68c  0x00005000
  FLASH 0x00000000  0x00000000



Exception when trying to parse flash map data.


Deployment Map
Empty

My actual platform is TC367 + Tasking compiler

I plan to use 6 sectors starting from 0xA00A0000 (16KB/ sector, minimum write 32 bytes) as the device deployment area. But I don't know how to fill in BlockRegionInfo, here is my configuration:

//
// Copyright (c) .NET Foundation and Contributors
// See LICENSE file in the project root for full license information.
//

#include <nanoHAL_Types.h>
#include <nanoPAL_BlockStorage.h>




// 256kB blocks
const BlockRange BlockRange3[] = {
    {BlockRange_BLOCKTYPE_DEPLOYMENT, 0, 3} // 080C0000 deployment
};

const BlockRegionInfo BlockRegions[] = {

    {
        (BlockRegionAttribute_ProgramWidthIs256bits),        
        0xA00A0000, // start address for block region
        6,          // total number of blocks in this region
        0x04000*6,    // total number of bytes per block
        ARRAYSIZE_CONST_EXPR(BlockRange3),
        BlockRange3,
    },

};

const DeviceBlockInfo Device_BlockInfo = {
    (MediaAttribute_SupportsXIP),       // STM32 flash memory is XIP
    2,                                  // UINT32 BytesPerSector
    ARRAYSIZE_CONST_EXPR(BlockRegions), // UINT32 NumRegions;
    (BlockRegionInfo *)BlockRegions,    // const BlockRegionInfo* pRegions;
};

MEMORY_MAPPED_NOR_BLOCK_CONFIG Device_BlockStorageConfig = {
    {
        // BLOCK_CONFIG
        {
            0,     // GPIO_PIN             Pin;
            false, // BOOL                 ActiveState;
        },

        (DeviceBlockInfo *)&Device_BlockInfo, // BlockDeviceinfo
    },

    {
        // CPU_MEMORY_CONFIG
        0,          // UINT8  CPU_MEMORY_CONFIG::ChipSelect;
        true,       // UINT8  CPU_MEMORY_CONFIG::ReadOnly;
        0,          // UINT32 CPU_MEMORY_CONFIG::WaitStates;
        0,          // UINT32 CPU_MEMORY_CONFIG::ReleaseCounts;
        16,         // UINT32 CPU_MEMORY_CONFIG::BitWidth;
        0x08000000, // UINT32 CPU_MEMORY_CONFIG::BaseAddress;
        0x00200000, // UINT32 CPU_MEMORY_CONFIG::SizeInBytes;
        0,          // UINT8  CPU_MEMORY_CONFIG::XREADYEnable
        0,          // UINT8  CPU_MEMORY_CONFIG::ByteSignalsForRead
        0,          // UINT8  CPU_MEMORY_CONFIG::ExternalBufferEnable
    },

    0, // UINT32 ChipProtection;
    0, // UINT32 ManufacturerCode;
    0, // UINT32 DeviceCode;
};

BlockStorageDevice Device_BlockStorage;

#define GloalHeapSize               (1024*20)
extern uint8_t GloalClrHeap[GloalHeapSize];
// RAM base address
//bygq
#define RAM1_MEMORY_StartAddress        ((uint32_t)GloalClrHeap)
// RAM size
#define RAM1_MEMORY_Size                ((uint32_t)GloalHeapSize)

// FLASH base address
#define FLASH1_MEMORY_StartAddress      (0)
// FLASH size
#define FLASH1_MEMORY_Size              (0)
HAL_SYSTEM_CONFIG HalSystemConfig =
{
    { true }, // HAL_DRIVER_CONFIG_HEADER Header;

    1, //ConvertCOM_DebugHandle(1),
    0,//ConvertCOM_DebugHandle(0),
    921600,
    0,  // STDIO = COM2 or COM1

   {RAM1_MEMORY_StartAddress, RAM1_MEMORY_Size},
   {FLASH1_MEMORY_StartAddress, FLASH1_MEMORY_Size},
};

snikeguo Aug 12, 2022
Author

@josesimoes nanoframework/nf-interpreter#2408 nanoframework/nf-Visual-Studio-extension#734

josesimoes Aug 12, 2022
Maintainer

You need to fill in config for all block storage. Minimum is booter+clr+deployment

I'm away from my desk until next Aug 16, so I can't help much from my phone.

As for the PR: any chnages there need to be done in the debugger repository, not in the submodule of VS extension.

snikeguo · 2022-08-12T10:26:09Z

snikeguo
Aug 12, 2022
Author

RUNNING OK！ DEBBUGGING FAILED...

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

how to debug? #1128

{{title}}

Replies: 2 comments 4 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

how to debug? #1128

snikeguo Aug 12, 2022

Replies: 2 comments · 4 replies

snikeguo Aug 12, 2022 Author

josesimoes Aug 12, 2022 Maintainer

snikeguo Aug 12, 2022 Author

snikeguo Aug 12, 2022 Author

josesimoes Aug 12, 2022 Maintainer

snikeguo Aug 12, 2022 Author

snikeguo
Aug 12, 2022

Replies: 2 comments 4 replies

snikeguo
Aug 12, 2022
Author

josesimoes Aug 12, 2022
Maintainer

snikeguo Aug 12, 2022
Author

snikeguo Aug 12, 2022
Author

josesimoes Aug 12, 2022
Maintainer

snikeguo
Aug 12, 2022
Author