英文:
Using nanoframework on the NUCLEO-F746ZG
问题
我想尝试使用.NET NanoFramework。对ESP32的初步测试成功，但那并不是我真正感兴趣的平台。与此同时，我有一块NUCLEO-F746ZG放在我的桌子上，用于进一步测试。
这块板子应该也被支持为一个"社区"板：
当我在板子上安装NanoFramework时，我得到了以下反馈：
PS C:\###> nanoff --target ST_NUCLEO144_F746ZG --update
.NET NanoFramework固件烧写工具 v2.4.30+cdac7a25ca
版权所有 (C) 2019 .NET Foundation 和NanoFramework项目贡献者
试图在稳定的存储库中找到ST_NUCLEO144_F746ZG...未找到
试图在社区目标存储库中找到ST_NUCLEO144_F746ZG...OK
提取ST_NUCLEO144_F746ZG-1.8.1.8.zip...OK
升级到1.8.1.8
连接到ID为0668FF495087534867043936的JTAG设备
设备：STM32F74x/STM32F75x
板子：NUCLEO-F746ZG
CPU：Cortex-M7
设备ID：0x449
******************************************* 警告 ***************************************
看起来即将使用的固件映像可能不适用于已连接的目标。但这并不一定意味着它不会工作。
*******************************************************************************************
正在烧写设备...
nanoBooter.hex
nanoCLR.hex
烧写完成...
重置设备上的MCU...OK
PS C:\###>
警告表明这可能不是正确的板子，但根据我的经验，应该是正确的。为什么会表明这可能是错误的板子，正确的板子是什么？
接下来，它无法与板子建立联系。只找到了调试适配器的COM端口，并且没有响应。
英文:
I would like to experiment with the .net nanoframework. An initial test on an ESP32 was successful, but that's not really the platform I'm interested in. Meanwhile, I have a NUCLEO-F746ZG on my desk for further testing.
<https://os.mbed.com/platforms/ST-Nucleo-F746ZG/>
This board should also be supported as a 'community' board:
<https://docs.nanoframework.net/content/community-targets/st-nucleo144-f746zg.html>
When installing the nanoframework on the board, I get the following feedback:
PS C:\###> nanoff --target ST_NUCLEO144_F746ZG --update
.NET nanoFramework Firmware Flasher v2.4.30+cdac7a25ca
Copyright (C) 2019 .NET Foundation and nanoFramework project contributors
Trying to find ST_NUCLEO144_F746ZG in stable repository...Not found
Trying to find ST_NUCLEO144_F746ZG in community targets repository...OK
Extracting ST_NUCLEO144_F746ZG-1.8.1.8.zip...OK
Updating to 1.8.1.8
Connected to JTAG device with ID 0668FF495087534867043936
Device: STM32F74x/STM32F75x
Board: NUCLEO-F746ZG
CPU: Cortex-M7
Device ID: 0x449
******************************************* WARNING ***************************************
It seems that the firmware image that's about to be used isn't the appropriate one for the
target connected. But this doesn't necessarily mean that it won't work.
*******************************************************************************************
Flashing device...
nanoBooter.hex
nanoCLR.hex
Flashing completed...
Reset MCU on device... OK
PS C:\###>
The warning indicates that it would not be the right board, but in my experience it should be. Why would it indicate that this might be the wrong board, which board would be correct?
Next, it fails to make contact with the board. Only the COM port of the debug adapter is found and there is no response to that.
答案1
得分: 1
请注意警告的最后一部分：“但这并不一定意味着它不会工作。”
固件包名称与目标连接的合理性检查。
您可以通过添加--nofitcheck来跳过检查/警告。
请查看此处获取详细信息。
对于此目标，需要连接用户USB连接器上的USB电缆。请查看此处。
英文:
Please note the last part of the warning: "But this doesn't necessarily mean that it won't work."
There is a sanity check on the firmware package name vs the target connected.
You can skip the check/warning by adding the --nofitcheck.
See here for details.
On this target, it's required to connect an USB cable on the user USB connector. See the now on the readme here.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论