-
Notifications
You must be signed in to change notification settings - Fork 2k
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
boards: add mcb2388 #12669
boards: add mcb2388 #12669
Conversation
1081b3d
to
a0053f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good in general but I have no hardware for testing. I just did a quick code review and found some things to change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@leandrolanzieri, @aabadie: I think code-wise this is fine. Please speak up if you find something that I have overlooked.
@benpicco: I should be able to test this with an MSB-A2, provided I override the programmer configuration, right?
I'm not sure how useful that would be. Last time I checked the MSB-A2 didn't have an LCD display or 8 debug LEDs. So you'd just be testing common code. |
I would attach a logic analyzers to the pins of the MCU. But this helps little to verify that the configuration indeed matches the pins the LEDs & LCD are actually connected to... |
I ran all the tests, the only failures were:
savannah.nongnu.org is currently down. Since this is all using 'virtual' network interfaces, I expect no board-specific surprises here anyway. Failures during test:
Will look into theses! |
Ran the tests again with the latest master. Failures during test:
huh? Those tests use the UART TX pin as GPIO for the driver - that won't work.
fixed by #13003
Uses
I'll squash the ADC commits should #12911 get merged before this, otherwise I'll remove them and add them in the other PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good.
@benpicco, do you have any idea on how to fix the remaining failing tests (tests/pkg_qdsa
, tests/pkg_libfixmath-unittests
, tests/unittests
). It seems to me that float support doesn't work well on this platform.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes are good so I won't block this anymore.
@benpicco, would you mind opening an issue to list the remaining failing tests on this board so we can keep track of them.
ACK, please squash (and remove the ADC related commits)
The MCB2388 Evaluation Board is a development board for the LPC2388 MCU. LPC2388 and LPC2387 are very simmilar, the only difference is added USB Host support. Since this is not used yet, I chose to just pretend it's an lpc2387. So far, only the two UARTs, LEDs and LCD display are configured.
Thank you for the review! |
Contribution description
The MCB2388 Evaluation Board is a development board for the LPC2388 MCU.
LPC2388 and LPC2387 are very similar, the only difference is that LPC2388 can also operate in USB host mode.
Since this is not used yet, I chose to just pretend it's an lpc2387.
So far, only the two UARTs, LEDs and LCD display are configured.
Testing procedure
I tried
examples/default
to blink the LEDs with SAUL.tests/driver_hd44780
also displays text on the LCD.Issues/PRs references
Was used for past and future
cpu/lpc2387
PRs.