We have now successfully tested the LPC-P1343 and LPC-1766STK prototype boards from Olimex so we have added them to the list of supported development boards:
http://www.astrobe.com/boards.htm
Search found 440 matches
- Wed Apr 25, 2012 12:38 am
- Forum: Astrobe for ARM Cortex-M0, M3, M4 and M7
- Topic: Olimex LPC-P1343 and LPC-1766STK now supported
- Replies: 0
- Views: 17741
- Thu Apr 05, 2012 11:24 pm
- Forum: Cortex-M0, M3, M4 and M7
- Topic: Blinker for LPC17xx
- Replies: 0
- Views: 13921
Blinker for LPC17xx
The following example works on the LPC1751 and LPC1756 boards from Coridium. MODULE Blinker; (* Example Cortex-M3 Oberon Program for NXP LPC17xx Led connected to P2.10 blinking approx. once per second *) IMPORT Main, MCU, SYSTEM, Timer; PROCEDURE Run(); CONST (* led connected to pin P2.10 *) ledBit ...
- Thu Feb 23, 2012 12:45 pm
- Forum: Oberon Language
- Topic: Concatenating string constants
- Replies: 4
- Views: 32655
Concatenating string constants
We are considering implementing an extension to Oberon in Astrobe to allow the use of + as a concatenation operator for string constants. This would be useful if you wanted to include double-quotes or non-printing characters in strings. e.g. CONST QuotedString = 022X + "String" + 022X; or if you pre...
- Fri Feb 03, 2012 7:13 am
- Forum: Astrobe for ARM Cortex-M0, M3, M4 and M7
- Topic: Oberon running on Cortex-M3
- Replies: 4
- Views: 33484
Re: Oberon running on Cortex-M3
We are still on track (despite the temporary diversion to implement the changes caused by the 2011 revision of Oberon) to our August 2011 announcement:
"Q2 2012 or possibly Q1 2012 if everything goes as planned"
"Q2 2012 or possibly Q1 2012 if everything goes as planned"
- Wed Feb 01, 2012 11:29 am
- Forum: Oberon Language
- Topic: Exported pointer variables
- Replies: 15
- Views: 89626
Re: Exported pointer variables
(By the way, when it comes to export of variables I would also have liked to be able to export character arrays which makes sense since strings can be exported.) That does not follow. strings are constants character arrays are variables . In the case of executables created using Astrobe the differe...
- Wed Feb 01, 2012 11:16 am
- Forum: Oberon Language
- Topic: Exported pointer variables
- Replies: 15
- Views: 89626
Re: Exported pointer variables
... my standpoint is that the inability to modify an exported field though an exported pointer (as in my example) represents a minor compiler bug That is not correct. Unless I have misunderstood what you are saying I believe you have 'got the wrong end of the stick'. The system is designed to try t...
- Tue Jan 31, 2012 8:22 pm
- Forum: Oberon Language
- Topic: Exported pointer variables
- Replies: 15
- Views: 89626
Re: Exported pointer variables
Sorry - I accidentally overwrite your reply when attempting to reply to it. Post it again if you like.
- Mon Jan 30, 2012 9:23 pm
- Forum: Oberon Language
- Topic: Exported pointer variables
- Replies: 15
- Views: 89626
Re: Exported pointer variables
That is how it is intended to behave. A read-only record is just that. It cannot be modified outside of the module where it is declared - neither by an attempt to modify the entire record in a single assignment, or by attempts to modify elements of the record with separate assignments. t1 is differe...
- Sat Jan 28, 2012 6:44 am
- Forum: Astrobe for ARM Cortex-M0, M3, M4 and M7
- Topic: Oberon running on Cortex-M3
- Replies: 4
- Views: 33484
Oberon running on Cortex-M3
This afternoon we have successfully used Astrobe to develop and run our first Oberon program (Blinker, of course!) on an ARM Cortex-M3 MCU. The Embedded Artists LPC1343 you can see in the photo may well be the smallest dev board that an Oberon program has ever run on: http://www.astrobe.com/images/L...
- Mon Dec 12, 2011 11:55 am
- Forum: Astrobe for ARM Cortex-M0, M3, M4 and M7
- Topic: Trap in MAU
- Replies: 6
- Views: 45625
Re: Trap in MAU
NEW only ever allocates memory - it never frees any memory. When you use NEW on a local dynamic array as in your example the memory is allocated on the stack (not the heap), just like the memory used by other local variables. When you exit from the procedure the memory used by the dynamic array is r...