Hi Guys,
I am trying to make a eval board for M16/62P M30620FCPGP#U9 out of an old junk industrial product that happen to have all the things ( micro, power supply, RS232 level shifter) including debug port. I can read the data off the debug port when connected to Hyperterminal (spit out by the internal program). But when I try to connect to erase the Micro with FDT it does not communicate.I get an error: COM5 readout error. Debug port uses UART1 and these pins are set as CNVSS (H), P5.0(H), P5.5(L), NMI(H),BYTE(L). What I want to know is if this micro is locked for communication in programming mode? The FDT is set on 115200 bauds but no communication.
I am a beginer to Renesas micros so I want to know if I need to pop in a new micro to get the board going.
Any help will be greatly appreciated.
Thanks
I would like to add more info on this problem. I tried to connect to this board with FlashSta program from Renesas and I put in all zeros or FF as ID and I get a message "Not Match ID". Seems like there is a code lock on this micro. Any input guys. I am this close to changing the micro. ![]()
This is the output of FDT program which I tried before FlashSta.
Flash Development Toolkit and flash programming components
are provided without support
OS: Windows XP [Admin]
FCF Settings Applied: M30620FCP, (C:\Program Files\Renesas\FDT4.05\kernels\ProtD\M30620FCP\Renesas\1_1_00\)
Opening file C:\WorkSpace\Buzzer\an_rec05b0098_m16c_timer\workspace\rec05b0098_src\Release\rec05b0098_src.mot
File loaded: 0x000E0000 -> 0x000FFFFF [User Flash]
Warning - file truncated to match flash range (saving this file will cause data to be lost above 0x000FFFFF or below 0x000E0000)
File loaded: 0x0000F000 -> 0x0000FFFF [Data Flash]
Warning - file truncated to match flash range (saving this file will cause data to be lost above 0x0000FFFF or below 0x0000F000)
ID Code = 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF
Clock Frequency (External) = N/A, Clock Mode = N/A, CKM = N/A, and CKP = N/A
Connecting to device 'M30620FCP' on 'COM5'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM5' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Changing baud rate to 115200 bps
Error No 15005: 'COM5' read time out
Error No 15016: Changing baud rate to 115200 bps
May be you should try some lower baud rate than 115200?
The FDT protocol you list suggests that communication works at 9600. The error happens only when FDT tries to switch to 115200.
Especially at higher UART speed the possible speed depends a lot on the oscillator connected to the processor.
Thanks FrankL.
Here is the response after changing to 9600.ID window shows up and I filled in FF in all the places and I get ID code failure.
Opening port 'COM5' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Changing baud rate to 9600 bps
Error No 16194: ID code check failure
If you don't know the ID and all FF and all 00 don't work, then its game over.
There is no wa to erase a chip with a programmed ID (except for unsoldering the device and erase it in a parallel mode programmer, if this function is not also disabled).
That sound pretty clear. You need a new chip - someone locked it down with a 56 bit ID key. No erase, no reprogram.
Ok Then. I am pulling the plug on this chip.
Thanks for the help.![]()
Good news is that you can still use your board with a new chip.
Samples are free on-line:
http://america.renesas.com/products/mpumcu/m16c/m16c60/m16c62p/m16c62p_root.jsp
or request a completely free demonstration board here:
http://america.renesas.com/products/mpumcu/reach_further/child_folder/m16c_child.jsp
or request a completely free demonstration board here:
If you mean the SPB, then if you're still shipping that to new users, could you please make sure it's supported under Windows 7 64-bit? It would be bad publicity to send an eval board to someone who can't use it with a current OS, if they happen to have 7/64.
You make a valid point.
However, with kits and CDs sitting on shelves in inventory we're not always able to do that.
There is some information on installation of the kits with Vista, and Win 7 on this website.
However, I think it's reasonable to sticker the boxes with instructions on what to do with Vista and Win7 (and the 64 bit versions). We'll work on that.
I have ordered some samples.
I have read a lot about the bootloader. Is there a document that tell which micro uses which UART port for bootloader communication.
Thanks.
This information is always included in the device manual.
R8C/M16C/M32C/R32C devices use usually UART1.
H8/SH devices use often SCI1 or SCI3.
OK. Great. I will check it.
I changed the micro and it works. I can connect to it with FDT.
Thanks for all the help.
©2003–2009 Renesas Technology Corp. All rights reserved. Using Our Website | Privacy
Contact us