Skip to content
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

Add multiple Chip IDs to Resolve mdloader not working on old/new PCBs #37

Open
CombatCables opened this issue Sep 8, 2020 · 2 comments

Comments

@CombatCables
Copy link

CombatCables commented Sep 8, 2020

{ "SAMD51J18A", 0x41002018, 0x60060006, 0x40000, 0x20000, 0x00000000, 0x20000000},

Further documentation can be found here to ultimately future proof this problem: http://ww1.microchip.com/downloads/en/DeviceDoc/SAM-D5x-E5x-Family-Silicon-Errata-DS80000748K.pdf

mcu_t mcus[] = {
      //Name,       Chip ID     Chip ID,    Program Memory, Data Memory,    Program Addr,   Data Addr
      //            Address                 (FLASH_SIZE)    (HSRAM_SIZE)    (FLASH_ADDR)    (HSRAM_ADDR)
    { "SAMD51J18A-0", 0x41002018, 0x60060006, 0x40000,        0x20000,        0x00000000,     0x20000000},
    { "SAMD51J19A-0", 0x41002018, 0x60060005, 0x40000,        0x20000,        0x00000000,     0x20000000},
    { "SAMD51J18A-3", 0x41002018, 0x60060306, 0x40000,        0x20000,        0x00000000,     0x20000000}, 
    { "SAMD51J19A-3", 0x41002018, 0x60060305, 0x40000,        0x20000,        0x00000000,     0x20000000}, 
};
@JasonYuanLiu
Copy link

There's also a chance it's 0x60060306 and 0x60060305, as seen in issue #24 and #32

@CombatCables
Copy link
Author

There's also a chance it's 0x60060306 and 0x60060305, as seen in issue #24 and #32

Alright I added the other Chip IDs as well. It should work with all boards mentioned. Just need Drop to submit the update for qmk_toolbox to get updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants