TI ICE Board VS Custom Board

Ignacio Aguilar

Hello All,

I am working with the gpio example in the starterware examples directory. Using the ICE board everything is fine, now when I try to run the same code on our custom board the code goes into a AbortHandler and stays in a infinite loop. Any ideas on trouble shooting this issue?

PS We have copied hardware from the ICE board.

over 9 years ago

0 Lalindra Jayatilleke over 9 years ago

TI__Mastermind 30365 points

Ignacio,

Have you checked your hardware during the bring-up to ensure everything is as expected especially the power sequencing and device alive?

Did you go through the board bring-up tips http://processors.wiki.ti.com/index.php/AM335x_board_bringup_tips ?

Could you put break points in your code to see where it crashes? are you able to load the code on the core?

Lali

0 Ignacio Aguilar over 9 years ago in reply to Lalindra Jayatilleke

Intellectual 310 points

I able to load code and step through the code but it seems its crashing at random places in the code.

0 Lalindra Jayatilleke over 9 years ago in reply to Ignacio Aguilar

TI__Mastermind 30365 points

Ignacio,

"crashing at random places in the code."

any specifics? its tough to debug what may be occurring if you are unsure where its crashing.

Is it reaching main()?

Did the board initialize properly?

Lali

0 Ignacio Aguilar over 9 years ago in reply to Lalindra Jayatilleke

Intellectual 310 points

Yes, it is reaching main. I think the board is initializinf properly if it reaching main (always reaching main). Could this be a pin muxing issue. Where in the industrial SDK would I change pin mux parametrs?

0 Lalindra Jayatilleke over 9 years ago in reply to Ignacio Aguilar

TI__Mastermind 30365 points

Ignacio,

Please take a look at this thread that was opened previously on a similar issue. As mentioned previously, It would be helpful to narrow down where in the code its jumping to the aborthandler.

https://e2e.ti.com/support/embedded/starterware/f/790/t/405837

Regarding pinmux changes, Section 9 of this training has directions.

http://software-dl.ti.com/public/hpmp/software/app_dev_procsdk_rtos/index.html

Hope this helps.

Lali

0 Frank Walzer over 9 years ago in reply to Ignacio Aguilar

TI__Mastermind 44306 points

Crashes at random locations could be due to access issues with DDR. As there is no pin-mux on DDR any problems with pin-mux should show up as program functions not working or giving wrong results. Crashes (Data abort exception e.g.) usually happen on non-clocked IP access - register is not visible for ARM. Same can happen with missing MMU config. But these should always show up at same location.

I suggest to check DDR config and reliability again.

Regards,

Processors

Processors forum

TI ICE Board VS Custom Board