| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
It has never been an AF, it's always been an error to set this pin to
AF.
|
|
allows "make -j10" work properly
|
|
F3 rcc configs were overhauled and we can now use standard init code
instead of specifying our own custom clock config.
|
|
Not full test coverage, obviously, but at least let it compile until the
delay methods have been implemented.
|
|
|
|
This has failing tests, and doesn't implement (yet) the delay routines,
so it won't even compile without disabling that functionality in the
core gadget0 code. However, it passes most tests, and it demonstrates
that the changes made to the setup handling earlier haven't broken USB
on this platform.
|
|
This is based on linux's gadget0 intel loopback tests, and also github
pr: https://github.com/libopencm3/libopencm3/pull/592
Note that this captures the currently broken control loopback issues on
dwc_otg devices.
See https://github.com/libopencm3/libopencm3/issues/873 and all linked
issues.
Current status is passing on f3, f0, and failing on f4.
|
|
The loopback functionality was never implemented, not for regular bulk
endpoints. By adding it, and adding pairs of endpoints, we can easily
catch buffer management problems. These tests currently fail on
st_usbfs devices.
This did require renumbering the endpoints, as dwc_otg_fs only offers
three endpoints in each direction, and they can't be arbitrary numbers,
unlike on st_usbfs.
See https://github.com/libopencm3/libopencm3/pull/880 and related tickets.
|
|
Provided in ea5d3cb7 genlink: provide LIBDEPS for libopencm3 itself
|
|
Don't spew loop prints, be more like all the other targets.
|
|
Without this you get errors about not finding the linker script (because
it will be generated) and linker errors due to bare -l flags.
|
|
Brace expansion is not posix defined, even if it's widely available.
Avoid it's use for portability.
|
|
Another readily available board with a user USB port, and this one lets
you test the st usbfs peripheral on a device with trace facilities.
|
|
pyusb quirk.
|
|
There's still no commonly available l1 with usb from ST, so target our
own developed test host board instead of one developer's private board.
|
|
|
|
|
|
This helps catch some perhaps unintended api changes
|
|
Fixes: ec1d2855b stm32l1: rcc: use better naming for flash wait states
|
|
|
|
D+ is PA12 not PA11. The reason this worked before, is because the line
before made PA12 output, and without setting the GPIO_ODR register
_before_ hand, this meant as soon as it was switched to output, it
received the reset value of GPIO_ODR for PA12, ie, 0. (Effectively
doing a "free" gpio_clear(GPIOA, GPIO12)
Because GPIO11 wasn't configured to be an output, the confusing
gpio_clear(GPIOA, GPIO11) was simply configuring the pullup/down value
of the input, which was still ignored, as it was (out of reset) in input
floating mode.
Reviewed-by: Karl Palsson <karlp@tweak.net.au>
|
|
|
|
|
|
Attempt to be more brutal by delaying more often, instead of always
promptly servicing the usb stack.
This is implemented via using timer6 to do a known number of
microseconds busy delay, and so only works on platforms that have
reached at least core timer functionality, and provide the
rcc_apb1_frequency variable.
NOTE! This will _fail_ on devices using the st_usbfs drivers at present,
but the code _should_ work, and the tests land to verify that the
library fix, fixes the problem. (see subsequent commit)
|
|
Doesn't actually change the test results, but gets more coverage from
the same test case.
|
|
Less command line arguments, more automatic "do what I mean"
|
|
Connect to an existing and pass the correct path name.
|
|
Easier than editing the file each time.
|
|
Drop unnecessary ; in python
|
|
|
|
No real changes.
|
|
This currently fails on stm32F072, which is expected but not normal.
See GH issues #401 , #461
|
|
|
|
Fixes Github issue #652
|
|
|
|
Instead of having committed files containing a single developer's serials, use
optional includes to include a local config file for each board.
If you have only a single board connected, simply:
$ make -f Makefile.<board> clean all flash
If you have multiple boards connected, make sure to fill in the appropriate
hla_serial in your openocd.<board>.local.cfg file, and then run the same
commands.
|
|
|
|
See
https://docs.python.org/2/library/unittest.html#unittest.TestCase.longMessage
Allows showing the 42 != 69 : custom message instead of _only_ showing the
custom message if one was specified.
|
|
|
|
The F429i board has the user USB OTG port connected to the HS capable
OTG core, rather than the FS OTG core. It is still only operating in FS
mode, as you need a ULPI phy to use HS mode.
|
|
Fixes: 3a7cbec776bc9b9b53eefc26d5bf365466977e5a
|
|
|
|
As recently added to the library, allow the tests to be compiled with user
overridable flags too
|
|
Control transfers can transfer less than was requested by the host in the
wLength field. if this short transfer is a multiple of the endpoint's packet
size, a zero length packet must be sent.
Adds tests for a range of control transfer IN requests, and properly supports
this in the core. Based heavily on work by Kuldeep Dhaka.
See https://github.com/libopencm3/libopencm3/pull/505
and https://github.com/libopencm3/libopencm3/pull/194 for original discussion.
Tested with stm32f4, stm32f103 and stm32l053.
|
|
Don't commit commented out code! bad!
|
|
Eliminate warnings. carry over from developing in a different tree.
|
|
Much more complicated clock setup, but tests all pass once you get past that
step.
|
|
* Only the L1 needed to include flash settings
* whitespace and comment cleanup
* drop redundant clock setting calls
|
