error: The application image is not compatible with the target.

[zfangqijun]

I compiled hex with yotta, I can't falsh to microbit, I'm a FE developer, I don't know anything about hardware, why? please help me, thank you very much!!!🙏🙏

.yotta.json

{
  "build": {
    "target": "bbc-microbit-classic-gcc,https://github.com/lancaster-university/yotta-target-bbc-microbit-classic-gcc"
  }
}

FAIL.TXT

error: The application image is not compatible with the target.
type: user

DETAILS.TXT

# DAPLink Firmware - see https://daplink.io
Build ID: v0257-gc782a5ba (gcc)
Unique ID: 99063602000528200d12df3d5109fd52000000006e052820
HIC ID: 6e052820
Auto Reset: 1
Automation allowed: 0
Overflow detection: 0
Incompatible image detection: 1
Page erasing: 0
Daplink Mode: Interface
Interface Version: 0257
Bootloader Version: 0257
Git SHA: c782a5ba907377658bc28aa8d132a0fa44543687
Local Mods: 0
USB Interfaces: MSD, CDC, HID, WebUSB
Bootloader CRC: 0x725bea7d
Interface CRC: 0xe561f1de
Remount count: 2
URL: https://microbit.org/device/?id=9906&v=0257

[microbit-carlos]

Hi @zfangqijun,

You are building the samples repo for micro:bit V1 and loading it into a V2. For the V2 samples repo see: https://github.com/microbit-foundation/micropython-microbit-v2/

Hope that resolved your issue!

[microbit-carlos]

@JohnVidler might be a good idea to update this README to indicate this is for V1 and where to find the repo for V2.

[zfangqijun]

@microbit-carlos
Thank you very much for your reply. 🙏This repo seems to have built-in micropython.
I wonder if there is a repo that does not contain micropython for reference?
Or let me see how to delete it。😊

[microbit-carlos]

Oh, sorry, I sent the wrong link!
https://github.com/lancaster-university/microbit-v2-samples

[zfangqijun]

@microbit-carlos Thank you very much

[finneyj]

Thanks @microbit-carlos! I'll forgive the shameless advertising of your excellent micro python implementation! :)

Definitely a good idea to improve cross-signposting for v1 and v2 repos. Can you please take a look @JohnVidler? I think this would align very well with the documentation updates you're working on?