YRPBRX62N – Renesas Promotional Board for RX62N Series Microcontrollers
YRPBRX62N – Renesas Promotional Board for RX62N Series
When I received this kit from Renesas to reveiw the immediate impression was that it would be just another evaluation board with I/O pins brought out to a connector. The tag ‘promotional board’ wasn’t helping much.
Once put to use, it proved to be a power-packed device, which, with the help of an embedded web server, highlighted the capabilities of RX62N series of Microcontrollers.
Accompanying small demo applications showcased the advanced features of the RX62N which include Ethernet Controller, USB Function and Floating Point Unit(FPU).
In-built Segger J-Link Debugger added to the compactness of the board eliminating the need for an external Debugger such as the E1.
The kit comes with
RX62N Promotional board – RPBRX62N
Mini CD with evaluation software, sample software and demonstration suit
The RPBRX62N uses a RX62N device with part number R5F562N8BDFP. This processor has an internal flash memory of 512 KB and SRAM of 96 KB which makes the device suitable for most advanced embedded applications. Internal communication peripherals such as UART, SPI, I2C, USB, Ethernet etc are available. Package is of 100 pin LQFP type and does not support external SDRAM or external DMA interface though other devices in the 144 and 176 pin pakcages do . Analog capability is provided by a 12 bit ADC and a 10 bit DAC.
The main crystal used is 12 MHz. As the device has a PLL inside, the frequency can be internally multiplied by software. 32 KHz crystal is used to generate dedicated RTC sub-clock.
Ethernet interface is done through a RJ45 connector while a standard mini-usb connector is provided for normal USB interface. Another mini-usb connector serves as the interface to the Segger J-Link Debugger. Through this connector the Renesas IDE - High performance Embedded Workshop connects to the chip and downloads code.
Several vital port pins are available with a 32 pin connector. The pin functions have been printed on the board on both sides for easy reference.
Apart from the above, the board has a user key and a joystick for evaluation of key inputs. Three LEDs provided can be used as status indicators by the firmware while testing. A potentiometer is connected to Analog 0 Channel.
Power is derived from the USB connector and is internally converted to 3.3V. A separate connector has been provided for external 5 V connection.
An I2C EEPROM 24C16 is connected to the I2C channel 0. LAN8700I , used for Ethernet Interface, is a 10/100 Ethernet Transceiver.
Extensive code with Sample applications based on Segger’s embOS real time operating system and emUSB, which is their embedded USB device stack, have been provided.
As my HEW had already crossed the time limit for evaluation, the code gave out memory limit errors. I installed the IDE in another computer and then ran the code. The webserver sample application worked flawlessly.
I could display images and shapes on a SED1335 based Graphic LCD(320 X 240) connected to the 32 pin connector. User key and potentiometer inputs were also checked by displaying values and changing image shapes.
Overall, the RPBRX62N not only proved to be useful in evaluating the controller’s features but also doubles as a downsized alternative to a full version Evaluation kit such as the RSKRX62N.
CommentsAdd a comment
If you just want to create a single Schematic & PCB then you need to keep to the same name if you want to do integrity checks and back annotate. If you need to use different names for the Schematic and PCB then all you need to do is create a Project: File / New and on the 'New Menu' select Project then and give it a new Project Name, let's call it Fred. Then when you open a new Schematic you are given the option to add this to an open project calling it say 'Jack' and after you translate to PCB you can give it a different name, say 'Jill'. DesignSpark PCB will then keep these names linked within the Fred project.
Hi,when one want to create the PCB from the Schematic, he uses Tools > Translate to PCB. You may then name the PCB what ever you wish. Say the Schematic name is Mysch and you chosse Mypcb v1 as the pcb name. The PCB will be created fine.But if you edit the schematic and then use Tools > Forward Design Changes, you get an error stating that Mysch.pcb is not found. Looks like you have to name the PCB the same as the Schematic, and in the same directory. Is it a bug or a feature ?Instead of throwing an error, DS should ask for the name of the PCB file. This way you could have more than one PCB files for a Schematic file in order to explore more than one designs.