Øyvind Harboe wrote: >> Sure, this will work (if there are no silly mistakes) but what is actually >> happening here ? >> - One specific postprocess function for every variant of in_handler function >> used >> - The upper level user must know which postprocess function to use in every >> specific place, or it wont work, you are rebuilding the in_handler >> functionality in a different place >> - But this is really only a property of the arm7_9 debug interface, and the >> bit structure of the Scanchain 1 and Scanchain 2 registers. >> - When we do cortex-a8 we will have a target with almost the same register >> structure as the ARM7 and 9, but using the arm_adi scanchains. so it is more >> difficult to reuse the armv4_5 stuff since we want to use the same register >> reading logic and writing but we must use differentportprocess functions. >> > > I'm not overly excited about this first attempt. I'll ponder it a bit more. > > I'm not committing anything that isn't a bugfix(regression or > otherwise) or docs until monday. > > > The problem with 1672 is in int MINIDRIVER(interface_jtag_add_ir_scan)(int num_fields, scan_field_t *fields, tap_state_t state) line 606, you have been moving things around.
add_ir_scan is called with just 1 scan_field, then this function sets the number of scanfields equal to the number of taps without allocating a a larger scan_field array. The error will be seen depending on if the out of bounds memory is cleared to 0 or not. Regards Magnus _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
