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

GDB blocks after running the continue command in 2.2-hardware #332

Open
BikiniBottomsVeryOwn opened this issue Oct 18, 2022 · 1 comment

Comments

@BikiniBottomsVeryOwn
Copy link

Screenshot from 2022-10-18 02-02-15
Screenshot from 2022-10-18 02-02-39 Screenshot from 2022-10-18 02-04-41
Screenshot from 2022-10-18 02-02-58

using with the multiarch setup on ubuntu 22.04

@mavjs
Copy link
Contributor

mavjs commented Nov 15, 2022

@BikiniBottomsVeryOwn - if you have the same hardware as the book, in 2.2 hardware, there's a note:

NOTE If GDB blocks the terminal instead of hitting the breakpoint after you issue the continue command above, you might want to double check that the memory region information in the memory.x file is correctly set up for your device (both the starts and lengths).

In which case, make sure your LENGTH for RAM is 40k (RAM : ORIGIN = 0x20000000, LENGTH = 40K) and not 64k which is the default when you clone/generate from the template.

E.g.

$ cat memory.x
/* Linker script for the STM32F303VCT6 */
MEMORY
{
  /* NOTE 1 K = 1 KiBi = 1024 bytes */
  FLASH : ORIGIN = 0x08000000, LENGTH = 256K
  RAM : ORIGIN = 0x20000000, LENGTH = 40K
}

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