Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Robosight nv erase
03-12-2011, 12:45 PM
Post: #1
Robosight nv erase
i want to ask some question about Robosight.
How can erase non-volatile memory?
I use a standart CCS compiler for recompiling the source in windows (i hate from windows) and i see some envorimental problem (like not found "param.h"), how can i fix this problem(using which compiler ?). Thanks for interesting.
Edip
Find all posts by this user
Quote this message in a reply
03-14-2011, 02:46 PM
Post: #2
RE: Robosight nv erase
Hi edurdag-
We use MPLab when we need to overwrite the firmware on RoboSight non-volatile memory.

We also use MPLab to manage our build environment (see sample .mcp project file below). I recommend visiting a CCS forum to resolve issues with your build environment, because the following setup file is specific to our own installation.

Please let me know if this is helpful!
/d

//======= SAMPLE .mcp =====//

[HEADER]
magic_cookie={66E99B07-E706-4689-9E80-9B2582898A13}
file_version=1.0
[PATH_INFO]
BuildDirPolicy=BuildDirIsSourceDir
dir_src=
dir_bin=
dir_tmp=
dir_sin=
dir_inc=C:\PIC\Projects\RoboSight\fw\main4620\Common;C:\PIC\Projects\RoboSight\i​nclude\RoboSight;C:\Program Files\PICCH\Drivers;C:\Program Files\PICCH\Devices
dir_lib=C:\Program Files\PICCH\Drivers
dir_lkr=
[CAT_FILTERS]
filter_src=*.c
filter_inc=*.h
filter_obj=*.o
filter_lib=
filter_lkr=
[CAT_SUBFOLDERS]
subfolder_src=
subfolder_inc=
subfolder_obj=
subfolder_lib=
subfolder_lkr=
[FILE_SUBFOLDERS]
file_000=.
file_001=.
file_002=.
file_003=.
file_004=.
file_005=.
file_006=.
file_007=.
file_008=.
file_009=.
file_010=.
file_011=.
file_012=.
file_013=.
file_014=.
[GENERATED_FILES]
file_000=no
file_001=no
file_002=no
file_003=no
file_004=no
file_005=no
file_006=no
file_007=no
file_008=no
file_009=no
file_010=no
file_011=no
file_012=no
file_013=no
file_014=no
[OTHER_FILES]
file_000=no
file_001=no
file_002=no
file_003=no
file_004=no
file_005=no
file_006=no
file_007=no
file_008=no
file_009=no
file_010=no
file_011=yes
file_012=yes
file_013=yes
file_014=yes
[FILE_INFO]
file_000=RoboSight4620.c
file_001=C:\PROGRA~1\PICCH\devices\18F4620.h
file_002=C:\PROGRA~1\PICCH\drivers\stdlib.h
file_003=C:\PROGRA~1\PICCH\drivers\stddef.h
file_004=C:\PROGRA~1\PICCH\drivers\string.h
file_005=C:\PROGRA~1\PICCH\drivers\ctype.h
file_006=C:\PIC\Projects\RoboSight\include\RoboSight\RoboSight.h
file_007=C:\PIC\Projects\RoboSight\fw\main4620\Common\Bootloader4620.h
file_008=C:\PIC\Projects\RoboSight\fw\main4620\Common\RoboSight_fw.h
file_009=C:\PIC\Projects\RoboSight\fw\main4620\Common\Eeprom_data.h
file_010=C:\PIC\Projects\RoboSight\fw\main4620\Common\RoboSight_hook.h
file_011=RoboSight4620.SYM
file_012=RoboSight4620.TRE
file_013=RoboSight4620.STA
file_014=RoboSight4620.OSYM
[SUITE_INFO]
suite_guid={BA86BF99-4C07-4CE2-A9E7-C2A337910996}
suite_state=
[TOOL_SETTINGS]
TS{1BC4CBE6-8517-4656-ADCE-144170246122}=+DF +LN +T +A +M -Z +Y=9 +EA #RS_FW="1" #RS_STANDARD="1"
[INSTRUMENTED_TRACE]
enable=0
transport=0
format=0
[CUSTOM_BUILD]
Pre-Build=
Pre-BuildEnabled=1
Post-Build=
Post-BuildEnabled=1

/d
----
Daniel Packard
http://roadnarrows.com
daniel@roadnarrows.com
Visit this user's website Find all posts by this user
Quote this message in a reply
03-15-2011, 02:32 PM
Post: #3
RE: Robosight nv erase
Thank you quick reply Daniel. This is helpfull but i wonder, do you think solving this problem in "The RoboSight serial interface". Otherside if i misunderstand, when i write firmware with programmer then your original bootloader is erasing and i must desoldering pic18f4620 for this purpose. If i wrong, can you information waypoint procedure ?
because i understand if i want to erase non-volatile ram, i desoldering PIC18F4620 and programming with a programmer and soldering again.
Other question, i use same setup for recompiling in windows, but i see error in standart c headers(not found /sys/param.h like etc.) What is your standart C envoriment for this library ? I use ccs 4.049, what is your version ?
and do you try compiling in Linux for firmware because i prefer its.
Thanks for interesting.
Edip
Find all posts by this user
Quote this message in a reply
03-15-2011, 03:56 PM
Post: #4
RE: Robosight nv erase
(03-15-2011 02:32 PM)edurdag Wrote:  Thank you quick reply Daniel. This is helpfull but i wonder, do you think solving this problem in "The RoboSight serial interface". Otherside if i misunderstand, when i write firmware with programmer then your original bootloader is erasing and i must desoldering pic18f4620 for this purpose. If i wrong, can you information waypoint procedure ?
because i understand if i want to erase non-volatile ram, i desoldering PIC18F4620 and programming with a programmer and soldering again.
Other question, i use same setup for recompiling in windows, but i see error in standart c headers(not found /sys/param.h like etc.) What is your standart C envoriment for this library ? I use ccs 4.049, what is your version ?
and do you try compiling in Linux for firmware because i prefer its.
Thanks for interesting.
Edip

Hi Edip,

There is no need to de-solder anything on the RoboSight board. There is a programming interface that you can connect to the HID (see pictures below), but this should *only* be necessary if the RoadNarrows Bootloader is not functioning.

The RoadNarrows Bootloader should be sufficient for almost all re-programming purposes. The bootloader makes it easy to upload new software over the serial interface, and we provide online documentation, examples, and source code for programming new RoboSight software and firmware:
I'm afraid we cannot help with your programming environment (e.g. finding /sys/param.h).. You will find better help on this in CCS forums.

Best!
/daniel

[Image: IMAG0029.jpg]
[Image: IMAG0030.jpg]

/d
----
Daniel Packard
http://roadnarrows.com
daniel@roadnarrows.com
Visit this user's website Find all posts by this user
Quote this message in a reply
03-16-2011, 01:05 PM (This post was last modified: 03-16-2011 01:06 PM by edurdag.)
Post: #5
RE: Robosight nv erase
Hi Daniel,
I am sure you are very helpful...you did great job...i want to use this hardware HID interface. Can you send its connection schema because i will try some bootloader option next day and i think you use Microchip programmer like RJ11 for programming. I congratulate for this good working (software and hardware). I wonder do you supply schema for Robosight because i think if i writing code for this device i must know hardware. In fact i can to evaluate the circuit but if you supply i can have more time for coding. I want to work about some filtering and noise reduction problem with this structure and i will share its like you. Thank you very much Daniel for sharing information...

Best Regards
Edip
Find all posts by this user
Quote this message in a reply
03-16-2011, 04:45 PM
Post: #6
RE: Robosight nv erase
Hi,

We don't have an electronic version of the connection schema on hand... but here is a jpg that should contain the requested information.

/daniel

[Image: IMAG0030-2.jpg]

/d
----
Daniel Packard
http://roadnarrows.com
daniel@roadnarrows.com
Visit this user's website Find all posts by this user
Quote this message in a reply
03-17-2011, 01:30 PM (This post was last modified: 03-17-2011 03:05 PM by edurdag.)
Post: #7
RE: Robosight nv erase
Hi Daniel thanks for photo schema, you can relax for a while Smile
Find all posts by this user
Quote this message in a reply
03-20-2011, 02:52 PM
Post: #8
RE: Robosight nv erase
Hi Daniel,
I see this error building with MPLAB can you help for this error.Thank for interesting.


Executing: "C:\Program files\Picc\CCSC.exe" +FH "RoboSight4620.c" +EXPORT I+="C:\PIC\Projects\RoboSight\fw\main4620\Common;C:\PIC\Projects\RoboSight\include\R​oboSight;C:\Program Files\PICCH\Drivers;C:\Program Files\PICCH\Devices" +DF +LN +T +A +M -Z +Y=9 +EA #RS_FW="1" #RS_STANDARD="1"
--- Info 300 "RoboSight4620.c" Line 743(23,24): More info: ** Division by zero
*** Error 44 "RoboSight4620.c" Line 743(23,24): Internal Error - Contact CCS
C:\PIC\Projects\RoboSight\fw\main4620\RoboSight\RoboSight4620.o ===> 1 Errors, 0 Warnings.
Halting build on first failure as requested.
Halting build on first failure as requested.
BUILD FAILED: Sun Mar 20 23:46:46 2011
Find all posts by this user
Quote this message in a reply
03-21-2011, 03:08 AM
Post: #9
RE: Robosight nv erase
Hi Daniel,
It is solved, there are CCS problem.
Find all posts by this user
Quote this message in a reply
04-01-2011, 03:24 PM (This post was last modified: 04-01-2011 03:26 PM by edurdag.)
Post: #10
RE: Robosight nv erase
Hi Daniel,
How are you?
I want to use I2C output for reading to training category via an embedded linux computer.
Can you explain for this purpose I2C address programming for reading? in fact i want to know which chip output to me (CM1K ?, PIC18F4620 ?, PCFXXX ?) and i think you use 2 X 512K NVRAM on board is it true?
Can you show a sample I2C reading program via any linux system? If i use 3.3V level cominucation signal are there a problem because i think Robosight use 5V I2C signal?
Thanks for interesting.
Best Regards
Edip
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)