 |
||||||||||||||
|
|
|
||||||||||||
CW2's ContentThere have been 148 items by CW2 (Search limited from 29-June 23) #60045 USB power vs. input power
Yes.
You don't need an industrial grade power supply, a wall adapter is sufficient.
No, the onboard linear regulator requires at least ~6.5 V input. #58673 VC0706 Adafruit camera and Netduino Plus 1
Ok, thanks for the clarification. This was fixed in .NET Micro Framework 4.3 (see Issue #1388), you can set Convert.UseRFC4648Encoding property in order to get '+' and '/' instead of '!' and '*': System.Convert.UseRFC4648Encoding = true; #59528 Using Netduino to prototype & program a chip...
If I understand it correctly you want a custom board running Netduino firmware? Of course that is possible, as long as it is hardware compatible (e.g. clock frequency, inputs/outputs etc.). However, you'd need to have very good component source deals to make it cheaper (the microcontroller itself in single quantity costs significant part of the retail Netduino price, plus the other parts, PCB, assembly, testing etc.). #60758 DateTime in NativeEventHandler()
Unfortunately, I don't know the accuracy. #56639 ND1 - Input is always TRUE
Quiz question: What return value do you expect from an unconnected input pin?
The thing is that you created input pin with ResistorMode.PullUp, which means the pin is in logic high (returns true), unless it is connected to other logic level (logic low, ground). Thus, if you want your input pin Read() method to return false, you have to wire the pin to GND.
If you use a port in output mode, its Read() method basically just returns the current state - i.e. the initial state passed via constructor parameter or what was set in the last call of Write() method. #61398 Native code interop
That is correct, in the current implementation of .NET Micro Framework, managed code (CIL) is interpreted (there is no JIT). #60257 Help! I've accidentally bricked my brand-new Netduino 1 when updating...
What guide are you following? ST tools do not work with Netduino 1, you have to use Atmel SAM-BA. #57035 Interrupt Port and Input Port Read Values are Wrong on First Interrupt.
I have not tried to reproduce the behavior, but there is one fundamental issue with using port.Read() in the interrupt handler: because the interrupts are queued, the handler is executed after a certain period of time, thus port.Read() returns the port state at the time the interrupt handler is being executed, not when the interrupt occurred. This can cause incorrect results, especially when the pulse duration or frequency is close to execution time of the interrupt handler (managed code).
I guess a better way is to use two interrupt ports, both set up for falling and rising edge (InterruptEdgeBoth) and use the handler parameters data1 (port number), data2 (port state, 1/0) and timestamp in a state machine (you can reuse one xxx_OnInterrupt handler). #56666 ND1 - Input is always TRUE
#59936 Maximum port frequency ...
You should have mentioned that in the original post - Shield Base has STM32F205 microcontroller that runs at 120 MHz, Netduino Go STM32F4 at 168 MHz. So, not enough for 145 MHz pin toggling even when done in assembly... #60711 Netduino Plus 2 SPI Possible Speeds?
The prescaler values are just for the SPI modules, SPI_CR1 register bits BR0..BR2. #60696 Netduino Plus 2 SPI Possible Speeds?
There are three SPI modules on Netduino Plus 2 microcontroller connected to two system busses: SPI1 on APB2, SPI2 and SPI3 on APB1. The bus frequencies are 42 MHz and 84 MHz and 3 bit prescaler is /2, /4, ... /256, which gives the following clock speeds:
Prescaler APB1 APB2
42000000 84000000
2 21000000 42000000
4 10500000 21000000
8 5250000 10500000
16 2625000 5250000
32 1312500 2625000
64 656250 1312500
128 328125 656250
256 164062 328125
I guess the firmware selects speed closest to the above values, the actual code is UINT32 clock = SYSTEM_APB2_CLOCK_HZ / 2000; // SPI1 on APB2
if (Configuration.SPI_mod != 1) clock = SYSTEM_APB1_CLOCK_HZ / 2000; // SPI2/3 on APB1
if (clock > Configuration.Clock_RateKHz << 3) {
clock >>= 4;
cr1 |= SPI_CR1_BR_2;
}
if (clock > Configuration.Clock_RateKHz << 1) {
clock >>= 2;
cr1 |= SPI_CR1_BR_1;
}
if (clock > Configuration.Clock_RateKHz) {
cr1 |= SPI_CR1_BR_0;
}
spi->CR1 = cr1;
where SPI_CR_BR_0..2 are prescaler bits (or-ed to give 0..7).
#60744 Netduino Plus 2 SPI Possible Speeds?
Yes, you should be able to lower peripheral clock speed by adjusting the bus clocks frequencies. But, when you start playing with PLL settings, keep in mind that the USB FS module requires 48 MHz clock to operate properly. #59589 Convert PIC code to run on Netduino
Why not use the PIC?
There are some issues with the current .NET Micro Framework implementation that limit its usage in such scenarios. I don't know exactly how the PIC drives the H-Bridge, but I can think of
1) Bit-banging - it depends on the frequency. Netduino's managed code is interpreted, i.e. slow. IIRC it can produce signal at 10 kHz range - I am not sure how fast you need to drive those power MOSFETs. Also, the code can be disturbed at any time, for example by garbage collector or interrupt handler, so the motor control will be stuck for relatively long time in certain state, which is not something you'd want. There are some techniques to minimize such events, but no guarantees.
2) Timers or PWM - there is missing the key feature: synchronized channels. The signals for left and right part of the H-Bridge must have precise relationship, they cannot overlap at certain moments etc. - usually, you configure two channels with opposite polarity, dead time and then start them at the same time. This would require firmware modification (the microcontroler has these features, but they are not accessible from managed code).
Personally, I would go with the PIC(s) - you've already got proven working (?) design, it is much better for real-time control, and also significantly cheaper. You can use Netduino to control them, if you must... #57392 Adding to Cpu.Pin enumeration
You can access those pins via Cpu.Pin enumeration - the ports are treated as consecutive array of pins, so PA is 0 .. 15, PB 16 .. 31, PC 32 .. 47 etc.: var pa4 = (Cpu.Pin)( 0 + 4); var pb1 = (Cpu.Pin)(16 + 1); var pc0 = (Cpu.Pin)(16 + 0); var pc8 = (Cpu.Pin)(32 + 8); #57051 Analog Output
In addition to what Nevyn said, you could use PWM with low-pass RC filter as cheap D/A converter. #58426 Netduino alternative development options
I am not sure what exactly you are asking... you kind of answered your own question in the last sentence in the original article.
It is certainly possible to program Netduino boards in C/C++, using toolchains you mentioned above. I am not familiar with ARM DS-5, but if you are looking for IDE then there are for example free/evaluation version of commecial products like Keil MDK Lite, IAR EWARM, CrossWorks for ARM, free CooCox CoIDE etc. Usually, they come with a few sample applications and sometimes even with higher level libraries...
You can use any RTOS, as long as the appropriate microcontroller port is available, using supported toolchain/IDE - you'd have to check the particular RTOS documentation, based on what exactly you need/want to do. #58430 Netduino alternative development options
For STM32F-based Netduinos (gen 2), you can use DfuSe utility to upload firmware when the device is in USB bootloader mode. During development, it is better to use JTAG or SWD in-circuit debugger/programmer, such as ST-LINK/V2.
Usually, the IDE supports at least one such debugger, so it is relatively easy to deploy the compiled binaries, place breakpoints and step through the code... #60743 Custom building a smaller Netduino 2
Very nice board !
Although, on the photo it seems that there are parts and traces very close to the mounting holes, maybe so close that the screw head could touch them or even cause some damage (?) #59233 Multiple InterruptPorts being fired?
I guess the output of toggling switch UP is affected by DisableInterrupt() and EnableInterrupt() calls in the event handler - it most likely causes the other interrupts to be ignored/missed.
I would recommend you to remove those Disable/EnableInterrupt() calls; and also change the interrupt trigger to InterruptEdgeHigh, so the button release event is not generated (you can add it back again later, if you need it). Also, apparently the switch bounces, so you'd need to implement either hardware or software debouncing (or both).
You can make the circuit a little bit simpler by switching to pull-up resistors, because you can enable the built-in ones (in the InterruptPort constructor); then you'd need to use InterruptEdgeLow instead. #59591 Convert PIC code to run on Netduino
If the main project objective is NOT building a motor controller, I would consider one of the many motor controller modules or specialized driver ICs... just for inspiration Pololu controllers... #59786 ISR in interop
You should be able to hit a breakpoint in an ISR handler - if you can't, it can indicate it is never called (do you actually activate/enable it in your code?).
What version of Netduino do you have? Are you developing a port for a new microcontroller? There is already USART ISR handler implemented in the firmware - you can use it as a reference for things needed to get it work (e.g. configure pins, enable peripheral clock, activate interrupt, setup USART module, use locks etc.). #59789 ISR in interop
When you use your ISR handler, have you disabled/removed the one in the firmware? There will be a conflict - .NET Micro Framework does not have any support for hardware resource sharing/management, so one must be a little bit careful when adding custom functionality.
Also, there are some things you have to add to your native code (which works in Keil) to make it work correctly in .NET Micro Framework - such as properly reserve the pins, use lock macros, etc. #59790 ISR in interop
CPU_INTC_ActivateInterrupt(g_STM32_UART_Irq[uartNum], STM32_USART_Interrupt0, 0); GPIO ISR is used in STM32_GPIO_functions.cpp to handle pin interrupts, does not do anything with USART. #60476 Receiving Junk from Serial Port
| ||||||||||||||
|
||||||||||||||
|
|
|
||||||||||||
|
This webpage is licensed under a Creative Commons Attribution-ShareAlike License. | |
||||||||||||
|
||||||||||||||
Posted by
