Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - modtro2

Pages: 1 2 [3] 4 5 ... 38
31
SBC66EC & SBC66ECL / Re: Does the Real Time Clock finally work?
« on: December 08, 2014, 09:34:50 PM »
Hi, I have uploaded the the netcruzer project, v2.03 to GitHub. The RTC is now supported, and working. For an example of how to use the RTC, see the "src/demos/rtc/rtc_debug_demo/main.c" folder. It is here on GitHub:
https://github.com/modtronix-com/netcruzer-src/blob/master/src/demos/rtc/rtc_debug_demo/main.c

You can build this demo, and program your SBC66 board with it. After doing that, use the Netcruzer USB Terminal to set time, print current time and perform other tests. See towards the end of the main.c file where the tests are performed.

32
Hello Marcelo

Thanks for your mail! Before you decide on a module, ensure that you test the RF board! Our SX1276 inAir9 boards are 4 layer, and designed in coroperation with Semtech Engineers. They reviewed the design, and recommended many design changes. We have evaluated a couple of the cheap boards available on internet, and they didn't even get close to the advertised range of LoRa. Some of the SX127x modules you listed in your post use a 2 layer PCB, and are VERY badly designed, not taking any RF PCB design requirements into consideration!

We aim to make the STM32L151 & SX1276 combination modules available for between USD30 to USD38. The SX1276 board should be about USD14 to USD18. We might make a lower price module available, removing the LiPo charger and DC/DC switch mode circuitry from the STM32 board. Will your application be powered by battery - will you be using the battery charger feature of the STM32 board?

We are busy adding the inAir9 (SX1276 board) to our site today. Should be done within 4-8 hours.

We have plenty of revision 1 STM32L151RC boards in stock. But, will not be adding it to our site. We are busy with a revision 2 that will change quite a couple of stuff. But, this will only be available in 2-3 months time. In the mean time, we can supply revision 1 boards on request. The main changes from rev1 board will be:
  • Enlarge size of pin header holes, they are very small, and pin header fits very difficult
  • Put all pins required for programming board on one side. This will enable simple 6 pin connector to be used to connect ST Link or other programmer to board
  • Add some more CPU port pins to pin header. Some CPU pins are currently not available on the pin header.

But, the revision 1 board works perfect. The main issue is just that you have to connect the ST Link programmer to 2 pins on 1 side, and 2 pins on the other side of the board. It is not that convenient. For compiling your project, you can use offline CoIDE or emBlocks with mbed API, or any other ARM compiler. We will soon place the mbed project on GitHub. The advantage of this code is that it will include the API for the SX1276 chip. Would you want to use it with mbed API? Would you be interested in helping test board, and post results online? For example, create a post on our forum with details of your code, and what you did. If you want to do this, I can send you a free CPU + SX1276 board.

33
SBC66EC & SBC66ECL / Re: SBC66ECL with no UART demo code? No thanks!
« on: November 30, 2014, 05:33:25 PM »
Hello Apostolis

We have a new beta firmware on our site with UART supported for UART1. Will soon update code to support all UARTs. Please let me know what you want to do? Do you need to access any UART functionality in your webpages? Or, you just need the API to read/wire from/to UART from C code? I can add an example for using UART to our online examples.

34
This board will use the STM32L151RC CPU, and will be followed by versions fitted with different CPUs:

===== NZ32-ST0A (or just NZ32-ST0) =====
STM32F030R8T6 - M0, 64K, 8K Ram, 0 EEPROM, 64Pin, 48MHz
f2xI2C, 2xSPI, 2xUSART, 0xCAN, 0xUSB, 10xTimers
1xADC 18x12bit, 0xDAC 12bit

===== NZ32-ST1C =====
STM32F103RCT6 - Maybe, have not decided yet. Seem like the STM32F1 processors have lots of Errata!

===== NZ32-ST2C (or just NZ32-ST2) =====
STM32F205RCT6 - M3, 256K, 100K Ram, 64Pin, 120MHz
3xI2C, 3xSPI, 6xUART/USART, 2xCAN, 2xUSB, 17xTimers
3xADC 16x12bit, 2xDAC 12bit

===== NZ32-ST3C (or just NZ32-ST2) =====
STM32F302RCT6 M3, 256K, 40K Ram, 64Pin, 72MHz
3xI2C, 2xSPI, 3xUART 2xUSART, 1xCAN, USB, 11xTimers
2xADC ?x12bit, 2xDAC 12bit

===== NZ32-ST4C (or just NZ32-ST4) =====
STM32F411RCT6  - M4F, 256K, 128K Ram, 64Pin, 100MHz
3xI2C, 5xSPI, 3xUART/USART, 0xCAN, 1xUSB, 11xTimers
1xADC 16x12bit, 0xDAC


35
Hello, can you please try replace following line in "serportUSB.c"
Code: [Select]
#if defined(__C30__)
    USBSleepOnSuspend();
#endif

with

Code: [Select]
#if defined(__C30__)
    //Disable sleep on suspend!
    //USBSleepOnSuspend();
#endif

This is from the current 2.03 Beta. I haven been using 2.03 for all custom project. I would recommend you also use 2.03.
http://forum.modtronix.com/index.php?topic=1551.0

36
STM32 Boards (NZ32 Range) / === New NZ32-ST1L board with STM32L151RC ===
« on: November 14, 2014, 10:23:50 PM »
We will soon be introducing a new, low cost range of STM32 boards. Main features are:
  • STM32L151RC Ultra low power CPU, optimized for low power applications (compatible with other STM32L151 and STM32L152 chips).
  • 256K Flash, 32K RAM, 8K EEPROM.
  • 3 x UART/USART ports, 2 x I2C ports, 3 x SPI ports.
  • 1 x Micro B USB Port.
  • Reset and Boot button.
  • 2 LEDs, one for indicating when battery is charging, and a user LED.
  • Firmware upgradable via USB port. If boot butter is pressed at power up(reset), board goes into bootloader mode.
  • Very low power 5V to 3.3V switch mode regulator with 16uA operating, and 0.01uA standby current.
  • Switch mode can be disabled by CPU, resulting in 0.01uA current, which is sufficient to run CPU for minutes in low power mode (run from power stored in Capacitors).
  • On board LiPo (lithium polymer) battery charger, and standard 2.0mm JST connector (many LiPo batteries have this connector). LED indicates when battery is charged. Can be charged from USB or 5V pin headers.
  • Hardware for monitoring input and battery voltage.
  • Additional regulator output capacitors to allow board to run for longer when switch mode is in standby mode (ultra low power 0.01uA operation).

    Click here for larger image.

    Click here for larger image.

=== Wireless Interface ===
These boards will feature 3 iMod ports. One on top, and two at the bottom. Versions of this board will be available with the top iMod port assembled with a WiFi, Bluetooth or SX1276 Wireless module. The SX1276 incorporates Semtech's LoRa technology, making very long range communication (over 10km) possible at low power! The photo below shows the NZ32-ST1L with a SX1276 iMod mounted on top, and pin headers assembled on the bottom (in the 2 bottom iMod ports).


=== Programming and Debugging ===
The boards can be programmed using the following methods:
  • Using the STM32 built in USB or UART bootloader. This mode is enabled by holding the "Boot" button down after reset (pressing reset button).
  • Using 2 wire SWD.  SWD uses an ARM standard bi-directional wire protocol, requiring only 2 wires for programming and debugging.
  • Using a 4 pin header, this board can be connected to an mbed programmer, allowing drag and drop and CMSIS-DAP programming and debugging.
  • Via ST-LINK or J-Link, but connecting a ST-Link or J-Jink programmer to the SWD pin.
The image below shows the location of the 5 pin SWD header. A reduce 4 pin header can also be used.


=== Optional Programming/Debugging daughter board ===
This option is still in prototyping stage. We are developing a small daughter board that plugs onto this new board. It will provide:
  • Debugging and Programming via ST-LINK or CMSIS-DAP interface
  • Virtual Com port allowing communication with main board (via UART)
  • Mass storage (USB Disk drive) for drag'n'drop programming
It will either use exactly the same circuit as present on the STM32 Nucleo boards (ST-Link programming/debugging), or the CMSIS-DAP firmware (CMSIS-DAP programming/debugging) provided by mbed - see this page.
The image below shows how this board will be mounted. To reduce cost, it can be a plug-in module. Only used during prototyping.

37
Hi, I also have win7, 64bit. I have never had that problem before. Do you have the standard firmware on the board, or have you modified it? I can not imagine the standard firmware can do this, it is used by many customers, and I have never encountered this problem.

38
Shields and Other / Re: FTDI Basic 5/3.3V programmer how to select 3.3V
« on: September 22, 2014, 07:19:06 PM »
See this picture

39
Shields and Other / Re: FTDI Basic 5/3.3V programmer how to select 3.3V
« on: September 22, 2014, 06:47:09 PM »
Hi! I updated the documentation on the FTDI Basic programmer page. Basically pin 3 of the 6 pin connector is always 5V, as marked on the PCB. See FTDI Programmer product page for detailed information.

40
General Questions / Re: Archived versions of Netcruzer Download?
« on: September 09, 2014, 07:41:32 PM »
Hi, you can look in the root "netcruzer download" folder. The version number is in the "netcruzer_download_changelog.html" file.

You can download the required version from our site at "www.netcruzer.com/nz/netcruzer_vxxx.zip", where "xxx" is the version number. For example:
www.netcruzer.com/nz/netcruzer_v202.zip

41
General Questions / Re: Archived versions of Netcruzer Download?
« on: August 28, 2014, 09:27:42 PM »
Hi, what version do you want? And, if I may ask, why do you want a previous version?

42
We will soon be adding Arduino example code showing how to read a matrix keypad, and write to outputs OUT1 and OUT2. The LCD2S has 2 general purpose open collector outputs, OUT1 and OUT2. These outputs can supply up to 1000mA, and have protection circuitry for driving relays.
  • When using only OUT1, a 4x4 (16 button) or smaller keypad can be used.
  • When using OUT1 and OUT2, a 4x3 (12 buttons) or smaller keypad can be used.

Using a 4x4 Keypad and OUT1
When using a 4x4 keypad, the OUT1 output is NOT available. The keypad is connected to the pins marked R1 to R4 (rows) and C1 to C4 (columns) on the X1 1x10 pin header. The LCD2S has built in button debouncing, which can be configured for different values. The default should work fine though.


Click for larger view

Using a 4x3 Keypad, OUT1 and OUT2
When using OUT1 and OUT2 outputs, the largest keypad that can be used is a 4x3, 12 button keypad. The keypad is connected to the pins marked R1 to R4 (rows) and C1 to C3 (columns) on the X1 1x10 pin header. The C4 pin can not be used (function is shared with OUT1). The "OUT1" jumper on the X1 (1x10 pin) header also has to be inserted.


Click for larger view


43
Serial LCD Displays / == Arduino I2C Source Code for IO functions ==
« on: August 17, 2014, 12:54:17 AM »
We will soon be adding Arduino example code to this post showing how control the OUT1 and OUT2 outputs. The LCD2S has 2 general purpose open collector outputs. These outputs can supply up to 1000mA, and have protection circuitry for driving relays. Both OUT1 and OUT2 are enabled by default. They are available via the X3 connector (2x6 pin header).

Output OUT2 does not share port pins with any other function, and is always enabled.

Output OUT1 shares a port pin with the keypad encoder, and can only be used when the keypad encoder is configured for a 4x3 keypad (4 rows by 3 columns = 12 keys) or smaller. It is enabled by inserting a jumper on the end of the 2x6 pin header (marked OUT1 on PCB). It is enabled by default, and this jumper is present. When the keypad encoder is configured for a 4x4 keypad, this jumper must be removed! Output OUT1 can not be used when using a 16 key, 4x4 keypad!



Click for larger view

44
Serial LCD Displays / == Arduino I2C Source Code for Keypad functions ==
« on: August 17, 2014, 12:53:56 AM »
We will soon be adding Arduino example code showing how to read a 4x4 matrix, 16 button keypad with Arduino. The keypad is connected to the pins marked R1 to R4 (rows) and C1 to C4 (columns) on the X1 1x10 pin header. The LCD2S has built in button debouncing, which can be configured for different values. The default should work fine though. The OUT2 output is also available when using a 16 button keypad.



Click for larger view - with 16 button keypad.


Click for larger view - with 16 button keypad and relay connected to OUT2.

45
Webserver Firmware / Re: software timer interrupt
« on: July 17, 2014, 11:19:47 PM »
Hi, when writing embedded code, you must always take care what functions you call from an interrupt ISR. Best is to keep your ISR code as short as possible, and not call any functions from it. If you have to call functions from within an ISR, special care must be taken that they are thread safe. The TickGet() function should not be called from within an ISR. Is there a work around you could use? Could you possibly post your ISR code.

Pages: 1 2 [3] 4 5 ... 38