Hello
I am running some demo code on my new hardware board. The code works fine using the USB dev-kit. On my board I end up in an infinite loop in the ROM code at location 7F0 00E6.
Can you help me with that one ?
- Are there any doc of the ROM code ?
- Is this a reset like BOD or watchdog ?
- Any other hardware exception ?
I am using Ozone v2.60i, JLink v640 and Segger Jlink EDU under Linux Ubuntu LTS 18.04 out of the box, no configuration.
Thank you in advance
Keywords:
Device:
Hibobspam@free.fr,
There is not any available document regarding the ROM code. Could you please clarify where the firmware gets stuck? I would suggest you to run in debug mode hot attach the debugger. All the hardware design guide lines for the DA1468x are demonstrated into theAN-B-061 Application Note: DA1468x Application Hardware Design Guidelinesdocument. I would highly suggest you to double check the power lines of you board and make sure that re according to the power specifications of DA1468x.
Thanks, PM_Dialog
Hello,
I do execute a demo software based on free_rtos software delivered with the SDK (it works on the USB demo board).
The code execute until "vTaskStartScheduler" but the first task never start.
When I manually halt the cpu, it is executing an infinite loop located at 0x7F000E6 in the ROM (Dialog factory code)
I already checked the LDOs and they are all OK at start-up. Clocks are also OK. The only thing I could not check yet is the DC-DC.
Can you please confirm to me when the DC-DC is started at the first time ? It seems that the DC-DC is located in the IDLE function and that it is toggled when entering or getting out of sleep mode.
Does the CPU try to enter sleep mode during the first execution of vTaskStartScheduler and thus start the DC-DC ?
My code size is 110k and goes to the RAM. I am not sure that all memory is being retained properly so a crash could happen when going to sleep.
Thank you in advance
Problem is solved.
JTAG probe was not loading properly sys_ctrl_reg after reset.