You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Keil for more than 10 years,and it's the standard tool for
Cortex M development, and I know they have many users, also they have
released the free version a few months ago, before that we had many many
many users with cracks! So I think My guess is not that ambitious.
I hope you would assign some team members to add the official support for
keil too.
Best Regards
On Sun, Jul 3, 2022 at 2:28 PM James Hughes ***@***.***> wrote:
That is a very ambitious claim since you don't actually know what our
sales actually are...
We are looking in to alternative toolchains.
—
Reply to this email directly, view it on GitHub
<#877 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECNZSK74SEMLZZU5FC67FDVSFP5HANCNFSM5ZMAQAMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
This is being looked in to. We do need support from ARM for certain things, which they will not be able to provide until the end of the year, unfortunately. In the meantime, lots of the toolchain already works.
On Thu, Jul 14, 2022 at 1:05 PM James Hughes ***@***.***> wrote:
This is being looked in to. We do need support from ARM for certain
things, which they will not be able to provide until the end of the year,
unfortunately. In the meantime, lots of the toolchain already works.
—
Reply to this email directly, view it on GitHub
<#877 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECNZSNBVSYSOWVSGOHGDMDVT7GLVANCNFSM5ZMAQAMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Linker tab: I see that you set R/O base to 0x0000000 whereas I had 0x10000000 when failed.
Once we use linker script, this kind of option won't affect the final result.
Got the same errors.
Can you pass me the map file?
This time I would like to use the official release to compare.
As I mentioned above, I have updated the Pico-Template to use official RP2xxx_DFP. The reason I asked you to try it is because this could become the common example project for us to understand the reason behind the issue you encountered.
@bgolab Can you attach the linker script also? The reason I ask this is because, the map file looks strange.
I know you suppose to use the linker script I provided, but just in case, please send me the one you actually uses
Memory Map of the image
Image Entry point : 0x200000c1
Load Region LR_IROM1 (Base: 0x20000000, Size: 0x000052e0, Max: 0x0003e000, ABSOLUTE)
Execution Region ER_BINRAY_INFO (Exec base: 0x20000000, Load base: 0x20000000, Size: 0x00000000, Max: 0xffffffff, ABSOLUTE)
**** No section assigned to this execution region ****
Execution Region ER_FLASH (Exec base: 0x20000000, Load base: 0x20000000, Size: 0x00000900, Max: 0xffffffff, ABSOLUTE)
Exec Addr Load Addr Size Type Attr Idx E Section Name Object
0x20000000 0x20000000 0x000000c0 Data RO 709 RESET lto-llvm-5f2a3e.o
0x200000c0 0x200000c0 0x00000008 Code RO 220 * !!!main c_p.l(__main.o)
0x200000c8 0x200000c8 0x00000054 Code RO 729 !!!scatter c_p.l(__scatter.o)
0x2000011c 0x2000011c 0x0000001a Code RO 733 !!handler_copy c_p.l(__scatter_copy.o)
This is the one on myside:
Memory Map of the image
Image Entry point : 0x20000001
Load Region LR_IROM1 (Base: 0x20000000, Size: 0x00005430, Max: 0x0003e000, ABSOLUTE)
Execution Region ER_BINRAY_INFO (Exec base: 0x20000000, Load base: 0x20000000, Size: 0x0000002c, Max: 0xffffffff, ABSOLUTE)
Exec Addr Load Addr Size Type Attr Idx E Section Name Object
0x20000000 0x20000000 0x0000002c Code RO 751 * .text.Reset_Handler lto-llvm-483d6d.o
Execution Region ER_RAM_VECTOR_TABLE (Exec base: 0x20000100, Load base: 0x20000100, Size: 0x00000000, Max: 0xffffffff, ABSOLUTE)
**** No section assigned to this execution region ****
Execution Region ER_FLASH (Exec base: 0x20000100, Load base: 0x20000100, Size: 0x00000858, Max: 0xffffffff, ABSOLUTE)
Exec Addr Load Addr Size Type Attr Idx E Section Name Object
0x20000100 0x20000100 0x000000c0 Data RO 795 RESET lto-llvm-483d6d.o
0x200001c0 0x200001c0 0x00000008 Code RO 268 * !!!main c_p.l(__main.o)
0x200001c8 0x200001c8 0x00000054 Code RO 834 !!!scatter c_p.l(__scatter.o)
0x2000021c 0x2000021c 0x0000001a Code RO 838 !!handler_copy c_p.l(__scatter_copy.o)
You might notice that the key difference is the Reset_Handler is placed at the start of the 0x20000000
Exec Addr Load Addr Size Type Attr Idx E Section Name Object
0x20000000 0x20000000 0x0000002c Code RO 751 * .text.Reset_Handler lto-llvm-483d6d.o
This is the key difference.
In your map file, I found this:
Reset_Handler 0x200031e9 Thumb Code 24 lto-llvm-5f2a3e.o(.text.Reset_Handler)
This is the location of Reset_Handler in my map file:
Reset_Handler 0x20000001 Thumb Code 24 lto-llvm-483d6d.o(.text.Reset_Handler)
Based on this, I really want to check the linker script you actually use.
Program Size: Code=18804 RO-data=2152 RW-data=260 ZI-data=41148
After Build - User command #2: C:/Users/abg015/AppData/Local/Arm/Packs/RaspberryPi/RP2xxx_DFP/0.9.4/tools\elf2uf2.exe "C:\Users\abg015\Documents\Keil\test1-sram\Objects\rp2040_example.axf" ".\rp2040_example.uf2"
ERROR: A RAM binary should have an entry point at the beginning: 20000001 (not 20000181)
".\Objects\rp2040_example.axf" - 0 Error(s), 0 Warning(s).
The old-way of controlling linker settings in such simple scenario like this (just moving the code region to SRAM area) wasn't so bad;)
The Old way won't help.
This is because RP2040 BOOTROM only wants the Reset_Handler to be located at a specific location. This is different from STM32, which always read Reset_handler address from the vector table (RESET section in our case).
The so called old way or new way only affects how the STACK and HEAP are configured.
Activity
GorgonMeducer commentedon Jun 30, 2022
Please let the Pico team concentrate on what they should do. They don't have sufficient resources to add support for MDK.
For MDK support, please try this one:
https://github.com/GorgonMeducer/Pico_Template
myjtag commentedon Jul 3, 2022
JamesH65 commentedon Jul 3, 2022
That is a very ambitious claim since you don't actually know what our sales actually are...
We are looking in to alternative toolchains.
myjtag commentedon Jul 4, 2022
bgolab commentedon Jul 14, 2022
I am also interested in Keil support as I am heavy user of Keil for STM32 and so on.
I tried some some you can find here:
https://github.com/GorgonMeducer/Pico_Template
So some ground works is already done...
JamesH65 commentedon Jul 14, 2022
This is being looked in to. We do need support from ARM for certain things, which they will not be able to provide until the end of the year, unfortunately. In the meantime, lots of the toolchain already works.
myjtag commentedon Jul 18, 2022
bgolab commentedon Mar 15, 2023
I wonder if there is any update on this issue available.
GorgonMeducer commentedon Mar 15, 2023
@bgolab, The latest version of Pico-Template now supports flash downloading in MDK.
Please feel free to have a try.
myjtag commentedon Mar 16, 2023
will-v-pi commentedon May 21, 2024
We have now released an RP2xxx_DFP, which should work as a CMSIS solution for Keil tools. Feel free to give that a go and see if it works for you
37 remaining items
GorgonMeducer commentedon May 23, 2024
Once we use linker script, this kind of option won't affect the final result.
Can you pass me the map file?
As I mentioned above, I have updated the Pico-Template to use official RP2xxx_DFP. The reason I asked you to try it is because this could become the common example project for us to understand the reason behind the issue you encountered.
bgolab commentedon May 23, 2024
rp2040_example.map.txt
renamed to txt to upload...
GorgonMeducer commentedon May 23, 2024
@bgolab Can you attach the linker script also? The reason I ask this is because, the map file looks strange.
I know you suppose to use the linker script I provided, but just in case, please send me the one you actually uses
This is the one on myside:
You might notice that the key difference is the Reset_Handler is placed at the start of the 0x20000000
This is the key difference.
In your map file, I found this:
This is the location of Reset_Handler in my map file:
Based on this, I really want to check the linker script you actually use.
bgolab commentedon May 23, 2024
Current settings of the Linker tab and latest / freshest file (BTW. I have not touched the content of the linker file):

[RP2040_debug_in_sra
rp2040_example.map.txt
m.sct.txt](https://github.com/raspberrypi/pico-sdk/files/15417662/RP2040_debug_in_sram.sct.txt)
GorgonMeducer commentedon May 23, 2024
@bgolab You are not using the latest RP2040_debug_in_sram.sct
Please use the latest one.
https://github.com/GorgonMeducer/Pico_Template/blob/main/project/mdk/RP2040_debug_in_sram.sct
It is different from the one you currently using.
Thank you.
This is the one you using:
This is the latest one:
bgolab commentedon May 23, 2024
I lost control of this. This time should be ok:
Program Size: Code=18804 RO-data=2152 RW-data=260 ZI-data=41148
After Build - User command #2: C:/Users/abg015/AppData/Local/Arm/Packs/RaspberryPi/RP2xxx_DFP/0.9.4/tools\elf2uf2.exe "C:\Users\abg015\Documents\Keil\test1-sram\Objects\rp2040_example.axf" ".\rp2040_example.uf2"
ERROR: A RAM binary should have an entry point at the beginning: 20000001 (not 20000181)
".\Objects\rp2040_example.axf" - 0 Error(s), 0 Warning(s).
RP2040_debug_in_sram.sct.txt
bgolab commentedon May 23, 2024
rp2040_example.map (2).txt
GorgonMeducer commentedon May 23, 2024
@bgolab I managed to replicate the same issue on myside, please add
--entry=Reset_Handlerto the Misc Controls in the linker tab as shown below:Without this option:
With this option:
bgolab commentedon May 23, 2024
Yes, the '--entry=Reset_Handler' magic setting helped. It looks like not everything is controlled by the sct.
The old-way of controlling linker settings in such simple scenario like this (just moving the code region to SRAM area) wasn't so bad;)
Thank you.
bgolab commentedon May 23, 2024
UF2 verified by my script that the code is located in SRAM:
rp2040_example.uf2.log
GorgonMeducer commentedon May 23, 2024
@bgolab You mixed different things up.
The Old way won't help.
This is because RP2040 BOOTROM only wants the Reset_Handler to be located at a specific location. This is different from STM32, which always read Reset_handler address from the vector table (RESET section in our case).
The so called old way or new way only affects how the STACK and HEAP are configured.
bgolab commentedon May 23, 2024
Yes, I see. Got used to STM32;)
GorgonMeducer commentedon May 23, 2024
Current solution, i.e. using
--entry=Reset_Handleris just a workaround. PRi team needs a more elegant way to place Reset_Handler at 0x2000-0000bgolab commentedon May 23, 2024
It looks like the RP2 is not officially supported yet:
https://www.keil.com/dd/
GorgonMeducer commentedon May 23, 2024
@bgolab It is the legacy list...
Please check here: https://www.keil.arm.com/packs/rp2xxx_dfp-raspberrypi/boards/