schouteq
Newbie
Posts: 41
|
 |
« on: March 09, 2010, 07:35:19 AM » |
|
Hello,
I think that a bad image is flashed on my ChipworkX System! I tried a couple different things: Opening the Script file and SAM-BA to flash my device! But my device isn't recognized in windows and can't be found. I tried COM1 on my board and this only shows the text "RomBOOT". Is there a way to erase all my memory and flash it again, because the board is still working/
Kind Regards.
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #1 on: March 09, 2010, 08:27:38 AM » |
|
1. disconnect everything
2. remove jumper on bottom side that is on chipworkx *module*
3. power the device and plug in the serial cable
4. place the jumper pack
5. flash your device
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #2 on: March 09, 2010, 08:46:21 AM » |
|
and which program do i use and which com port.
Kind Regards
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #3 on: March 09, 2010, 08:53:01 AM » |
|
SAM-BA as described in manual.
You need to make sure your windows sees a new COM port after you are at step 4 (before you do step 5). Open windows "device manager" and verify that the driver is installed and after you do the steps you see a new COM port device....if you remove the USB cable then that COM port should disappear.
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #4 on: March 09, 2010, 08:55:35 AM » |
|
That is the problem my windows doesn't see a new COM port. Otherwise i could flash my device.
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #5 on: March 09, 2010, 08:59:52 AM » |
|
If you followed the steps and still have no luck then the device is probably defective.
Is this the development system or your own board?
Do you see anything on the screen?
If you follow the step I mentioned before, do you see a new COM port?
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #6 on: March 09, 2010, 09:05:25 AM » |
|
It's the ChipworkX Dev. System and it's still working i think, because when i connect COM1 from the Dev. System to my rs-232 port on my computer i still get an response. So everytime i reboot the board is see the text "RomBOOT" in my terminal. The screen is completly white. When i connect through USB there is no new device added and the device isn't visible in the windows device manager.
The problem occurred when i updated the TinyBooter Firmware. The system did work but after the update not anymore!
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #7 on: March 09, 2010, 09:16:04 AM » |
|
And i get "RomBOOT" not "RomBOOT>" else SAM-BA could access the device!
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #8 on: March 09, 2010, 09:27:56 AM » |
|
This is why I asked you to remove the jumper...when you remove the jumper and power the device then TinyBooter no longer loads. So, even if you loaded a bad program, removing the jumper will solve your issue.
Still no luck, then send the device back for repair. Note that there are fees if the problem turned out to be related to your PC. So, you may want to try a different PC to make sure
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #9 on: March 09, 2010, 10:00:14 AM » |
|
Ok i tried different PCs and none of them worked. I tried it with jumper and without jumper so i can't find where the problem is. I can send it back but im from the Netherlands so then i need to send it to Antratek. Can you take care that the will send me an other module?
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #10 on: March 09, 2010, 10:17:05 AM » |
|
We do not know for sure if you have a defective unit or not and Antratek doesn't have a way for testing the modules. Also, we need to know what went wrong in the module.
If you like, you can send us the module only, not the whole board so shipping is less. But we prefer if you send us the whole system.
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #11 on: March 09, 2010, 10:22:41 AM » |
|
Oke i talked to Antratek and the will send it for me! But in the mean time i need a replacement module so that i can continue my work. Maybe you can work something out with Antratek so that they will send me an other module, because i don't want to buy an other module.
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #12 on: March 09, 2010, 10:29:51 AM » |
|
We will send you a replacement or ask Antratek to send you a replacement module after we receive the one you have and verify the issue. This will only take few days.
Reflashing the ChipworkX will never brake it so we want to know what went wrong....is it a coincidence or you did something that damaged it...we will know once we have it
|
|
|
|
« Last Edit: March 09, 2010, 10:31:53 AM by SupportAdmin »
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #13 on: March 09, 2010, 10:43:33 AM » |
|
It can't be broken, because it still sends data over COM1 of the Dev. System!
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #14 on: March 09, 2010, 10:52:23 AM » |
|
Exactly! Then why you are not able to use USB? This is what we need to know
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #15 on: March 09, 2010, 11:26:32 AM » |
|
Is there also way to connect via JTAG? If so please explain me in detail how!
|
|
|
|
|
Logged
|
|
|
|
|
support
|
|
« Reply #16 on: March 09, 2010, 11:44:35 AM » |
|
Did you try to update the tinybooter bin file through serial port?
|
|
|
|
|
Logged
|
|
|
|
schouteq
Newbie
Posts: 41
|
|
« Reply #17 on: March 09, 2010, 03:37:48 PM » |
|
which COM port do i need to use and with what for program?
|
|
|
|
|
Logged
|
|
|
|
|
SupportAdmin
|
|
« Reply #18 on: March 09, 2010, 03:38:34 PM » |
|
This is in reference to your comment "and i get "RomBOOT" not "RomBOOT>" else SAM-BA could access the device!"
|
|
|
|
|
Logged
|
|
|
|
|
