Use verbose keywords in linker fragments #5

sirhcel · 2021-06-11T21:53:39Z

When using flip-link for stack overflow protection, it parses the linker scripts/fragments for RAM memory addresses and expects the keywords ORIGIN and LENGTH to be used in its verbose form. Allow friction-less integration of flip-link and this crate by using the verbose form.

Otherwise using flip-link would result in an error like the following:

$ cargo build
   Compiling serial-test v0.1.0 ([...])
error: linking with `flip-link` failed: exit code: 1
[...]
  = note: rust-lld: warning: address (0x8001834) of section .rodata is not a multiple of alignment (16)
          Error: MEMORY.RAM not found after scanning linker scripts


error: aborting due to previous error

error: could not compile `serial-test`

Which is the discovery board used for this testsuite

This is needed, so probe-run can get enough information to verify a test sucess even in release mode

Now that this is fixed, examples are building again in the root folder and ci can use cargo -p testsuite again

This reverts commit 18c415b.

Accessing the USARTs TDR is safe again with stm32f3 0.13.2.

As this section gets bigger, I moved it into its own README.md in testsuite/.

Give more prominent information on wiring for test

Clean up unsafe write to USART TDR

Even after unplugging my STM32F3DISCOVERY MB1035D for several hours, I'm getting a noise error in this test case.

…ariants Accept different errors in send_receive_wrong_baud

When using flip-link for stack overflow protection, it parses the linker scripts/fragments for RAM memory addresses and expects the keywords 'ORIGIN' and 'LENGTH' to be used in its verbose form. Allow friction-less integration of flip-link and this crate by using the verbose form.

Sh3Rm4n · 2021-06-14T06:31:46Z

Thanks! This is a good catch. I've just disable flip-link in my case, because it was not building correctly but haven't looked into why that was the case.

I've cleanup the more-tests branch, so this patch is difficult to just merge this way. Instead I've just cherry-picked your commit into stm32-rs#212

Sh3Rm4n added 30 commits June 6, 2021 19:45

blablabla

7577049

Move tests to testsuite

a83e266

Add .toml to codegen cargo config

bc3ede9

fixup! Move tests to testsuite

a979f63

Adjust README for test execution

21235f3

WIP: Add some gpio tests

11d94c4

Add ld feature

c56bb63

Add gpio input test

e7b49ff

Add gpio push pull test

83f5c3f

Disable flip link usage

9ef6ec7

Relocate input test pins

c183fa9

Add gpio output open drain test

45c54e1

Add testsuite build step to ci

e6eaa75

Fix formatting

b84e0d2

Set test default feature to stm32f303xc

c110c4d

Which is the discovery board used for this testsuite

Enable full debug inforation for all cargo profiles

d8bf231

This is needed, so probe-run can get enough information to verify a test sucess even in release mode

Add pull up and down test

4299a70

Remove some warnings

4a6a4ba

Use cargo.toml in toplevel

4f1ed33

Now that this is fixed, examples are building again in the root folder and ci can use cargo -p testsuite again

Add defmt::Format derive to serial error

9c6b8ff

fixup! Use cargo.toml in toplevel

207d30d

Add uart test

d1db80e

Iterrrr

242b4ff

Some drafts for uart refactoring

f72864b

Add todo to usart tests

6f82816

fixup! Use cargo.toml in toplevel

5ea4fc7

Readd connect-under-reset-flag

0305a1d

Support defmt for dma example

6688e74

Add debugger asm::wfi workaround

c776411

Add adc tests

e740b27

Sh3Rm4n and others added 26 commits June 6, 2021 19:49

Cleanup serial

03d73c7

fixup! Implement read and write for serial

b574b93

Cleanup serial

572ac42

fixup! Implement read and write for serial

5a899bd

Cleanup serial

fbedf33

Seal serial TxPin and RxPin traits

fff70df

Cleanup serial

5289ad0

Some effors for Serial::join() method

ef0247f

Revert "Some effors for Serial::join() method"

f71f1a2

This reverts commit 18c415b.

Add Idle to serial interrupt events

2bf9ddf

Cleanup serial

b4a300e

Cleanup serial

736d6f0

fixup! Implement read and write for serial

30eef9a

Cleanup serial

be01c89

Add serial test for read write methods and different baud rates

fec8b87

Remove test matrix for testsuite CI build

d472554

Fix CI

57e7a37

Clean up unsafe write to USART TDR

b4cdb95

Accessing the USARTs TDR is safe again with stm32f3 0.13.2.

Give information on wiring for test execution

4e942fd

As this section gets bigger, I moved it into its own README.md in testsuite/.

Add image showing test wiring

c5d87aa

Merge pull request stm32-rs#2 from sirhcel/test-wiring-information

83446fe

Give more prominent information on wiring for test

Merge pull request stm32-rs#1 from sirhcel/safe-uart-tdr

a216cff

Clean up unsafe write to USART TDR

Accept different errors in send_receive_wrong_baud

1fffc37

Even after unplugging my STM32F3DISCOVERY MB1035D for several hours, I'm getting a noise error in this test case.

Fix some formatting issues moaned by linter

c7ed3c5

Merge pull request stm32-rs#4 from sirhcel/receive-wrong-baud-error-v…

bbe8d5a

…ariants Accept different errors in send_receive_wrong_baud

Sh3Rm4n force-pushed the more-tests branch 2 times, most recently from e123b09 to 95b17fc Compare June 14, 2021 06:29

Sh3Rm4n closed this Jun 14, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use verbose keywords in linker fragments #5

Use verbose keywords in linker fragments #5

sirhcel commented Jun 11, 2021

Sh3Rm4n commented Jun 14, 2021 •

edited

Loading

Use verbose keywords in linker fragments #5

Use verbose keywords in linker fragments #5

Conversation

sirhcel commented Jun 11, 2021

Sh3Rm4n commented Jun 14, 2021 • edited Loading

Sh3Rm4n commented Jun 14, 2021 •

edited

Loading