Pessoal, sem minha permissão, formataram meu PC aqui na empresa.
Instalei o CCS, MPLAB e plug-in de ambos. Também selecionei o CCS como compilador do MPLAB.
Utilizo gravador e hardwares que já fiz vários projetos com eles e já depuravam perfeitamente.
Quando preciso gravar um PIC, tudo funciona bem, mas qgora que precisei fazer um debug, não entra em modo DEBUG nem fodendo.
Reinstalei os programas, troquei de gravador, troquei a placa que faço debug, troquei cabo USB, troquei cabo de gravação e o problema persiste.
O hardware para debug tem alimentação própria e configuro isso no MPLAB.
Alguém poderia me auxiliar?
A mensagem que aparece:
MPLAB ICD 2 ready for next operation
Programming Target...
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0x5B7F)
...Loading DebugExecutive
...Programming DebugExecutive
...Programming Debug Vector
...Programming RSBUG
Verifying...
...Program Memory
...Debug Executive
...Debug Vector
...Verify Succeeded
Programming Configuration Bits
.. Config Memory
Verifying configuration memory...
...Verify Succeeded
Connecting to debug executive
ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information.
MPLAB ICD 2 ready for next operation
Fórum sobre desenvolvimento de sistemas embarcados: Hardware e Software, Tecnologias: Eletrônica digital e analógica, Microcontroladoras, Microprocessadores, Sistemas *NIX (Linux, BSD), Software embarcado Baremetal. Sem fins lucrativos.
Resolvido - Format no PC e agora MPLAB não Debug
Moderadores: andre_luis, 51, guest2003, Renie
8 mensagens
• Página 1 de 1
Resolvido - Format no PC e agora MPLAB não Debug
por hemasc » 29 Fev 2012 15:02
Editado pela última vez por hemasc em 07 Mar 2012 16:31, em um total de 1 vez.
- hemasc
- Nibble
- Mensagens: 80
- Registrado em: 26 Fev 2007 08:59
- Localização: Campinas - SP
Re: Format no PC e agora MPLAB não Debug
por andre_luis » 01 Mar 2012 05:33
hemasc escreveu:...ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information...
O que aparece ?
+++
"Por maior que seja o buraco em que você se encontra, relaxe, porque ainda não há terra em cima."
-
andre_luis - Dword
- Mensagens: 5447
- Registrado em: 11 Out 2006 18:27
- Localização: Brasil - RJ
Re: Format no PC e agora MPLAB não Debug
por hemasc » 01 Mar 2012 11:09
quando clico na mensagem, aparece
ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information.
Description: MPLAB ICD 2 was unable to establish communications with the debug software on the target. This will prevent all debug operations (run, step, halt, breakpoint, etc.)
General Debug Failure Actions
The MPLAB ICD 2 was unable to perform a debugging operation. There are numerous reasons why this might occur.
Top Reasons Why You Can't Debug
1. The oscillator is not working. Check your configuration bits setting for the oscillator.
2. The target board is not powered. Check the power cable connection.
3. Verify whether or not the device requires a header. For the project device, check the Header Specification (DS51292) or Header online help file to see if a header is required.
4. The MPLAB ICD 2 has somehow become physically disconnected from the PC. Check the USB communication cable connection.
5. The MPLAB ICD 2 has somehow become physically disconnected from the target board. Check the communications cable connection.
6. The device is code-protected. Check your configuration bits setting for code protection.
7. You are trying to rebuild the while in Release mode. Select Debug in the Build Configuration drop-down list on the Project menu, then rebuild the project.
8. MPLAB ICD 2 is selected as a programmer, and not as a debugger, in MPLAB IDE.
9. MPLAB ICD 2 to PC communications has somehow been interrupted. Reconnect to the ICD in MPLAB IDE.
10. The target application has somehow become corrupted or contains errors. For example, the regular linker script was used in the project instead of the MPLAB ICD 2 version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr). Try rebuilding and reprogramming the target application. Then initiate a power-on-reset of the target.
11. Other configuration settings are interfering with debugging. Any configuration setting that would prevent the target from executing code will also prevent the ICD from putting the code into debug mode.
12. MPLAB ICD 2 cannot always perform the action requested. For example, the ICD cannot set a breakpoint if the target application is currently running.
13. Brown-out Detect voltage is greater than the operating voltage Vdd. This means the device is in Reset and cannot be debugged.
Other Things to Consider
1. It is possible the error was a one-time glitch. Try the operation again.
2. There may be a problem programming in general. As a test, switch to programmer mode and program the target with the simplest application possible (e.g., a program to blink an LED.) If the program will not run, then you know that something is wrong with the target setup.
3. It is possible that the target device has been damaged in some way (e.g., over current.) Development environments are notoriously hostile to components. Consider trying another target device.
4. Microchip Technology Inc. offers myriad demonstration boards to support most of its microcontrollers. Consider using one of these applications, which are known to work, to verify correct MPLAB ICD 2 functionality.
5. Review the operational theory of ICD operation to ensure proper application setup. (MPLAB ICD 2 Overview)
6. If the problem persists contact Microchip.
ontem atualizei meu MPLAB de 8.80 para 8.84 e continua com o mesmo problema.
algo que notei... sempre que eu tentava entrar no DEBUG com o CODE PROTECT acionado, o MPLAB me dava uma mensagem impedindo, agora nem mensagem ele dá mais
ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information.
Description: MPLAB ICD 2 was unable to establish communications with the debug software on the target. This will prevent all debug operations (run, step, halt, breakpoint, etc.)
General Debug Failure Actions
The MPLAB ICD 2 was unable to perform a debugging operation. There are numerous reasons why this might occur.
Top Reasons Why You Can't Debug
1. The oscillator is not working. Check your configuration bits setting for the oscillator.
2. The target board is not powered. Check the power cable connection.
3. Verify whether or not the device requires a header. For the project device, check the Header Specification (DS51292) or Header online help file to see if a header is required.
4. The MPLAB ICD 2 has somehow become physically disconnected from the PC. Check the USB communication cable connection.
5. The MPLAB ICD 2 has somehow become physically disconnected from the target board. Check the communications cable connection.
6. The device is code-protected. Check your configuration bits setting for code protection.
7. You are trying to rebuild the while in Release mode. Select Debug in the Build Configuration drop-down list on the Project menu, then rebuild the project.
8. MPLAB ICD 2 is selected as a programmer, and not as a debugger, in MPLAB IDE.
9. MPLAB ICD 2 to PC communications has somehow been interrupted. Reconnect to the ICD in MPLAB IDE.
10. The target application has somehow become corrupted or contains errors. For example, the regular linker script was used in the project instead of the MPLAB ICD 2 version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr). Try rebuilding and reprogramming the target application. Then initiate a power-on-reset of the target.
11. Other configuration settings are interfering with debugging. Any configuration setting that would prevent the target from executing code will also prevent the ICD from putting the code into debug mode.
12. MPLAB ICD 2 cannot always perform the action requested. For example, the ICD cannot set a breakpoint if the target application is currently running.
13. Brown-out Detect voltage is greater than the operating voltage Vdd. This means the device is in Reset and cannot be debugged.
Other Things to Consider
1. It is possible the error was a one-time glitch. Try the operation again.
2. There may be a problem programming in general. As a test, switch to programmer mode and program the target with the simplest application possible (e.g., a program to blink an LED.) If the program will not run, then you know that something is wrong with the target setup.
3. It is possible that the target device has been damaged in some way (e.g., over current.) Development environments are notoriously hostile to components. Consider trying another target device.
4. Microchip Technology Inc. offers myriad demonstration boards to support most of its microcontrollers. Consider using one of these applications, which are known to work, to verify correct MPLAB ICD 2 functionality.
5. Review the operational theory of ICD operation to ensure proper application setup. (MPLAB ICD 2 Overview)
6. If the problem persists contact Microchip.
ontem atualizei meu MPLAB de 8.80 para 8.84 e continua com o mesmo problema.
algo que notei... sempre que eu tentava entrar no DEBUG com o CODE PROTECT acionado, o MPLAB me dava uma mensagem impedindo, agora nem mensagem ele dá mais
- hemasc
- Nibble
- Mensagens: 80
- Registrado em: 26 Fev 2007 08:59
- Localização: Campinas - SP
por Djalma Toledo Rodrigues » 01 Mar 2012 17:53
8. MPLAB ICD 2 is selected as a programmer, and not as a debugger, in MPLAB IDE.
9. MPLAB ICD 2 to PC communications has somehow been interrupted. Reconnect to the ICD in MPLAB IDE.
10. The target application has somehow become corrupted or contains errors. For example, the regular linker script was used in the project instead of the MPLAB ICD 2 version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr).
Verificado esses itens?
DJ
9. MPLAB ICD 2 to PC communications has somehow been interrupted. Reconnect to the ICD in MPLAB IDE.
10. The target application has somehow become corrupted or contains errors. For example, the regular linker script was used in the project instead of the MPLAB ICD 2 version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr).
Verificado esses itens?
DJ
-
Djalma Toledo Rodrigues - Dword
- Mensagens: 2334
- Registrado em: 03 Ago 2008 13:22
por hemasc » 02 Mar 2012 15:20
Djalma Toledo Rodrigues escreveu:8. MPLAB ICD 2 is selected as a programmer, and not as a debugger, in MPLAB IDE.
9. MPLAB ICD 2 to PC communications has somehow been interrupted. Reconnect to the ICD in MPLAB IDE.
10. The target application has somehow become corrupted or contains errors. For example, the regular linker script was used in the project instead of the MPLAB ICD 2 version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr).
Verificado esses itens?
DJ
Olá Djalma e obrigado pela resposta!
ítem 8. - Verificado várias vezes
ítem 9. - Verificado várias vezes
ítem 10. - ele grava o mesmo pic na mesma placa, mas não depura
- hemasc
- Nibble
- Mensagens: 80
- Registrado em: 26 Fev 2007 08:59
- Localização: Campinas - SP
por hemasc » 05 Mar 2012 15:42
Ah, tentei depurar em outro PC e nada.
Liguei na Labtools e me disseram que pode ser que a minha fonte chaveada esteja causando isso. Vou montar uma fonte linear e ver o resultado, mesmo sabendo que sempre funcionou com a fonte chaveada.
Depois posto o resultado.
Liguei na Labtools e me disseram que pode ser que a minha fonte chaveada esteja causando isso. Vou montar uma fonte linear e ver o resultado, mesmo sabendo que sempre funcionou com a fonte chaveada.
Depois posto o resultado.
- hemasc
- Nibble
- Mensagens: 80
- Registrado em: 26 Fev 2007 08:59
- Localização: Campinas - SP
por hemasc » 07 Mar 2012 16:29
Bom, vamos lá...
Conforme recomendado pela Labtools-Mosaico, coloquei uma fonte linear no lugar da chaveada. Testei no PC que formataram mas não depurou. Pode ser o motivo do PC estar extremamente lento.
Resolvi testar em outro PC e aí depurou tranquilamente.
Resumindo:
Antes depurava em fonte chaveada, agora não depura mais.
Depurou com fonte linear.
No PC que meteram o format e instalaram 1 milhão de softwares não depurou, mas não sei se o motivo seria ele estar mais lento.
Obrigado a todos pelas dicas.
Conforme recomendado pela Labtools-Mosaico, coloquei uma fonte linear no lugar da chaveada. Testei no PC que formataram mas não depurou. Pode ser o motivo do PC estar extremamente lento.
Resolvi testar em outro PC e aí depurou tranquilamente.
Resumindo:
Antes depurava em fonte chaveada, agora não depura mais.
Depurou com fonte linear.
No PC que meteram o format e instalaram 1 milhão de softwares não depurou, mas não sei se o motivo seria ele estar mais lento.
Obrigado a todos pelas dicas.
- hemasc
- Nibble
- Mensagens: 80
- Registrado em: 26 Fev 2007 08:59
- Localização: Campinas - SP
8 mensagens
• Página 1 de 1
Quem está online
Usuários navegando neste fórum: Nenhum usuário registrado e 1 visitante