Unfornately what I experienced is exactly the opposition from your suggestion:
when I donwgrade from V2.4.0 to V2.3.0 the eDMA config tools works perfectly, single TCD, scatter gather mode all are good
but when I use the V2.4.0, the result from the eDMA configure just drive me crazy, here is my test result:
I have a very simple srcAddr and dstAddr array as global variable
uint32_t srcAddr[8] = {0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8};
and
uint32_t dstAddr[8];
below is the "auto-code" from the eDMA (v2.4.0) by using configuration tools

by using different majo loop transfer (bytes), the test result looked like this:

Question: Why the output always doubled as the major loop transfer number?
in the V2.3.0, when I set
major loop transfer byte as 4, I got -> 1 0 0 0 0 0 0 0
major loop transfer byte as 8, I got -> 1 2 0 0 0 0 0 0
major loop transfer byte as 12,I got -> 1 2 3 0 0 0 0 0
.....
I am pretty sure the results from V2.3.0 is expected exactly due to the reference manual. (4 bytes = 1 uint32_t)
the scatter gather mode by V2.4.0 is A desaster. The example code which worked perfectly by V2.3.0. but by V2.4.0 the output is totally wrong.
Has any one from NXP validated the result of eDMA config tool in V2.4.0?