-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Programming ATSAME51J19A #209
Comments
Hi @lillikelley, what's the error message exactly? Anyway, the |
Hi, thank you for answering! Would it be easy to make a custom .json for the SAME51 chip using some of the information from the feather w/ can board? Here is my original error message: Verbose mode can be enabled via |
You probably have two installations of the same platform here
I guess you can use the |
Alright, so this is as far as I got after making those changes. The project built successfully, and I have the .hex file to be programmed in
Processing adafruit_feather_m4_can (platform: https://github.com/platformio/platform-atmelsam; board: adafruit_feather_m4_can; framework: arduino)
[Inferior 1 (Remote target) killed] |
Hi @lillikelley 1 Microchip SAME51N20A (rev D) M4 Is that an indicator of the issue? It’s not the ATSAME51J19A part? |
Hi @valeros, I ran the "Project Inspect" feature and found that there is an invalid board option 'upload.offset_address'. My firmware includes the bootloader, so I modified PIO Core Call Error: "Processing feather_can_debug (platform: https://github.com/platformio/platform-atmelsam; board: adafruit_feather_m4_can; framework: arduino)Verbose mode can be enabled via
KeyError: "Invalid board option 'upload.offset_address'": feather_can_debug FAILED 00:00:00.953 |
You're probably using an incorrect option name, it should be |
Hello all,
I am trying to use the Black Magic Probe to load firmware (.hex w/ bootloader) onto an ATSAME51J19A using a SWD header on a separate PCB. I have updated my BMP firmware as well as the PIO core (I am using the VSCode extension). I have my board set to the Adafruit feather w/ can since they have the same MCU, even though they're not the same board, but let me know if that's the root of my problems here. I have edited my C:\Users<user>.platformio\platforms\atmelsam\boards\adafruit_feather_m4_can.json file and added "blackmagic" into the protocols array to no avail.
Here is my platformio.ini file:
[env:adafruit_feather_m4_can]
platform = GitHub - platformio/platform-atmelsam: Atmel SAM: development platform for PlatformIO 1
board = adafruit_feather_m4_can
framework = arduino
debug_tool = blackmagic
debug_port = COM4
upload_port = COM4
upload_protocol = blackmagic
The text was updated successfully, but these errors were encountered: