MCHCK support
Moderator: utzig
-
- Posts: 359
- Joined: Sat Jan 07, 2012 6:22 pm
- Location: Brazil
- Has thanked: 1 time
- Been thanked: 20 times
- Contact:
Re: MCHCK support
I'll review them tonight and commit afterwards. Nice job sir, hope you have fun now!
-
- Posts: 359
- Joined: Sat Jan 07, 2012 6:22 pm
- Location: Brazil
- Has thanked: 1 time
- Been thanked: 20 times
- Contact:
Re: MCHCK support
Charles,
Sorry for the delay, there are some issues we should discuss:
I remember you mentioning the bus pirate before but I didn't give much thought to it. I was reading the programmer source and it seems to support communicating with the usb-dfu bootloader. Any reason for using an external programmer instead of the bootloader?
Cheers
Sorry for the delay, there are some issues we should discuss:
Code: Select all
MEMORY
{
flash0 : org = 0x00000c00, len = 0x100
flashcfg : org = 0x00001000, len = 0x10
flash : org = 0x00001010, len = 32k - 0x1010
ram : org = 0x1FFFF000, len = 8k
}
- The RAM size is incorrect for MK20DX128. You might have another micro-controller on your board like a MD20DX32. Also the starting address would be correct if that is the case.
- Having a flashcfg at address 0x1000 doesn't make any sense because it's fixed at address 0x400 for every Kinetis CPU. Maybe we're requiring that that sections exists, not sure. I'll check later.
Code: Select all
ruby $MCHCKBaseDirectory/programmer/flash.rb name=buspirate:dev=/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A6026RY1-if00-port0 ./ch.bin 0xc00
I remember you mentioning the bus pirate before but I didn't give much thought to it. I was reading the programmer source and it seems to support communicating with the usb-dfu bootloader. Any reason for using an external programmer instead of the bootloader?
Cheers
-
- Posts: 38
- Joined: Sat Jan 10, 2015 10:12 pm
- Has thanked: 1 time
- Been thanked: 1 time
Re: MCHCK support
Hey Fabio,
1. That is correct. The ram size is incorrect for the MK20DX128. However, that is not the chip that is reccomended on the mchck bill of materials. The reccomended chip is the MK20DX32VLF5.
Bill of materials:
https://github.com/mchck/mchck/wiki/BOM
Digikey link:
http://www.digikey.com/product-search/e ... X32VLF5-ND
2. I am not sure about the flashcfg. My only data at this point is that that make file/linker script blinked and the other ones have not.
I used an external programmer because my initial attempts to get ChibiOS working on the MCHCK had some sort of bad interaction with the bootloader. After loading the image, the bootloader refused to respond to attempts to program it over USB. The bus pirate was able to overcome the problem and always worked, so I just kept using it after I got it. I will attempt to try the bootloader programming with the revised linker script/make file this evening.
Thanks,
Charlie
1. That is correct. The ram size is incorrect for the MK20DX128. However, that is not the chip that is reccomended on the mchck bill of materials. The reccomended chip is the MK20DX32VLF5.
Bill of materials:
https://github.com/mchck/mchck/wiki/BOM
Digikey link:
http://www.digikey.com/product-search/e ... X32VLF5-ND
2. I am not sure about the flashcfg. My only data at this point is that that make file/linker script blinked and the other ones have not.
I used an external programmer because my initial attempts to get ChibiOS working on the MCHCK had some sort of bad interaction with the bootloader. After loading the image, the bootloader refused to respond to attempts to program it over USB. The bus pirate was able to overcome the problem and always worked, so I just kept using it after I got it. I will attempt to try the bootloader programming with the revised linker script/make file this evening.
Thanks,
Charlie
-
- Posts: 359
- Joined: Sat Jan 07, 2012 6:22 pm
- Location: Brazil
- Has thanked: 1 time
- Been thanked: 20 times
- Contact:
Re: MCHCK support
Charles,
I'll wait for your feedback on the bootloader (I'm confident it will work this time!).
Regarding the flashcfg section I'll investigate it later. I'll also look into generalizing the processor memory info (flash/ram size).
Cheers,
Fabio Utzig
I'll wait for your feedback on the bootloader (I'm confident it will work this time!).
Regarding the flashcfg section I'll investigate it later. I'll also look into generalizing the processor memory info (flash/ram size).
Cheers,
Fabio Utzig
-
- Posts: 38
- Joined: Sat Jan 10, 2015 10:12 pm
- Has thanked: 1 time
- Been thanked: 1 time
Re: MCHCK support
Apologies for the delay. One of my boards had trouble using the boot loader, but I think it was due to a hardware defect. I tested it with another board and the ChibiOS image worked just fine without interfering with the bootloader.
Thanks,
Charlie
Thanks,
Charlie
-
- Posts: 38
- Joined: Sat Jan 10, 2015 10:12 pm
- Has thanked: 1 time
- Been thanked: 1 time
-
- Posts: 359
- Joined: Sat Jan 07, 2012 6:22 pm
- Location: Brazil
- Has thanked: 1 time
- Been thanked: 20 times
- Contact:
Re: MCHCK support
Very cool! Now the only thing that remains is finding out why the flashcfg section is required. I'll see into that soon.
Cheers,
Fabio Utzig
Cheers,
Fabio Utzig
-
- Posts: 71
- Joined: Sat Aug 22, 2015 1:22 pm
Re: MCHCK support
Sorry to resurrect an old thread - did you figure out the flashcfg bit? I would be interested in having the MCHCK support finished...
Who is online
Users browsing this forum: No registered users and 4 guests